15:48:34 <RRSAgent> RRSAgent has joined #lws
15:48:39 <RRSAgent> logging to https://www.w3.org/2024/10/11-lws-irc
15:48:39 <Zakim> RRSAgent, make logs Public
15:48:40 <Zakim> please title this meeting ("meeting: ..."), pchampin
15:49:01 <pchampin> meeting: Linked Web Storage WG kick-off meeting
15:49:20 <agendabot> agendabot has joined #lws
15:49:27 <pchampin> agenda: https://www.w3.org/events/meetings/a51d8296-7205-4935-a2de-ad17b26b3fdf/#agenda
15:49:28 <agendabot> clear agenda
15:49:28 <agendabot> agenda+ Intro to W3C process (10 minutes)
15:49:28 <agendabot> agenda+ Charter and resources (5 minutes)
15:49:28 <agendabot> agenda+ Vision (5 minutes)
15:49:28 <agendabot> agenda+ Objectives and success criteria (10 minutes)
15:49:31 <agendabot> agenda+ Testing (with protocol test examples from SPARQL Graph Protocol or LDP) (5 minutes)
15:49:34 <agendabot> agenda+ Use cases (15 minutes)
15:51:56 <eBremer> eBremer has joined #lws
15:59:19 <csarven> present+
15:59:45 <acoburn> acoburn has joined #lws
16:00:07 <pchampin> present+
16:00:08 <laurens> laurens has joined #lws
16:00:16 <acoburn> present+
16:00:37 <eBremer> present+
16:02:03 <pchampin> not easy for me to speak
16:02:12 <pchampin> am I sill muted on zoom?
16:02:15 <laurens> yes
16:03:10 <laurens> present+
16:03:18 <bumblefudge> bumblefudge has joined #lws
16:03:29 <jeswr> jeswr has joined #lws
16:03:33 <hadrian> hadrian has joined #lws
16:03:34 <dmitriz> present+
16:03:38 <bumblefudge> present+
16:03:40 <jeswr> present+
16:03:46 <hadrian> present+
16:04:06 <bumblefudge> present+ ericP
16:05:25 <BenDM> BenDM has joined #lws
16:05:28 <jucanbe> jucanbe has joined #lws
16:05:57 <timbl> timbl has joined #lws
16:06:13 <bumblefudge> present+ BenDM
16:06:17 <bumblefudge> present+ jucanbe
16:06:28 <bumblefudge> present+ timBL
16:06:34 <timbl> present+
16:06:49 <AZ> AZ has joined #lws
16:07:01 <dmitriz> scribe+
16:07:17 <pchampin> for future scribes, instructions are available here: https://w3c.github.io/scribe2/scribedoc.html#notes
16:07:23 <AZ> present+
16:07:48 <bumblefudge> present?
16:07:57 <bumblefudge> zakim, who's here?
16:07:57 <Zakim> Present: csarven, pchampin, acoburn, eBremer, laurens, dmitriz, bumblefudge, jeswr, hadrian, ericP, BenDM, jucanbe, timBL, AZ
16:08:00 <Zakim> On IRC I see AZ, timbl, jucanbe, BenDM, hadrian, jeswr, bumblefudge, laurens, acoburn, eBremer, agendabot, RRSAgent, Zakim, pchampin, dmitriz, csarven
16:08:06 <pchampin> zakim, who is here?
16:08:06 <Zakim> Present: csarven, pchampin, acoburn, eBremer, laurens, dmitriz, bumblefudge, jeswr, hadrian, ericP, BenDM, jucanbe, timBL, AZ
16:08:08 <Zakim> On IRC I see AZ, timbl, jucanbe, BenDM, hadrian, jeswr, bumblefudge, laurens, acoburn, eBremer, agendabot, RRSAgent, Zakim, pchampin, dmitriz, csarven
16:08:16 <TallTed> TallTed has joined #lws
16:08:23 <TallTed> present+
16:08:27 <dmitriz> topic: Introductions
16:08:38 <csarven> +q
16:08:40 <TallTed> Zakim, who's here?
16:08:40 <Zakim> Present: csarven, pchampin, acoburn, eBremer, laurens, dmitriz, bumblefudge, jeswr, hadrian, ericP, BenDM, jucanbe, timBL, AZ, TallTed
16:08:43 <Zakim> On IRC I see TallTed, AZ, timbl, jucanbe, BenDM, hadrian, jeswr, bumblefudge, laurens, acoburn, eBremer, agendabot, RRSAgent, Zakim, pchampin, dmitriz, csarven
16:09:02 <csarven> Hi I'm Sarven Capadisli. My WebID: https://csarven.ca/#i . My background on Solid/LWS etc. work: https://csarven.ca/linked-web-storage-invited-expert-request
16:09:13 <dmitriz> csarven: hi, I'm Sarven, excited to be here, it's been a long road
16:09:30 <dmitriz> ... I've been involved in Solid (core aspect of Linked Web Storage work) since 2015 at MIT
16:09:45 <dmitriz> ... I've chaired the Solid CG for 4 years, authored and edited almost all of the input docs you see in the charter
16:09:52 <dmitriz> ... and worked on implementing applications and some server work
16:10:15 <dmitriz> ... happy that a lot of fun and pain and crying led to the work here, hoping we'll have a successful outcome (and I'm sure we will!). and fix the web!
16:10:44 <dmitriz> acoburn: hi I'm Aaron Coburn, work for Inrupt, I'm one of the co-chairs
16:11:03 <dmitriz> ... been working in the Solid space for a number of years, worked on LDP related things, including Fedora API, I was editor and author on that spec
16:11:14 <dmitriz> ... very happy to be here, I've also been editor and author of various docs in the Solid space as well
16:11:30 <dmitriz> eBremer: hi I'm Eric Bremer, working for ...? for Bioinformatics
16:11:36 <ryey> ryey has joined #lws
16:11:48 <dmitriz> ... working on deep learning pipelines, GeoSPARQL, modeling the storage system after Solid
16:12:13 <dmitriz> s/...?/Stonybrooks University/
16:12:32 <dmitriz> laurens: hi, I'm Laurens, one of the co-chairs, I represent the government of Flanders,
16:12:38 <cpn> cpn has joined #lws
16:12:41 <dmitriz> ... been working with Solid for many years, mostly apps building on top of it
16:12:44 <cpn> present+ Chris_Needham
16:12:55 <dmitriz> ... I hope for a very successful outcome for this WG of course
16:13:57 <dmitriz> dmitriz: hi, I'm Dmitri, longtime fan of Solid
16:14:14 <dmitriz> bumblefudge: hi, I represent the IPFS Foundation
16:14:49 <Grace> Grace has joined #lws
16:15:00 <dmitriz> jeswr: I'm Jesse Wright, been working on Solid and semantic things for several years, previously affiliated Australian nat'l university
16:15:16 <eBremer> s/Stonybrooks University/Stony Brook University/
16:15:28 <dmitriz> ... worked at Inrupt a couple years working on SDKs, now doing research on semantic web agents, data privacy, automated data governance
16:15:46 <dmitriz> hadrian: hello I'm Hadrian, excited to be here, I'm representing Inrupt, I'm also co-chair of Solid CG
16:16:01 <dmitriz> ... also member of Apache Software Foundation. also happy this WG started
16:16:13 <eBremer> s/for Bioinformatics/in the Department of  Biomedical Informatics/
16:16:39 <dmitriz> ericP: my name is Eric P., worked at W3C for a long time, on a number of semantic web standards
16:16:53 <dmitriz> ... my current affiliation is - Leiden (sp?) University Medical Center
16:17:14 <dmitriz> ... I found out today that I'll be doing another medical data storage system on top of Solid. I'm also co-chair
16:17:46 <dmitriz> benDM: I'm from IMAC, Belgian research university, we've been doing some research since 2009, me from 2013
16:17:58 <pchampin> s/IMAC/Imec
16:18:07 <dmitriz> ... we've been doing Solid research and working together with Flemish Government for a couple of years, bringing Solid to production
16:18:28 <dmitriz> jucanbe: hi everyone, I'm Juan, I work on University Polytechnical Madrid, finishing my PhD Thesis
16:18:36 <dmitriz> ... related to semantic web policy policies based on ODRL
16:19:28 <dmitriz> timbl: hi, I'm Tim Berners-Lee, invented the web 30-something years ago,
16:19:28 <dmitriz> ... worked at MIT at W3C, which a bunch of you contributed to
16:19:36 <dmitriz> ... in 2001, we had some funding in the lab from DARPA for some semantic web research
16:19:47 <dmitriz> ... so we built rule-based system, exporters & importers, a Read-Write Web
16:20:23 <dmitriz> ... when browsers got Javascript / AJAX, the ability to communicate with the web itself, that meant we could move from apps running on our laptops to a read-write web
16:20:40 <dmitriz> ... if a storage system doesn't care which app writes to it, that's very powerful
16:20:50 <dmitriz> ... still working on a good name for it, we ended up with Social Linked Data or Solid
16:21:14 <dmitriz> ... we had more funding to improve Solid from Mastercard, in the lab
16:21:28 <dmitriz> ... and a few years, we founded Inrupt
16:21:28 <dmitriz> ... to continue the work of bringing Solid to the world
16:21:41 <dmitriz> ... my dayjob is at Inrupt
16:22:06 <dmitriz> AZ: I'm Antoine Zimmermann, professor at Ecole ...?
16:22:26 <dmitriz> ... I've been doing research in the area of Semantic Web for 20 years now, recently I took interest in helping autonomous web agents to interact with web resources
16:22:36 <acoburn> s/...?/Institut Mines-Télécom/
16:22:37 <dmitriz> ... I'd like to investigate how artificial agents could have a web presence in the form of Solid pods
16:22:56 <dmitriz> ... also co-chair of the Web Agents CG
16:23:28 <dmitriz> TallTid: hi I'm Ted T., involved with OpenLink Software since 2000, w3c shortly after that
16:23:31 <dmitriz> ... if it has to do with the semantic web, sparql, etc, I'm there
16:23:45 <pchampin> Pierre-Antoine Champin, from Inria and W3C. I'm the team contact of this WG. Thrilled to have the group starting at last, and to see you all here.
16:23:46 <AZ> s/at Ecole ...?/at École des mines de Saint-Étienne, part of Institut Mines-Télécom/
16:23:47 <dmitriz> ... my primary coding language is English, so, expect lots of grammer & spelling etc corrections on your PRs
16:24:04 <TallTed> s/grammer/grammar/
16:24:05 <TallTed> :-)
16:24:50 <dmitriz> ryey: hi I'm Rui Zhao, at University of ...?, working on privacy preserving computation and privacy policies
16:25:01 <dmitriz> ... big fan of decentralized tech, including Solid
16:25:03 <TallTed> s/TallTid: hi I'm Ted T., involved/TallTed: hi, I'm Ted Thibodeau, involved
16:25:14 <TallTed> RRSAgent, draft minutes
16:25:16 <RRSAgent> I have made the request to generate https://www.w3.org/2024/10/11-lws-minutes.html TallTed
16:25:26 <ryey> present
16:25:28 <dmitriz> present+ ryey
16:25:56 <dmitriz> cpn: hi I'm Chris Needham, representing the BBC, I have various roles at w3c, media related groups
16:26:12 <dmitriz> ... the BBC has been very interested in personal data stores and a more private web in general, giving data ownership and control to people over the years
16:26:29 <dmitriz> ... we've had quite a few research projects in this space over the past 8 years. Relative newcomer to Solid myself
16:26:38 <dmitriz> ... as an org we're generally very supportive of the work here
16:27:08 <dmitriz> ericP: next thing is to go over w3c Process a bit
16:27:28 <dmitriz> ericP: W3C is a standards org that develops in the open
16:27:38 <dmitriz> ... and we make it so that the people in the WG can vote, argue, make PRs etc
16:27:51 <dmitriz> ... the public in general can also make comments at regular intervals (on Working Drafts)
16:28:06 <dmitriz> ... we'll probably start with a Use Case Document, then start working on specs after that
16:28:21 <dmitriz> ... the process is one where we as a group elect an Editor
16:28:32 <TallTed> chair: acoburn
16:28:42 <dmitriz> ... we make suggestions ,they make edits, we make a snapshot ready to share with the world (Working Draft)
16:28:58 <dmitriz> ... specifically First Public Working Draft (FPWD)
16:29:09 <dmitriz> ... after that, we'll iterate, publish WDs every 3 months so that the world is appraised
16:29:28 <dmitriz> ... we want the community engaged, making PRs
16:29:28 <dmitriz> ... for patent protection, everyone who joined the group had to sign the IPR policy
16:29:34 <dmitriz> ... goal there is to make sure there's no submarine patents
16:29:55 <bumblefudge> bumblefudge has joined #lws
16:29:58 <dmitriz> ... if a member of the public makes a technical PR to a spec, we have to make sure to clear it
16:30:09 <dmitriz> ... then we'll go to Last Call. typically before Last Call, we'll make a Test Suite
16:30:19 <dmitriz> ... we'll have some specs, some tests, interoperable implementations
16:30:26 <dmitriz> ... the idea is separately implement it independently
16:30:35 <dmitriz> ... we're testing the spec by implementing. and then test the implementations
16:31:00 <dmitriz> ... then we get to go to Proposed Recommendation (PR)
16:31:07 <dmitriz> ... (this is also mostly for patent protection)
16:31:28 <dmitriz> ... there's another path, if we have a continuously changing spec, we can do what's known as an Evergreen Spec
16:31:38 <dmitriz> ... basically saying - it feels done, but we keep adding more cool things to it, so we can go to PR or REC when we do Evergreen as well
16:32:08 <dmitriz> timbl: I'm sure if we missed any process aspects, we'll discover them and bring them up later
16:32:41 <dmitriz> ericP: last thing is, during Candidate Rec (CR), when people are making comments, we have to document to the Director that we have adequately addressed all the issues people raised
16:32:50 <dmitriz> ... which means we have to do good bookkeeping, so, brace yourself.
16:32:53 <pchampin> q+ to talk about CR and exit criteria
16:32:57 <csarven> q-
16:33:34 <pchampin> just to point out that we have a list of groups with which we need to synchonize
16:33:44 <pchampin> we must not wait until going to PR to do that
16:34:16 <dmitriz> ericP: yeah, another role of W3C is that we're telling a coherent story, that the groups talk to each other
16:34:32 <dmitriz> ... in the charter, we have a list of groups to coordinate with because they're related tech
16:34:45 <dmitriz> ... especially the Infrastructure group, Accessibiilty, etc
16:34:59 <dmitriz> ... so when we get close to CR, we'll have to do horizontal review in advance
16:35:28 <dmitriz> ... there is probably a fair amount of i18n and accessibility expertise in the group
16:35:28 <dmitriz> ... so if you have a question about that, please let us know
16:35:38 <TallTed> current process doc -- https://www.w3.org/policies/process/
16:35:59 <dmitriz> topic: Charter and Resources
16:36:17 <dmitriz> ericP: the charter has a bunch of pointers to the Mailing List and various input docs
16:36:32 <acoburn> Charter document: https://www.w3.org/2024/09/linked-web-storage-wg-charter.html
16:36:33 <dmitriz> ... the Process doc much more formally describes what I've been going over
16:36:37 <jeswr> jeswr has joined #lws
16:36:44 <dmitriz> ... one of the things you'll see in it is "How do we know we're done?" or Success Criteria
16:36:56 <dmitriz> ... important to keep in mind, whether it goes into the critical path to completion of specs
16:37:02 <dmitriz> ... so, reading scope and deliverables is useful
16:37:04 <TallTed> all about LWS WG -- https://www.w3.org/groups/wg/lws/
16:37:06 <dmitriz> ... also has a timeline
16:37:28 <dmitriz> topic: Vision
16:38:01 <dmitriz> timbl: sure. the Vision for this WG is quite big, in that we're hoping that this protocol will be used by many systems
16:38:18 <dmitriz> ... if you have a pod which has one app running on it, that sort of misses the main value proposition
16:38:54 <dmitriz> ... but if you have different apps being able to read and write the same data, using read-write Linked Data Storage, and they actually share
16:38:58 <dmitriz> ... then that becomes very powerful
16:39:07 <dmitriz> ... obviously AI is part of the mix now, which adds to the power
16:39:28 <dmitriz> ... so, it's about putting the user in a situation where they're in control
16:39:41 <dmitriz> ... not just protecting privacy, but it's also focusing on the positive aspects -- individuals are a lot more powerful when there's interop between many different apps
16:39:44 <TallTed> s/current process/current W3C process/
16:39:50 <TallTed> RRSAgent, draft minutes
16:39:51 <RRSAgent> I have made the request to generate https://www.w3.org/2024/10/11-lws-minutes.html TallTed
16:39:59 <dmitriz> ... so, the vision is hard to explain to people. sort of like, Code Locally, Think Globally
16:40:14 <dmitriz> ericP: any questions?
16:40:30 <dmitriz> topic: Objectives and Success Criteria
16:41:00 <dmitriz> acoburn: (reads them from charter)
16:41:38 <dmitriz> ... couple of things we're looking at. one is, a proposed rec of interoperable implementations of each of the feature defined in the spec
16:41:48 <dmitriz> ... a Linked Data Storage protocol, defined at the end of this process
16:41:57 <dmitriz> ... we'll document the testing policies, processes, etc
16:42:09 <dmitriz> ... each spec will contain sections on Security and Privacy implications. there'll be a general thread model
16:42:13 <dmitriz> ... for the ecosystem
16:42:21 <dmitriz> ... in addition, each spec will contain a section on Accessibility
16:42:30 <dmitriz> ... benefits, impacts, accessible features
16:42:42 <dmitriz> ericP: any questions on the above?
16:42:47 <dmitriz> topic: Testing
16:43:11 <dmitriz> ericP: when we're developing the spec, we typically have 2+ implementations for each spec.
16:43:29 <dmitriz> ... there's a history  of writing test suites for a protocol, notably LWP and Sparql
16:44:11 <dmitriz> ... with protocol tests, it's more that - we have some client that we all use as a test tool, and it has some interactions with your server, it gets a response back, we validate if it passes/fails
16:44:15 <jucanbe> jucanbe has joined #lws
16:44:17 <csarven> s/LWP and Sparql/LDP and SPARQL/
16:44:20 <dmitriz> ... every feature in the spec needs 2+ implementations that pass the test
16:44:37 <dmitriz> ... so, we'll try to look to LDP test suite for inspiration
16:44:52 <dmitriz> ... so, expect that we'll be writing server tests
16:44:52 <pchampin> some work has also been done in the CG about test suites
16:45:05 <dmitriz> topic: Use Cases
16:45:33 <dmitriz> acoburn: before we begin writing spec text, we're going to develop a Use Cases doc
16:45:49 <dmitriz> ... which will feed into a Use Cases and Requirements doc, which we'll prioritize
16:45:53 <dmitriz> ... and then we can buil da spec on that.
16:46:14 <dmitriz> ... we'll be collecting use cases, both from members of the WG and also from people who have interest in this
16:46:21 <dmitriz> ... there'll be a Github repo
16:46:34 <acoburn> https://www.w3.org/groups/wg/lws/tools/
16:46:40 <dmitriz> ... two repos of relevance, you can find them from ^
16:46:44 <acoburn> https://github.com/w3c/lws-ucs
16:46:46 <dmitriz> ... in particular, the Use Cases Doc ^
16:46:54 <dmitriz> ... what we'd like to do is have use cases presented as Issues
16:47:06 <dmitriz> ... so, rather than PRs with specific use cases, instead open issues for each one
16:47:26 <dmitriz> ... that way, it can be refined, discussed, and once we have consensus, then we can make a PR
16:47:29 <dmitriz> ... which will eventually become a WG Note
16:47:35 <dmitriz> ... we don't have a template currently, but we will soon
16:48:00 <dmitriz> ... we began collecting some use cases from TPAC, at a breakout session
16:48:08 <dmitriz> ... so we have some already collected. those have not yet been added to the repo
16:48:29 <dmitriz> ... we'll open issues for them shortly.
16:48:44 <dmitriz> ... I suspect the use cases will primarily be collected asynchronously, and during meetings
16:48:57 <dmitriz> ... anything that requires specific discussion and voting, that's when it'll happen
16:49:16 <BenDM> q+
16:49:23 <timbl> q+ to mention the solid roadmap for vertiicals
16:49:38 <dmitriz> ack pchampin
16:49:38 <Zakim> pchampin, you wanted to talk about CR and exit criteria
16:49:46 <dmitriz> ack BenDM
16:50:09 <dmitriz> benDM: the target goal of these Use Cases, is it meant that these are real world scenarios that we want to make sure works with LWS recs?
16:50:20 <dmitriz> ... are we talking about more technical use cases? What's the level of technicality required?
16:50:43 <TallTed> RRSAgent, draft minutes
16:50:44 <RRSAgent> I have made the request to generate https://www.w3.org/2024/10/11-lws-minutes.html TallTed
16:50:50 <dmitriz> acoburn: I'm expecting things from the real world, things a developer or a user would encounter in the process of using this protocol
16:50:54 <dmitriz> ... so, as much details as is relevant to that. I don't want these use cases to be pages and pages in length
16:51:07 <csarven> q+ to talk about degree of commitment to implement a requirement (derived from URC) and share implementation code
16:51:10 <dmitriz> ericP: yeah, agree. typically Use Cases drive technical requirements, but they dont' initially contain technical reqs
16:51:28 <dmitriz> ... it's handy to have short coherent stories at the beginning
16:51:28 <dmitriz> q?
16:51:35 <dmitriz> ack timbl
16:51:35 <Zakim> timbl, you wanted to mention the solid roadmap for vertiicals
16:51:38 <timbl> Solid project Verticals Roadmap https://solidproject.solidcommunity.net/Verticals/Roadmap/index.ttl#this
16:51:52 <dmitriz> timbl: the Solid project has a Solid Pod provisioned for it
16:52:07 <dmitriz> ... there's some brainstorming for which Verticals are out there
16:52:28 <dmitriz> ... rough high-level list
16:52:38 <dmitriz> ... so, Healthcare community for example
16:52:44 <dmitriz> ... might have specific requirements.
16:53:28 <dmitriz> ericP: yeah, we might need to make sure we've got coverage of use cases and verticals
16:53:28 <dmitriz> ... so, lots of eyes and brains on it
16:53:38 <dmitriz> ... one thing we can do is tag our usecases with which vertical it applies to
16:53:45 <dmitriz> timbl: that would be good
16:53:52 <dmitriz> q?
16:54:22 <dmitriz> ... it'd be good if communities brought their existing specs and usecases, and we could map it to usecases
16:54:34 <dmitriz> ericP: makes sense
16:54:38 <acoburn> q+ we need volunteers to manage and edit use cases
16:54:48 <dmitriz> q+ ryey
16:55:06 <dmitriz> acoburn: we haven't formally set a date/time for calls
16:55:28 <dmitriz> ... looks like Tue/Wed/Thu are very busy for everyone. so I suspect this will be a Fri or Mon call
16:55:36 <dmitriz> ack csarven
16:55:36 <Zakim> csarven, you wanted to talk about degree of commitment to implement a requirement (derived from URC) and share implementation code
16:56:04 <dmitriz> csarven: just so we know when we're done (with use cases)
16:56:04 <TallTed> s/URC/UCR/
16:56:21 <dmitriz> ... we need to figure out a bunch of things - deadlines, some sort of criteria for done-ness
16:56:21 <acoburn> q+
16:56:32 <dmitriz> ... criteria for which usecases to keep, or which ones are duplicates
16:56:39 <dmitriz> ... whether the usecases are ethically grounded, etc
16:56:56 <dmitriz> ... one thing I often find comes up with other groups is, assessing whether the usecases will actually be implemented, and by whom
16:57:57 <dmitriz> ... so that we're not overwhelmed by too many usecases / hypotheticals
16:58:09 <dmitriz> ericP: makes sense
16:58:58 <dmitriz> ... there will be a lot of organic development, feel free to raise the issue if it doesnt get addressed
16:59:18 <csarven> s/URC/UCR
16:59:27 <dmitriz> ... we'll get to a point where we have use cases, where we'll be like - love to do that, won't get it done
16:59:30 <dmitriz> ack ryey
16:59:37 <dmitriz> ryey: also question about the scope of the usecases
16:59:49 <dmitriz> ... do we have a scope of what goes into the LWS protocol?
16:59:57 <dmitriz> ... in terms of what additional things go in there?
17:00:02 <dmitriz> ericP: not yet
17:00:19 <dmitriz> ryey: I have some use cases, but I'm not sure if they fit into the scope of the WG
17:00:32 <dmitriz> ericP: write them up and bring em up in the meeting, or just open an issue
17:00:38 <hadrian> hadrian has joined #lws
17:01:11 <dmitriz> acoburn: we're going to need someone who can be an editor of these usecases. (one or more people)
17:01:26 <TallTed> for future -- meetings should target :55 as end-time (and really try hard to stick to it)
17:01:28 <dmitriz> ... to refine them, edit them, format them
17:01:28 <dmitriz> ... if people are interested, start thinking about that
17:01:41 <acoburn> ack acoburn
17:02:24 <csarven> q+ Suggest to avoid Monday/Friday -- holidays and folks being away for other reasons
17:02:39 <pchampin> I propose to send a poll today or tomorrow about a weekly slot. The previous poll was explicitly for this week only.
17:02:47 <dmitriz> @csarven -- that rules out all the days then :)
17:03:21 <csarven> I meant Monday and Friday, not Monday to Friday =)
17:03:28 <dmitriz> ericP: we'll take the timing discussion to the mailing list
17:03:28 <dmitriz> scribe-
17:03:51 <dmitriz> @csarven - and earlier in the call, eric  & aaron mentioned that Tue-Weds-Thu are taken up
17:04:45 <pchampin> RRSAgent, make minutes
17:04:46 <RRSAgent> I have made the request to generate https://www.w3.org/2024/10/11-lws-minutes.html pchampin
17:04:52 <csarven> Ah, I guess we only have the weekend =)
19:09:17 <timbl> timbl has joined #lws
23:44:17 <dmitriz> dmitriz has joined #lws