Thanks to the folks who joined us yesterday. Notes are here.
Key takeaways:
-
Everyone is encouraged to review the Github project board which captures and sorts all of our open issues into a backlog and a set of proposed items for consideration in Version 3.1. In the months ahead, we’ll be reviewing and revising these lists based on your input.
-
@devin and I will review and affirm the descriptions in the Tools spreadsheet, then he will update the Survey text and then we can circulate that for feedback.
-
I’ll consolidate Devin’s committee governance proposal with @mrshll’s version control proposal into one document for review.
-
Seems like we have a near-term path forward on the Schedule table issue that satisfies @skyleryoung vis-a-vis the 2-1-1 network. And also potentially a proposal for longer-term upgrade that can be added to the backlog. Follow the thread.
-
I have voiced my dislike of the term “non-normative” for guidance material that is not formally part of the standard – and I proposed “informative” as an alternative – but the developers in this conversation seem comfortable with “non-normative,” and I recognize that the documentation is for developers not English majors. I’d like to hear whether others have an opinion about this, but for now I expect we can keep it and just hone our explanation of what we mean by the phrase “non-normative” to make it clear that it means “this is something we do think ought to be done, even though the word we’re using to say that seems to literally mean the exact opposite.”