– DRAFT –
CG Internal Meeting 1

<citrullin> https://www.w3.org/2022/Talks/0322-tools-ka/#6

next CG event

ege: what kind of next event we would like to do?
… we can do one about a specific topic
… we can even create an event for a summary about the current wot spec
… or we can ask other CG members to present their own projects
… any other topics to discuss?

citrullin: I can present what I was supposed to present during TPac
… a temperature sensor on RIOTos
… with another node that display information
… it is a showcase of opensource solutions

cris: we can always present node-wot

citrullin: focused on new features

cris: right

citrullin: we can do this once in a while

ege: it makes sense

ege: do you have contact with the firebase node-wot implementation
… ?

cris: not me directly

daniel: he is pretty active on github
… probably is from japan

ege: somebody from the japanese CG knows him ?
… seems no

mizushima: no sorry

ege: do you have suggestion about the topic area?
… ok then let's move on

Collaboration with IG

ege: we want to promote a single image of the Web of Things to the public
… we want to have continuity between WoT groups
… first we have to reach an agreement
… then propose it to the WG and IG
… and finally discuss with the W3C Management
… in the current setup CG is not even mentioned
… but there are some issues
… like the website is under IG/WG but resources like tutorials, dev tools are not part of WG or IG work
… we have a maintenance issues
… onboard is hard
… can't invite people easly to provide use cases and ideas
… there are no modern tools for discussion and idea sharing

<ege shows the new setup relation graph>

discussion

ege: what is the goal of the collaboration ?

kaz: remember that community groups are free to do anything they want. WG and IG are regulated under the W3C process document
… my suggestion is, like with the Japanese CG, to start with a simple topic
… it easier than starting from transferring ownership from Wg/IG website.

ege: we are starting work on it
… but now there is the question where to host these resources
… should we hand over to IG website
… or host ourselves (causing a split in the community)

kaz: current issues slide is misleading
… We should rather start with the discussion on what kind of activities to be done by the CG directly.
… it makes more sense to start over with an activity list

ege: we sort of have it but we decided to focused on the collaboration first

kaz: Maybe it would make sense to think about what kind of activities or categories of the work items to be done collaboratively with the WoT IG/WG like Mizushima-san described about the WoT-JP CG during the TPAC meeting, e.g., Outreach, Deployment, Use Cases and Translation..

<Mizushima> about WoT-JP CG

lu_zero: it is very difficult to get an overview of the WoT

ege: ok
… the repository list is not clear either

citrullin: I can mirror repositories

ege: I liked kaz suggestion
… let's focus on this point
… what should we do

ege: should we create task forces inside the CG?

kaz: You don't have to create TFs within the CG, but you need to identify what kind of tasks to be done by the CG. If needed, you can create a dedicated TF for each task item later.

cris: it might be interesting to create awesome-wot repository

citrullin: there is already one

cris: ok, another thing about activities I think one of the goal should be onboard developers

ege: ok true
… but about activiities
… event organization
… and create developer community infrastructure

citrullin: targetting events

ege: we have already a lot of ambitious goals

cris: I agree, but now the next step is to decide the image to use
… are we CG? are we representing WoT ?

citrullin: simple answer we can represent ourselves or our company

ege: so which link should we give people

citrullin: we can just give them two links
… in my previous experience
… we can just make it clear that is a community effort

cris: we should try to have a single image

citrullin: it would be nice
… but the problem is, we can't enforce it

cris: I agree, but it wouldn't be better to give people the means to claim to be under the same umbrella?

kaz: From my viewpoint, the policy is clear enough, so I'm not sure what is the question here. If you (as a participant in the WoT CG) would like to represent the WoT CG at some conference, you need to make a

citrullin: so, as long as it is clear that our resources are not from the w3c wg/ig, we are fine

kaz: for example, if you want to do a presentation at a conference
… you need to have a resolution from the CG

kaz: regarding the WoT icon, it is already used
… and you can use it

ege: I think we should

<Ege> https://github.com/w3c/wot-cg/blob/main/wot-ig-collaboration.md

<Ege> https://github.com/w3c/wot-cg/discussions/6

ege: before closing I set up a github discussion to continue talking about it
… also citrullin why do you want to use another logo?

citrullin: The same logo give to the user the false impression to be in an official wot webpage

ege: Japanese CG use it

cirtrullin: not sure

<kaz> resolution by the WoT CG. On the other hand, if you (as a participant in the WoT IG/WG) would like to represent the WoT IG/WG at some conference, you need to make a resolution by the WoT IG/WG.|

cris: why don't we do just a variation of the current logo?

citrullin: ok if everybody is on the same page

<kaz> s#resolution by the WoT CG. On the other hand, if you (as a participant in the WoT IG/WG) would like to represent the WoT IG/WG at some conference, you need to make a resolution by the WoT IG/WG.|##

ege: we'll send updates for the next event

[adjourned]

<kaz> s#, you need to make a#, you need to make a resolution by the WoT CG. On the other hand, if you (as a participant in the WoT IG/WG) would like to represent the WoT IG/WG at some conference, you need to make a resolution by the WoT IG/WG.#