Skip to content

Commit b9c489c

Browse files
elf-pavlikTallTed
andauthored
Create 2025-09-03.md (#741)
* Create 2025-09-03.md * Update meetings/2025-09-03.md Co-authored-by: Ted Thibodeau Jr <[email protected]> --------- Co-authored-by: Ted Thibodeau Jr <[email protected]>
1 parent 44b3954 commit b9c489c

File tree

1 file changed

+129
-0
lines changed

1 file changed

+129
-0
lines changed

meetings/2025-09-03.md

Lines changed: 129 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,129 @@
1+
# W3C Solid Community Group: Weekly
2+
3+
* Date: 2025-09-03:00:00Z
4+
* Call: https://meet.jit.si/solid-cg
5+
* Chat: https://matrix.to/#/#solid_specification:gitter.im
6+
* Repository: https://github.com/solid/specification
7+
8+
## Chair
9+
10+
* Michiel
11+
12+
## Present
13+
14+
* [elf Pavlik](https://elf-pavlik.hackers4peace.net)
15+
* [Pierre-Antoine Champin](https://champin.net/#pa)
16+
* [Matthias Evering](https://soliweb.me/testpro/)
17+
* [Erich Bremer](https://ebremer.com)
18+
* Tom Byrd
19+
* [Michal](https://id.mrkvon.org)
20+
* Marc Haddle
21+
* Michiel de Jong
22+
* Mahdi Baghbani
23+
* [Matthieu Bosquet](https://github.com/matthieubosquet)
24+
* Ted Thibodeau Jr (he/him) (OpenLinkSw.com) // GitHub:[@TallTed](https://github.com/TallTed) // Mastodon:[@TallTed](https://mastodon.social/@TallTed)
25+
* [Rui Zhao](https://me.ryey.icu)
26+
27+
28+
## Regrets
29+
30+
## Scribes
31+
32+
* elf Pavlik
33+
34+
---
35+
36+
## Announcements
37+
38+
39+
### Meeting Guidelines
40+
* [W3C Solid Community Group Calendar](https://www.w3.org/groups/cg/solid/calendar).
41+
* [W3C Solid Community Group Meeting Guidelines](https://github.com/w3c-cg/solid/blob/main/meetings/README.md).
42+
* 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.
43+
* Join queue to talk.
44+
* 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.
45+
46+
### Participation and Code of Conduct
47+
* [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/)
48+
* [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/)
49+
* 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.
50+
* If this is your first time, welcome! please introduce yourself.
51+
52+
---
53+
54+
## Review Action items
55+
56+
* eP: [Draft PR to CSS grant-type:jwt-barer — alternative to client credentials](https://github.com/CommunitySolidServer/CommunitySolidServer/pull/2053) — Client ID URL and multi tenant
57+
* eP: [Conformance Test Hanress 'main' seems broken](https://github.com/solid-contrib/conformance-test-harness/issues/673)
58+
* eP: [ESM support for Components.js](https://github.com/comunica/comunica/issues/930#issuecomment-3224275352) — affecting CSS, sai-js, LDO (indirectly NextGraph), Comunica, etc.
59+
60+
## Topics
61+
62+
### Community Council CG
63+
64+
[Update on Project to Enhance Community Groups](https://www.w3.org/events/meetings/29a19815-57f8-488a-8e14-9b5809bf14de/)
65+
66+
### Solid World
67+
68+
https://theodi.org/news-and-events/events/solid-world-september-2025/
69+
70+
Tue Sep 16th
71+
72+
73+
### Focus in Q4 2025
74+
75+
#### Demos
76+
77+
* PodOS — Angelo
78+
* DToU — Rui
79+
* LDES? — Wout?
80+
* SpOTy: Solid app developed in collab with research center in linguistics — PAC
81+
* Solid Activity Pub integration — Michal
82+
83+
84+
##### misc
85+
86+
* Tom: Discussion about access control models and law; for example, in US, regarding health care.
87+
88+
89+
### Tracking obstacles
90+
91+
We can keep better track of the obstacles participants are facing in achieving their goals. How CG and broader Solid community can help with overcoming them.
92+
93+
eP: For instance, functionality someone needs in CSS or in the test harness.
94+
95+
MdJ: Yes, for instance also, when someone asks a question on Matrix, in general we get good replies and pointers.
96+
97+
Matthias: I managed to process read process, now working on write. It feels like the puzzle where pieces are falling into places. I'm diving into Noel's code, and following open source approach.
98+
99+
### Use cases and requirements
100+
101+
* Coordinating with WG
102+
* Capturing ones like brought up by Fred for Trinpod
103+
104+
### Reconnecting with communities
105+
106+
Maybe Practictioners could lead it
107+
108+
* https://solidlab.be/
109+
* https://solidcommunity.au/
110+
111+
PAC: Scope of Solid CG is pretty broad and it might be hard to track. There are break out sessions around TPAC and in spring. CGs may discuss and open what they do for broader audience. Also open our group and make joined sessions. PAC will be there in person.
112+
113+
https://www.w3.org/2025/11/TPAC/breakouts.html
114+
115+
116+
### Scribing
117+
118+
Can we keep trying to automate it? More CGs need it, worth finding out what hapened to the [modern tooling](https://w3c.github.io/modern-tooling/) effort.
119+
120+
* TallTed: Credentials CG has embraced GoogleMeet and some autotranscriber therein. It's still not perfect, but it's better than many humans, and far better than bot transcription was <strike>a year</strike> a few months ago.
121+
122+
MdJ: I don't think scribing is enough of a reason to move away from open source tooling.
123+
124+
125+
## Actions
126+
127+
* ACTION: eP to add Solid World to CG calendar
128+
* ACTION: Tom to prepare agenda topic about access control models and law
129+
* ACTION: PAC Look for a person to explore the possibility and discuss it with Jesse, there will be semweb conf before that.

0 commit comments

Comments
 (0)