Meeting minutes
minutes review - Nov 30
<kaz> Nov-30
Ege: last meeting, PR on contacts, article in embedded.com by Phillip Blum, Wiki redesign, wikipedia, community comm/chats
… any objections to publishing?
… none, will be made public
embedded.com article
<kaz> Issue 235 - Feedback for embedded.com article
Ege: issue #235
Ege: I have provided feedback, but not published yet... see issue for link to review
McCool: ok for this to be a public link?
Ege: yes, ok, author's version allowed
Ege: pls provide feedback, but will want to close next week
… no real deadline, but would like to close in a week
easy issues
Ege: have identified some issues I think we can close quickly
Issue 94
<kaz> Issue 94 - Missing W3C in IoT Wikipedia page
Ege: first, there is an IoT wiki page listing standards and organizations
… for TD have pointed to wiki, for Discovery etc. point to TRs (which point to WD for now)
… have posted this to the IoT summary index page, edit was accepted
<Ege> https://
Daniel: should we have a page for Discovery, etc?
McCool: want to wait until after CR, also maybe we should have a master WoT page first; the current one needs work
Issue 228
<kaz> Issue 228 - Deleting Table of Contents looking section from Wiki pages
Ege: done, think we can close
McCool: I did do some tweaks, to security and discovery
Ege: that is a new issue for that, see #231
Ege: closing #228
issue 203
<kaz> Issue 203 - [website] Possible restructuring of website
Ege: contact page, all subtasks done, propose closing
… some other issues created for new tasks
Ege: closing #203
… continue with #234
discussion
issue #236
<kaz> Issue 236 - Have Regular CG Meetings - OpenDay
McCool: propose openday
McCool: in general, CG events should be CG events
… if we are going to have an openday, we should figure out how to use it
… and also, using the CG page for something useful rather than just being a dead page
Kaz: if you mean the "WoT CG" by "CG" here, we need to reboot the group's activity first
McCool: two problems here; general problem of CG, and specific problem of OpenDay promotion
McCool: so wondering if there are mechanisms for promoting events, one of which could be the OpenDay
Kaz: can reboot, need active chair and participants
McCool: we should consider the CG as one of several mechanisms, and it is more "official", so
Kaz: need an active chair, currently Dave Raggett is the chair, but should not really be a staff member
McCool: think we should at least delete the obsolete content, point at new pages
… and community events should officially be CG events
… can put myself forward as chair
… should plugfest be a CG event?
Kaz: currently plugfestis IG event
McCool: ok, let's leave plugfestalone, but openday makes sense as CG
McCool: my idea is not to do things we are not doing already
McCool: probably should create a different issue about rebooting the CG
Kaz: mm too busy?
Ege: I can do it
McCool: will have to follow procedures, get nominations, have resolution
McCool: we have at least a few here...
Daniel: I support ege
Mizushima: I support ege
Philipp: I support ege
McCool: I support ege
Kaz: technically dp is in the same org as ege
McCool: ok, let's bring this up in the main call
issue #231
<kaz> Issue 231 - Add Description to Top of Each TF Wiki Page
McCool: updating wiki to include description (can be copied from web page)
… see security and discovery for a template
Ege: ok, let me add a list of task forces pages to work on
… and a link to an example (discovery)
McCool: note also the link the main call has been broken out in the TOC
McCool: I will update the Marketing and the Main wiki pages
three issues from McCool
<kaz> Issue 79 - Tutorials should be easy to find
Ege: first one 79 is about tutorials being hard to find
McCool: well, they are still hard to find
McCool: they are not linked from obvious places like documentation or developers
… they can hosted elsewhere, but we should index them on the web page
Ege: should we rename documentation?
McCool: could go into menu bar, or first thing under Developers
McCool: perhaps rename the current documentation page as "Explainer", add a separate "Tutorials" page, and then a master "Getting Started Guide"
Daniel: for now we can just add a couple of bullet points to the Developer's page
McCool: sounds good to me
… later on we can discuss doing something more complicated
Ege: also the developer's journey
McCool: relates to getting started guide, let's look at that next time
<kaz> [adjourned]