Meeting minutes
Minutes Review
McCool: Already reviewed the 15th
… pretty straightforward
… still the problem that I cannot edit the minutes, need to talk to Kaz
… but I don't see issues with these minutes per se
… relatively short
… and I am okay with them
… I think what we can do here, if any of us finds anything, we can send Kaz an email
… any objections to approving them?
No objections, minutes are approved
McCool: There are some issues with minutes for the 8th, though, so I think what we should do here is sending a short email to Kaz
… (starts composing an email)
… so let's see if we can find any problems and I will type them up here
… intro was fine, as well as schedule
… "PR 305" is a heading for an empty section, should be deleted
… then we have "New Issue Demo", not sure what that means
… oh, I see, it is regarding the new title, let's change the template, it's confusing
… well, the title "PR 262" could be better and refer to what the PR is about, but I assume this is fine
… finally, "adjourned" is misspelled
… I actually thought there were more problems, but they are okay
… (adds the points mentioned to the email)
… I will send this off and then we can address the points next time
Logistics
McCool: I think we are still on time
… could move use cases up, but there is no reason to do so at the moment I think
… no holidays to consider at the moment, I think
… I really want Ege to deal with this requirements stuff
… Sebastian did not have break during winter time
… any more conflicts? No? Then the schedule is confirmed
PRs
McCool: Checked earlier, seems like there are no new ones
… there is only this one by Ege
<McCool> w3c/
PR 262
<McCool> w3c/
McCool: This one should be deferred until Ege is available
… or will give us feedback on it
Update Readme
McCool: Need to clean this up
… there are two things actually: Referring to the new template
… and fixing the directory structure
… should archive the old directories, moving them to an archive directory
… and then start over
… in a new process, we would use PRs and issues, would not need dedicated directories
… but there are still things we need
… like certain documents we should keep around
… but it is not really active anymore
… so I guess I want to move this and then update the README
… (takes a closer look at the README)
… so in general, I think the README is still fine
… but I think the term extracting is not correct
… we are rather documenting
… but this is not so critical
… the other file we have was what we were working on last time
… (goes to the "USE-CASES" directory)
… I think we should incorporate this into the main README
… (pastes content into the main README file)
… (adjusts the "Contributing" section to document the process of submitting Use Case proposals)
… (adds intructions on how to submit a use case proposal)
… so I think this NOTES.md might need to be moved to a higher directory
… let's make sure the contents of the README are under the right place
… (makes some adjustments to the file)
… just clarifying a few things
… I think one step missing is that, you know, that there is going to be an editor's draft and that we won't publish a note until we have the note process
… then I think we can get rid of parts of the "Review Process" section
… (adds new sections for the review process of user stories and use case categories)
… okay, how does that look?
… okay, actually, this is kind of a mess here
… I think we should put what is written under "Content" into "Other Changes"
… (further adjusts the document)
… so, I think, this (publication status) is just annoying, so I think we can just remove this, so either we refernce the PR or move the link up to the top
… (moves the link to the rendered document further up)
… let's take a look at the current status
… (assesses the rendered version)
… the formatting is a bit messed up, let's fix this
… "the next WG charter" can just be deleted, as the new charter period has already begun
… (deletes the phrase)
… anyone else have objections to this?
… one thing I was wondering was whether user stories should only come from task forces
… but we can leave this open for now
… does the review process make sense here?
… tried to make the terminology and casing more consistent
Jan: Changes look good to me so far, do you want to commit this correctly or do you want to create a PR?
McCool: Will make a PR right now
… oh, I accidentally committed it directly, sorry about that
Mizushima: We need a clarification about what a use case, a user story, and what a requirement is
McCool: I think we have something about that in the templates
… hmm, but it seems as if there is no definition of what a use case is
… (adds a definition to the README.md file)
… (also adds a user story definition)
… (adds a use case category definition)
Jan: Should there also be a definition for "feature"?
McCool: Use it in the sense of assertions
… but left it intentionally vague
… in the future, we should probably link to sections of the document
… individual assertions might be too much
… if everyone is okay with the current changes, I will create a PR for them
McCool: (opens a PR with the changes)
Directory Reorganization
McCool: Will archive the old directories
… (adds a comment with his plan to issue 315)
… will make a PR after moving the directories via the command line
… will do something similar for the REQUIREMENTS directory as mentioned in issue 313
… I think we are almost done
Issues
Issue 304
McCool: I think we have taken care of this, so we can close this one
… (adds a comment)
… like to close this one if that is okay
Mizushim: Yeah
Issue has been closed
Issue Backlog
McCool: We still have over 100 issues open, at some point we need to deal with this
… we also have some pending use cases, which we need to turn into ...
… should not have a 100 issues laying around, should clean this up at some point
… bunch of stuff regarding categories
… probably will be resolved once we have Use Case Categories defined
… next meeting we should probably see how to clean up this backlog
… there is also procedural stuff that we may want to document
… there is also one minor linking issue in the README that needs to be updated
… (resolves the issue)
… will commit this directly
… and create an issue regarding further required changes to the notes.md file
… (opens issue 318 for this)
… I think this all we have time for today, but we now have more than there was before
… okay, move to adjourn
[adjourned]