14:54:07 RRSAgent has joined #lws 14:54:11 logging to https://www.w3.org/2024/12/02-lws-irc 14:54:11 RRSAgent, make logs Public 14:54:12 please title this meeting ("meeting: ..."), pchampin 14:54:16 meeting: Linked Web Storage WG meeting 14:54:21 agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20241202T100000/ 14:54:32 pchampin, sorry, could not get https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20241202T100000/ (code 500). 14:54:48 agenda: https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20241202T100000/#agenda 14:54:58 pchampin, sorry, could not get https://www.w3.org/events/meetings/a19ab7dc-1753-433d-bac5-64e3ad8c0a43/20241202T100000/#agenda (code 500). 14:55:15 agenda+ Introductions and announcements 14:55:25 agenda+ Meetings during the holiday season 14:55:43 agenda+ Pending Action Items 1 -> https://github.com/orgs/w3c/projects/153/views/1 14:55:58 agenda+ Separate repository for action items 2 -> https://lists.w3.org/Archives/Public/public-lws-wg/2024Nov/0007.html 14:56:18 PR review 3 -> https://github.com/orgs/w3c/projects/153/views/2 14:56:40 s|PR review 3 -> https://github.com/orgs/w3c/projects/153/views/2| 14:56:43 agenda+ PR review 3 -> https://github.com/orgs/w3c/projects/153/views/2 14:56:48 agenda? 14:58:16 eBremer has joined #lws 14:59:32 acoburn has joined #lws 14:59:38 laurens has joined #lws 14:59:55 uvdsl has joined #lws 15:00:40 present+ 15:00:54 AZ has joined #lws 15:01:12 present+ 15:02:18 present+ 15:02:25 present+ 15:02:33 present+ 15:03:03 hadrian has joined #lws 15:03:59 where is the scribe rotation list? 15:04:40 kaefer3000 has joined #lws 15:04:45 present+ 15:04:47 balessan has joined #lws 15:04:48 Scribe rotation list: https://github.com/w3c/lws-protocol/wiki/Scribe-list 15:05:02 scribe+ uvdsl 15:05:04 present+ 15:05:10 present+ 15:05:30 Laurens: Lets get started. 15:05:35 zakim, open item 1 15:05:35 agendum 1 -- Introductions and announcements -- taken up [from pchampin] 15:05:37 Laurens: Introductions 15:05:41 chair: laurens 15:05:42 present+ 15:05:49 Laurens: Any newcomers? 15:05:55 RRSAgent, draft minutes 15:05:56 I have made the request to generate https://www.w3.org/2024/12/02-lws-minutes.html acoburn 15:06:03 Spilled a tonne of tea on my laptop keyboard. Grumpy with a hair dryer 15:06:03 ... 15:06:30 Laurens: One point of interest: Work on use cases 15:06:39 Laurens: Two points: 15:06:58 Laurens: We want people to engage in async discussions in the Github issues. 15:07:16 Laurens: We only have limited time in the meeting, so get involved. 15:07:53 Laurens: Any comments? 15:07:53 My suggestion: Time box 15 min in each meeting for now on, if there are discussions to have, if not move on. but reserve the time for it 15:08:06 q+ 15:08:42 q? 15:08:53 s/My suggestion/... My suggestion 15:09:35 dmitriz has joined #lws 15:09:49 present+ 15:09:57 bumblefudge has joined #lws 15:10:02 Sarven: Another point to PA's remark: Make sure to switch as to who is speaking 15:10:12 ack csarven 15:10:37 s/Sarven:/csarven: 15:11:02 csarven: +1 to Lauren's suggestion, maybe also add that we may want to consider some time for the proposer to present the use case. 15:11:18 csarven: Then there is more time to review and have question 15:11:37 laurens: +1, lets ask hadrian how he wants to address this 15:11:46 q? 15:12:00 laurens: This was an announcement from my side, any other? 15:12:05 zakim, open next item 15:12:05 agendum 2 -- Meetings during the holiday season -- taken up [from pchampin] 15:12:21 laurens: Holiday season is coming up 15:13:01 ... people have days off, I think there is no overlap between our meetings between the years... however, how will we deal with the meetings on 23rd and the next one? 15:13:16 pchampin: +1, these two might be problematic 15:13:43 kaefer: what about the 6th of January, that might also be relevant to spanish-speaking countries... 15:13:44 i'm working the 6th 15:13:54 can we do a strawpoll to ask who's available on these dates? 15:14:02 q? 15:14:14 laurens: we can do a straw poll 15:14:22 ryey has joined #lws 15:14:26 present+ 15:14:39 present+ 15:14:44 laurens: pchampin is there a straw poll practicse at w3c? 15:14:58 pchampin: just type it out 15:15:09 ... and people comment 15:15:09 STRAWPOLL: Should we keep the WG meeting on December 23th, 2024 15:15:22 -1 15:15:24 -1 15:15:24 -1 15:15:26 -1 15:15:27 -0.5 (I'm not available) 15:15:27 +0 15:15:28 -1 15:15:31 -1 15:15:37 -1 15:15:52 s/23th/23rd 15:16:04 STRAWPOLL: Should we keep the WG meeting on December 30th, 2024 15:16:12 0 15:16:17 -0.5 15:16:20 -1 15:16:22 -1 15:16:22 -1 15:16:23 -0.5 15:16:23 -1 15:16:24 -1 15:16:31 -1 15:16:56 laurens: I guess this means we will cancel these meetings, as most are in favor 15:17:08 ... for good measure 15:17:11 STRAWPOLL: Should we keep the WG meeting on January 6th, 2024 15:17:16 +1 15:17:17 +1 15:17:17 +1 15:17:18 +1 15:17:18 -0,5 15:17:18 0 15:17:21 +1 15:17:23 +1 15:17:29 0 15:17:38 0 15:17:41 laurens: most of you in favour, so we keep that meeting. 15:18:01 ... pchampin will you cancel the two meetings? 15:18:14 zakim, open next agendum 15:18:14 agendum 3 -- Pending Action Items 1 -> https://github.com/orgs/w3c/projects/153/views/1 -- taken up [from pchampin] 15:18:16 pchampin: yes 15:18:34 laurens: let us check in, I do not see any open action items 15:18:48 ... I do not think we had any remaining action items, let me double check 15:19:02 ... I don't think so. 15:19:17 q? 15:19:25 ... then I guess if there are no other action items from meeting participants, then I guess we can jump to the next agenda item 15:19:25 zakim, open next agendum 15:19:25 agendum 4 -- Separate repository for action items 2 -> https://lists.w3.org/Archives/Public/public-lws-wg/2024Nov/0007.html -- taken up [from pchampin] 15:20:04 laurens: brought up by csarven on the mailing list, based on the LWS protocol github repo, csarven can you elaborate? 15:20:10 ack csarven 15:20:53 hadrian+ 15:20:57 csarven: I ll be brief - it is just that the repo is mainly about the type of assets that we work on 15:21:08 s/hadrian+/present+ hadrian 15:21:28 q+ 15:21:33 ... perhaps we can track documents that we work on seperately 15:21:36 present- BBL 15:21:39 ... from the repo 15:22:06 laurens: How do other WG address these kinds of work, how do they track that? 15:22:15 ack pchampin 15:22:42 pchampin: these action itmes / works were put there by bots I set up in the repo (?) 15:22:54 ... RDF-star has a different repo for issues for actions 15:23:19 ... one more repo just for the issues were not a problem there, but in our special case: 15:23:28 ... is it really worth of the overhead? 15:23:56 q+ 15:24:06 I agree with csarven that some of the issues are not related to the protocol, that being said, I would consider the LWS repo as the main repo of the WG, so it is ok to have the org issues there as well. 15:24:21 s/I agree/... I agree 15:24:32 ack laurens 15:24:32 ack laurens 15:24:35 q? 15:24:55 RRSAgent, draft minutes 15:24:57 I have made the request to generate https://www.w3.org/2024/12/02-lws-minutes.html acoburn 15:25:03 laurens: I think it may not be useful to add yet another repot to the 2 existing 15:25:14 cpn has joined #lws 15:25:21 laurens: might be overkill, I do not have strong feelings about creating a new repo 15:25:23 present+ 15:25:34 laurens: csarven just left 15:25:40 q+ 15:25:48 pchampin: does anyone else have strong opinion? 15:25:50 ack hadrian 15:26:18 hadrian: I agree depending how you look at it. If you saw my PR, I put the spec part in a different directory. 15:26:26 ... we have to much to handle already 15:26:34 laurens: anyone else? 15:26:37 s/to much/too much 15:27:01 laurens: So, I dont think we change something in the way how we operate today 15:27:11 ... I think we can come back to the issue in the future 15:27:17 ... if the need arises 15:27:19 +1 to come back to it in the future if this creates confusion/issues 15:27:51 q+ 15:27:58 laurens: hadrian, we can jump back to how we present use cases and discuss them in the meetings 15:27:59 topic: setting up a recurring timebox slots about UCs 15:28:17 laurens: re-iterating proposal 15:28:25 ack hadrian 15:28:27 I have made the request to generate https://www.w3.org/2024/12/02-lws-minutes.html pchampin 15:28:48 s/setting up/Setting up 15:29:11 hadrian: I like the idea of a time-box, but I would like most of the discussion to be asyn, then maybe in meeting have discussions, editors be prepared 15:29:12 q+ 15:29:29 hadrian: to present and answer questions 15:29:42 ... there are lots of use cases to be introduced 15:29:52 s/kaefer:/kaefer3000: 15:30:00 ... I am not yet happy with the formatting 15:30:08 q+ 15:30:14 ack laurens 15:30:26 laurens: that would be my proposal as well 15:30:38 q+ 15:30:40 "discussion at next meeting" :D 15:30:43 ... maybe introduce a tag in the repo, flagged for discussion 15:31:01 s/... maybe/laurens: maybe 15:31:07 laurens: can we set this up? 15:31:18 some w3c groups i've been in use a "next-meeting" tag on github and run the queue accordingly 15:31:21 q? 15:31:25 laurens: if we then do not see the tags, then we can move through the agenda 15:31:26 ack acoburn 15:31:29 ack acobrun 15:31:51 acoburn: I agree. But this is also predicated on people in this group to comment and get engaged 15:32:07 ... please review the use cases, leave comments / call to action! 15:32:08 q? 15:32:14 ack pchampin 15:32:39 pchampin: Just to add: There is actually a practice in other groups, there is a tag in their repos set up 15:32:47 ... discussion tag 15:32:59 ... and we review a list of issues with this tag in the WG meeting 15:33:10 ... the idea is to prio async / offline discussion 15:33:23 ... if this gets too much, then we prompt online discussion with this tag 15:33:27 q? 15:33:34 pchampin: which seems to be efficient 15:34:08 q+ 15:34:10 laurens: Seconding the request of acoburn: Please get involved! And if we can set up a tag, that would be great, hadrian.... 15:34:13 ack hadrian 15:34:36 hadrian: +1, I will create a "needs discussion" tag, and use it as necessary 15:34:51 laurens: will create an action item 15:34:59 ACTION: hadrian creates a needs-discussion tag in the https://github.com/w3c/lws-ucs repo 15:35:07 I created -> issue #5 https://github.com/w3c/lws-protocol/issues/5 15:35:07 but I could not add the "action" label. 15:35:07 That probably means I don't have push permission on w3c/lws-protocol. 15:35:09 pchampin: hadrian, ping me and I will set up the appropriate view in the project 15:35:23 zakim, open next agendum 15:35:24 laurens: Okay, then I guess we can close this agenda item 15:35:24 agendum 5 -- PR review 3 -> https://github.com/orgs/w3c/projects/153/views/2 -- taken up [from pchampin] 15:35:45 laurens: there is a couple of open PRs 15:36:04 laurens: there are some by pchampin? 15:36:42 pchampin: first one is from me, this is a technical one: Making sure that everyting (issues and sorts) is added to the repo/dashboard (?) 15:36:49 ... only needs approval 15:36:55 q? 15:36:55 laurens: given approval just now 15:37:04 ... the other one is by hadrian 15:37:13 q+ 15:37:15 ... I think these are just tehcnical 15:37:17 https://github.com/w3c/lws-ucs/pull/20 15:37:17 https://github.com/w3c/lws-ucs/pull/20 -> Pull Request 20 Prepare to publish first draft. ReSpec tooling and sample content (by hzbarcea) 15:37:21 ack hadrian 15:37:25 s/tehcnical/technical 15:37:45 hadrian: there is not much to discuss ... it is detailled enough. I am unsure when and how you want these PRs merged. 15:37:52 q+ 15:37:56 ... content is correct but looks ugly 15:38:03 ack pchampin 15:38:05 q? 15:38:25 pchampin regarding the uglyness, should not prevent us from merging it. 15:39:09 https://github.com/w3c/rdf-concepts/pull/115 15:39:10 https://github.com/w3c/rdf-concepts/pull/115 -> Pull Request 115 add section about 'unstar' mapping (by pchampin) 15:39:10 ... There is a service that needs to be activated which includes in each PR a link to a preview - maybe we do not need that actually .... 15:39:50 pchampin: This is just for convenience / I propose to make the configuration, I can take an action for this 15:40:03 ... and more to the point: I have not reviewed the PR, I am happy to have a look. 15:40:08 ACTION: pchampin to configure Echidna for preview/diff on PRs in https://github.com/w3c/lws-ucs 15:40:08 I created -> issue #6 https://github.com/w3c/lws-protocol/issues/6 15:40:08 but I could not add the "action" label. 15:40:08 That probably means I don't have push permission on w3c/lws-protocol. 15:40:23 pchampin: we can merge it. we do not need to wait for the improved css. 15:40:42 hadrian: pchampin, once you approve, I merge it. 15:40:51 ... lets get to the process where each PR needs to be approved 15:40:53 s/Echidna/PR-preview 15:40:55 q? 15:41:01 ... then you know someone looked at it 15:41:13 laurens: I do not see anyone on the queue. 15:41:36 laurens: I think this is the end of the regular agenda. Any other business? 15:41:43 q? 15:41:55 laurens: Then we can close early... 15:42:09 ... thank you, and again: Submit your comments on the use cases! 15:42:14 ... see you next week! 15:42:19 ... goodbye! 15:42:20 bye 15:42:27 bye 15:42:27 RRSAgent, make minutes 15:42:29 I have made the request to generate https://www.w3.org/2024/12/02-lws-minutes.html pchampin 16:01:05 TallTed has joined #lws 16:03:55 RRSAgent, pointer? 16:03:55 See https://www.w3.org/2024/12/02-lws-irc#T16-03-55 16:04:25 RRSAgent, draft minutes 16:04:26 I have made the request to generate https://www.w3.org/2024/12/02-lws-minutes.html TallTed s|1 -> https://github.com/orgs/w3c/projects/153/views/1|([1](https://github.com/orgs/w3c/projects/153/views/1)) s|2 -> https://lists.w3.org/Archives/Public/public-lws-wg/2024Nov/0007.html|([2](https://lists.w3.org/Archives/Public/public-lws-wg/2024Nov/0007.html)) s|3 -> https://github.com/orgs/w3c/projects/153/views/2|([3](https://github.com/orgs/w3c/projects/153/views/2)) 17:43:00 s/dont think/don't think/ 17:45:00 s/Time box 15 min in each meeting for now on, if there are discussions to have, if not move on. but reserve the time for it/From now on, time box 15 min in each meeting for any necessary discussions; if none, move on. 17:45:00 s/Lauren's suggestion/Laurens' suggestion/ 17:46:00 s/on 23rd and the next one/on 23rd and 30th/ 17:46:00 s/6th of January, that/6th of January? that/ 17:46:00 s/practicse/practice/ 17:47:00 s/brief - it/brief — it/ 17:48:00 s/asyn, then/async, then/ 17:50:00 s/there is a couple/there are a couple/ 17:50:00 s/everyting/everything/