From ec7eb8a40164b69c5553916725d053413ae83bd0 Mon Sep 17 00:00:00 2001 From: Th <133600193+thhck@users.noreply.github.com> Date: Thu, 21 May 2026 17:40:31 +0200 Subject: [PATCH] Create 2026-05-20.md --- meetings/2026-05-20.md | 133 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 133 insertions(+) create mode 100644 meetings/2026-05-20.md diff --git a/meetings/2026-05-20.md b/meetings/2026-05-20.md new file mode 100644 index 00000000..e72f7e68 --- /dev/null +++ b/meetings/2026-05-20.md @@ -0,0 +1,133 @@ +# W3C Solid Community Group: Weekly + +* Date: 2026-05-20T14:00:00Z +* Call: https://meet.jit.si/solid-cg +* Repository: https://github.com/solid/specification + +## Chair + +* Theo[@thhck](https://github.com/thhck) + +## Present + +* Roberto S.K. Breitman (ODI) +* [Precious Oritsedere](https://ruky-oritsedere.solidcommunity.net#me) +* elf Pavlik +* [Jesse Wright](https://www.jeswr.org/#me) +* Alain Bourgeois +* [Luke Dary](https://w3c.social/@lukedary) +* [Erich Bremer](https://ebremer.com) +* [Rui Zhao](https://me.ryey.icu) + + +## Regrets + +* + +--- + +## Scribe + +* Roberto S.K. Breitman (ODI) +* [Precious Oritsedere](https://ruky-oritsedere.solidcommunity.net#me) + + +### Meeting Guidelines + +* [W3C Solid Community Group Calendar](https://www.w3.org/groups/cg/solid/calendar). +* [W3C Solid Community Group Meeting Guidelines](https://github.com/w3c-cg/solid/blob/main/meetings/README.md). +* No audio or video recording, or automated transcripts without consent. Meetings are transcribed and made public. If consent is withheld by anyone, recording/retention must not occur. +* Join queue to talk. +* Topics can be proposed at the bottom of the agenda to be discussed as time allows. Make it known if a topic is urgent or cannot be postponed. + +### Participation and Code of Conduct +* [Join the W3C Solid Community Group](https://www.w3.org/community/solid/join), [W3C Account Request](http://www.w3.org/accounts/request), [W3C Community Contributor License Agreement](https://www.w3.org/community/about/agreements/cla/) +* [Solid Code of Conduct](https://github.com/solid/process/blob/main/code-of-conduct.md), [Positive Work Environment at W3C: Code of Conduct](https://www.w3.org/policies/code-of-conduct/) +* Operating principle for effective participation is to allow access across disabilities, across country borders, and across time. Feedback on tooling and meeting timing is welcome. +* If this is your first time, welcome! Please introduce yourself. + +--- + +## Introductions +* + +## Announcements + +* Alain Bourgeois: asks if we want to use AI to transcribe the call +* Theo: refers this as a future full topic in a future meeting + +## Topics + +### Action review + + - eP : issue for tasks on solid/shape repository - https://github.com/solid/shapes/pull/62#issuecomment-4448819312 + - Ep: the PR is already up and ready for review, Asks Jesse if he wants it to be merged yet + - JW: not inclined to have it merged right now, until an actual implementation have been done to use the shapes + - Theo: Will wait for implementers ( Noel, Rui ) to give feedback on the PR + + - Theo: invite people to join the chat, set a meeting , solid forum , mailing list, invite noel, the Australian team + - Theo: had an action on inviting folks from autralia for a meeting, invite is out to them, waiting for an answer. would be morning in the EU, late noon in Aus, and middle of the night for USA. + + - invite someone that use ACP to next meeting discussing Virginia's proposition #787 (https://paa.pub uses ACP alongside WAC; docs: https://github.com/daryltd/paa.pub/blob/main/docs/access-control.md ) + - Theo: on the topic of inviting someone who implements ACP, still waiting for input on whether we want to do this, snooze the topic until we can put out an ask to an ACP implementer. + - EP: Is it possible to implement WAC and ACP together? Thinks it will be problematic to have both at same time. Suggests us discussing with any implementers who have already successfully achieved this kind of implementation. Maybe ask Aaaron from Inrupt- might be the best person to evaluate this. + - Luke in chat: implemented in paa.pub + + + +### solid llm-skills repo +- https://github.com/solid/solid-llm-skills +- very nice and helpfull, but needs Community review +* AB: On Solid LLM skills repo, a series of concenrs have been put on github - the key of it is that if this is a skill for everyone to contribute to (rather than just for internal ODI use) it should go through CG review. +* JW: this is meant for everyone, but indeed it needs to be reviewed, both from the CG and from the ODI Solid team (much of this was llm generated). +* AB: this document seems to include both llm intructions and directions to newcomers, but makes no mention of WAC, and includes strange comments on servers. +* JW: it is meant for LLMs to consume not humans, can you point to where it speaks about servers? +* JW: (finds the file), it points to some deployments but not all of them - this seems like a fairly random list. JW will open an issue there to say this should point to the server list on solidproject.org. +* AB: it's a good intiative, but we need to review it and use it. +* Theo: i'll invite everyone to review the skills as suggested. in fact, how do these skills work? +* JW: when using a coding environment you 'install' the skills, then when using an agent it will try and work out what skills are relevant, then use those. I have had mixed experience with skills, i find it most useful in niche languages (it makes up for lack of training data) +* Theo: it would make sense then to add files for specific apps/projects as it doesnt add noise to the files (say if we had a fedcm, or SAI skills file) +* JW: correct + +### use of solid repo on github +- https://github.com/solid +- seems that some last year repo's creation should be better located in solid-contrib or a dedicated ODI repo. + + + +* Theo: passing to Alain on whether certain things should be in the Solid repo (or contrib instead) +* AB: yes, this has come up before, but now i am seeing new repos being created in Solid again which likley should live in Solid-contrib, or the ODI repos. Solid organisation is not ODI, it is meant as the core solid. +* eP: when it concerns codes, it would be good to coordinate with Jackson and the open source tooling group, eP will be in touch with Jackson to set up a a meeting. that said if its opinionated implementation, it should be all or none for them (not just ODI). +* JW: it's always been unclear, what the scope of the Solid github should contain, maybe just specifications repo? Roberto needs to work on this to determine what lives in the Solid Contrib, ODI,etc +* RS: Can help write out the goveners for this and help coordinate things at the ODI too to ensure things are done the right way +* eP: App developers shouldn't feel like they have to compete with the solid project +* RS: the ODI apps shouldn't be prioritised over other implementers apps in the organisation +* Theo: Should we dig into this now? and determine what should belong where? +* JW: we dont have the right stakeholders like Jackson on the call right now to have this discussion now +* Theo: we can make this an action item +* JW: Can Roberto bring a proposed governs doc on this next CG meeting + +### solidcommunity.net updates ( if times allow ) + + - update FedCM module + - google login ? + + * JW: Solidcommunity.net performance issue is being currently reviewed ( current hypothesis is an issue with lock file ) + * Theo: possible to have servers not only in Europe, for same performance around the world ? + * JW: don't have that resource right now + +## Actions +eP to reach out to Jackson to set up time to talk about reposatory organization. + + - Roberto: Redefine scope of solid repo ( /solid /solid-contrib /odi ... ) as well as npm package + - eP: recontact Jackson to get update on open-source tooling + - eP: add roadmap to next week CG + +## Decisions + +## Links + + + + +