Meeting minutes
Minutes
McCool: Review of last
meetings minutes
… last meeting before the face to face plugfest,
next week is canceled because of this.
… Minutes were accepted.
Meeting Logistics
McCool: Canceling next
week because of the plugfest.
… The 4th of Dec we will have a
meeting
… Canceling the 18th because of vacation, Christmas
and New Years
… We will still have a meeting on the
11th.
Schedule
McCool: Charter is till
Oct, so less than a year left
… need to keep the process going for gathering
requirements for TD
… We did target March for our publication, but are
we ready for a publication then.
… We need to capture as many use cases as possible.
Do we call this done or move it forward some weeks.
Ege: Yaml templates need to be added so the use case capture, so move to Dec
McCool: Issue with
March is we loose a lot of Jan, so it might not be perfect. So we
might want to do two publications later on to update it.
… Moving its date to Sept, to clean it up and
gather the rest of the UC.
Ege: Mid Dec for TD features might be difficult
McCool: rather try to get things done and recharter with new goals
Mizushima: Looking to allow us to start accepting the use cases.
McCool: After we add
the new structure we can allow new acceptance of use cases.
… New PR created with changes to be reviewed in the
next meeting
Pull requests
McCool: made an update
to allow categories and sections to show up in the table of
contents.
… Changed the overall description to show a common
property
… for requirements user stories are up a level, and
reformatted the details to have a what and why
… When we make the yaml template we will make it
clearer
Ege: approves of the changes
McCool: cleanup needs to be done to move user stories to the end and make things more generic.
McCool: Asking for
approval to merge PR 306
… No objections so merged
<McCool> https://
McCool: Need a new
issue for Yaml for use cases that already exist.
… Starting new issue https://
… Asking for approval of the outline.
Mizushima: Looking for an addition of an example section
McCool: do we need the submitter as part of the template, or is the github username enough
Ege: adding an others section to list other parties that are involved in the use case not only the submitter.
McCool: Assigning the task to myself, please add comments on it so we can discuss next meeting
PR Review
McCool: would like to clear out the backlog so we can reformat the use case doc. This way the current PR's will not break
McCool: PR-240 to
update the version of the document to the new pages
… reviewed the PR and found we need to update it to
the RFC since its RFC9556.
… Seems that this PR is incorrect and needs some
description removed. So merging it in then creating an issue to fix
the issue with not using respec refs
… Starting new issue https://
… Merged 240 after asking for approval with no
objections
… PR-245 moving it to the editorial Label. This is
not really a UC.
… This brings up a point that UCs can become
obsolete. We need to find a way to mark these as
completed
Ege: what is the context of the removed line
McCool: We should add a
marker like Resolved to the text instead of editing the text from
the UC. This way we have a history when stuff is resolved
outside
… Merging it to get the PR closed, and will find a
better way to show when items are resolved rather than deleting the
comments.
… New Issue https://
… Merged PR245 after no objections
Ege: PR 248 is updates to things that are already done
McCool: Ok with merging
this as long as its optional, since this has to do with constrained
devices.
… Merged PR-248 after no objections
<McCool> https://
McCool: PR-255 creates
a table to analyze all the different use cases and put them into
categories and are linked in the UC categories section.
… The blanks need use cases and the Dashes mean a
category
… Removing Mahda from the Todo so we can work the
issues
… Merging PR-255 after no objections