Meeting minutes
Guests, New Members, IEs
Koster: new member, but not here today
… pending ie requests, nothing happening today
Kaz: still waiting for responses, e.g. registrations
… and to schedule Crris' presentation
Minutes
<kaz> Jun-25
Koster: from June 25, assume people have reviewed already
McCool: for the record the PRs that we resolved to merge last week have now been merged.
Koster: made a resolution to ask for a 3mo extension to work on the new charter
McCool: looks like there is a duplicate of the resolution at the bottom to merge PR #363, delete the one, #2, that now has a broken link
Kaz: fixed
Koster: accept?
… hearing no objections, approved
Quick Items
Schedule for FPWD for TD 2.0
<kaz> TD call on June 18
Koster: discussed in TD TF
… need to publish for TD 2.0 and registry in this charter period
… registry is relatively straightforward
… but for TD, what do we include by September?
… about 6 working weeks between now and then
… there is a list of items to be worked on
… biggest item is the old binding templates document which Ege would like to clean up
… there are other work items
… the registry of course,
… but also document reformatting
… manageable affordances,
… data mapping, etc.
… at this point, we would like to publish the document as-is, then follow up with more work later
Kaz: the TD task force has some basic idea; confirm this direction first
… then TD can think of concrete date
McCool: purpose of an FPWD is to gather input, so I suggest at least adding editor's notes indicating where things are likely to change, e.g. what the plan is
Kaz: I also suggested this in the TD call
… but they need to have more discussion
… as a starting point for the schedule, we should at least capture the goal to publish an FPWD by September
<mjk> Proposal: TD task force is to prepare the TD specification document for publication by the end of September at the latest, final date to be determined by the TD task force, scope to include basic clean-up and editors notes describing the planned new sections and content. The registry document is to be included in this plan.
McCool: need a call for resolution to the WG, and two weeks for review...
Kaz: the resolution can be about the WG publishing by end of Sept, TD TF needs to work back from that to establish a detailed schedule...
<mjk> Proposal: The WoT Working Group shall publish the TD 2.0 draft specification document and first draft of the registry document by the end of September at the latest, final date to be proposed by the TD task force, scope to include basic clean-up and editors notes describing the planned new sections and content.
<mjk> Proposal: The WoT Working Group shall publish the First Public Working Draft of the TD 2.0 specification document and first draft of the registry document by the end of September at the latest, final date to be proposed by the TD task force, scope to include basic clean-up and editors notes describing the planned new sections and content.
RESOLUTION: The WoT Working Group shall publish the First Public Working Draft of the TD 2.0 specification document and first draft of the registry document by the end of September at the latest, final date to be proposed by the TD task force, scope to include basic clean-up and editors notes describing the planned new sections and content.
Start WG/IG structure discussion for the new Charter
Koster: we need to discuss the new Charter, are discussing getting rid of the IG and doing everything in the WG
Kaz: possible, but we decide what is defined by each
McCool: one issue with shutting down the IG is that we might have to shut down or rehome some documents, I know the UC&R doc is published by the IG.
McCool: plugfest is also an IG event, but it could be a CG/WG joint event, which allows for outside attendees
McCool: I did look at this when I split the schedule
Kaz: it would be easier for us to think about what needs to be done rather than concrete text
… after we do that, then we can update the charter (or charters)
Kaz: today Koster just wanted to give a heads-up for that possible direction
Koster: we know we have one thing we want to change, which is to add a provision for user stories in the task forces
… something we are already doing
Koster: also the use-case work is maturing, getting close to a maintenance state
… then there is marketing and plugfest
McCool: marketing is IG too, right?
Kaz: yes, at the moment
McCool: just one comment on user stories, my intention at least was that is could be used for both top-down AND bottom-up requirements documentation
McCool: the intent was to have a procedure that is appropriate for both capturing TF-generated requirements and external feature requests
… the purely top-down approach we had before was not working
Koster: if we only have user story generation requirements in TF, they could do it top-down or bottom-up
… but TF participation is limited to WG members
McCool: couple comments, purely internal requirements can be unhealthy, and there may be requirements that don't fit in an existing TF. However, for external requirements, we need to focus on a process that gives us *actionable* requirements and not just vague scenarios.
Kaz: note however there is no big difference between IG Note and WG Note. We can use github issues to get input from outside the WG.
McCool: it is purely a technical issue. As long as we can collect external input and act on it, that's fine
Kaz: correct. so we don't need to get concerned about which group to handle what :). clarifying the basic schedule is also important as the starting point.
Koster: what do you mean by clarifying?
McCool: I think you need to fill in some intermediate steps in the schedule
Kaz: McCool has started to update the IG schedule and Koster has started to update the WG schedule, so I'd suggest we start with looking at those proposed schedule :)
Koster: editors need to update the schedules along this line
IG Schedule
<kaz> IG Schedule
Koster: so you are saying we need some internal milestones
… for both publications and new charter
WG Schedule
<kaz> PR 1232 - Update wg-schedule.md
Kaz: there is a PR, #1232, that we should look at and update
Koster: we have gotten rid of old dates that have passed, we have to recalculate the dates for the new charter.
Koster: still Security doc updates, but an unknown since no TF
McCool: The security work though is mostly cleanup, but yes, without a TF we can't really work on it
Koster: can merge 1232 and cancel 1231
… it is just cleanup, then we have a basis for future new items
… and the changes proposed in 1231 are included in 1232
Koster: (closes 1231 without merging)
Koster: (merges 1232)
Kaz: request for all editors to update schedule will concrete dates, please
AOB
Kaz: no plugfest call today, but am talking with event team about logistics
Koster: adjourned, no profile or plugfest call today