Skip to content

Commit f1c445d

Browse files
egekorkanegekorkan
authored
Add minutes from joint meeting with WoT CG
This README contains the minutes from the joint meeting with the WoT CG, detailing discussions on various topics including CG activities, Plugfest organization, and collaboration with the WoT WG.
1 parent 7a1db39 commit f1c445d

File tree

1 file changed

+212
-0
lines changed
  • Meetings/2025-TPAC/WG-CG-JointMeeting

1 file changed

+212
-0
lines changed

‎Meetings/2025-TPAC/WG-CG-JointMeeting/README.md‎

Lines changed: 212 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,212 @@
1+
# Joint Meeting with WoT WG
2+
3+
Minutes are copied from WG Etherpad and pasted below.
4+
The slides are provided as pdf.
5+
6+
7+
## Minutes (not corrected yet)
8+
9+
Joint meeting with WoT CG (Ege / Cristiano)
10+
11+
CG Session Slides: https://docs.google.com/presentation/d/1GBIeF4bj2YkZbWiCrPsDkRjui89VoHS_MrXCtbsPyW4/edit?usp=sharing
12+
13+
ege: joint meeting with the CG
14+
... Cristiano should be joining
15+
... starting with brief updates
16+
... trasnparency of the work
17+
... then Plugfest and Liaison
18+
19+
subtopic: What dows the CG do?
20+
21+
ege: no plan for publishing specs
22+
... no official agreement about docs
23+
... but oranizing meetups
24+
... put slides, etc., on GitHub
25+
... video on YouTube also
26+
... Tutorials also have been created
27+
... e.g., underlying technology
28+
... also office hours
29+
... to discuss questions from external developers
30+
... (shows "Updates from WoT CG" video)
31+
... 5 tutorials, 10 meetups
32+
... WoT Week
33+
... Plugfest
34+
... various target areas
35+
... different industry categories
36+
... opensource collaboration
37+
... join the community!
38+
... the video summarizes the CG's activity
39+
... (What works well)
40+
... Meetups have 20+ attendees
41+
... tutorials get reviews and watched regulerly
42+
... (shows channel view information)
43+
... some are more popular than others
44+
... DT's AI topic is popular
45+
... questions?
46+
47+
seb: how many from the WoT main page?
48+
... e.g., the ones from the WoT marketing page
49+
50+
ege: 30000
51+
... pretty good number
52+
... (shows videos listed on YouTube)
53+
54+
ege: (What does not work well)
55+
... office hours
56+
... ok in the beginning
57+
... but i the worst case, simply used as a chairs call
58+
... monthly calls
59+
... very low numbers and not motivated to work on CG tasks...
60+
... maybe need more "concrete" tasks?
61+
... created the "Adopters page", though
62+
... a "starter" page can be created
63+
64+
ege: (Plugfest Organization)
65+
... as mentioend yesterday
66+
... possibly the WoT IG would be closed
67+
... possibly move Plugfests to the CG side
68+
69+
ege: (Liaison)
70+
... discussion during TPAC in Sevilla
71+
72+
-> https://github.com/w3c/wot-cg/pull/227 wot-cg PR 227
73+
74+
-> https://github.com/w3c/wot-cg/blob/bf7739043a14527678b94b7ea3ea8197b7217829/liaisons.md proposed liaisons.md
75+
76+
ege: proposed liaisons.md document about WoT WG collaboration
77+
... e.g., around WoT Binding
78+
... create a non-normative document to be submitted to the WG
79+
... also topic on Plugfests
80+
81+
seb: just a proposal from the CG side
82+
83+
ege: right
84+
85+
seb: make sense to have discussion
86+
87+
daniel: just checked
88+
... IG has 3 TFs
89+
... what about Marketing and Use cases?
90+
91+
ege: possibly
92+
93+
seb: we talked about that yesterday as part of the WoT WG Charter topic
94+
... Use Cases work can be moved to the WoT WG
95+
... on the other hand, Plugfests would have external developers
96+
... so make more sense for the CG to work on that, I think
97+
98+
daniel: ok, tx
99+
100+
seb: anything else?
101+
102+
cris: would support this direction
103+
... wondering about the Marketing work like meetups
104+
105+
ege: Web site maintenance is the big part
106+
107+
cris: yeah
108+
... so wondering about the possible collaboration about that
109+
110+
seb: Marketing on the WG side is hosted by the W3C officially
111+
... on the other hand, the CG is differently managed
112+
... but possible liaison to be discussed
113+
... would initiate discussion on that
114+
115+
kaz: good direction
116+
... wondering about how to proceed
117+
... OK to have further discussion as part of the WoT WG Chartering?
118+
119+
ege: sure
120+
... technically, some of the WG topics could be discussed by the CG
121+
... in a non-normative manner
122+
123+
kaz: good point
124+
... so we need to clarify the procedure about the relationship between CG and WG
125+
126+
seb: regarding the WoT WG Charter
127+
... probably we would have less focused work for the WoT WG
128+
... but that should not mean we (as the whole W3C) should stop discussion on the other topics
129+
... e.g., JSON-LD guys also have been discussing how to work on which topics
130+
131+
mahda: wondering about the license
132+
133+
ege: CGs have their own license mechanism
134+
... (mentions possible collaboration between a WG and a CG)
135+
136+
mahda: maybe the CG is not really interested in writing specs
137+
... probably they're more interested in implementations
138+
... WoT tooling could be a topic, though
139+
140+
ege: some of the CG participants might be interested
141+
142+
mahda: test files, schemas, etc.
143+
144+
ege: but difficult to split the tasks for testing in general
145+
... maybe in some case, it might be possible, though
146+
147+
david: what about use cases work by CG?
148+
149+
seb: no, at the moment
150+
151+
david: we have factory manager, and if we reach out them
152+
... it's just narrative, what is wished to have or hate to have
153+
... what would make their lives better, etc.
154+
... could invite them to the CG
155+
... almost kind of like having one unique group
156+
... could get very strong opinions
157+
... we have to be sure
158+
... facing to external people
159+
... WoT solves offload problems
160+
... but it's not a clear turnkey solution
161+
... actually, node-wot is still kind of difficult to understand
162+
... don't want to use websocket itself, etc.
163+
... would see what external people really would like to have
164+
165+
ege: yeah
166+
... but not sure how to do that...
167+
168+
cris: one comment
169+
... one actual point here is markeing from my side
170+
... explain the WoT landscape better
171+
... I agree WoT for offloading approach
172+
... opensource projects can get people as the necessary effort is less than others
173+
174+
ege: people have more...
175+
... would like to know how to handle WoT?
176+
... they describe their issues on their slides
177+
... pipeline should be clarified
178+
179+
david: yes, pipeline to be clarified
180+
181+
cris: some companies don't allow people to make contribution to opensource projects
182+
... should make the license easier
183+
184+
kaz: we can generate our proposal and then talk talk with the Team :)
185+
186+
david: we have the next step to simply the work
187+
... some of us get together to clarify the current procedure
188+
... we have to try
189+
... we're actually losing participation due to "paper work"
190+
191+
(some discussion about opensource vs legal departments within companies)
192+
(also some more discussion about how to promote the WoT work in general)
193+
194+
seb: wondering about the Plugfests
195+
196+
(some quick discussion about Plugfests)
197+
198+
ege: then that's it for today :)
199+
200+
seb: and I've already done our closing session ;)
201+
... thank you very much for our 6-day meeting!!!
202+
203+
ege: enjoyed Karaoke much :)
204+
205+
seb: but still have October Fest, etc., in Germany
206+
... both of then in Osaka, though
207+
... anyway, thank you very much for your participation, all!
208+
... no WoT meetings next week
209+
... so see you all in 2 weeks
210+
211+
ege: note that there will be a meetup of the CG next week
212+

0 commit comments

Comments
 (0)