New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Status of This Document #47
Comments
Before we publish FPWD, I believe it would be helpful to note in the Status of The Document section [1] that the group uses GitHub for issue tracking. Currently, the spec has 27 open issues in GitHub [2]. Some issues are inline in the spec to provide more context around them (and that's fine), thus it may not be obvious to people outside the group reviewing the spec that they should also be looking at GitHub issues. I suggest we keep the "Participate" header too, perhaps make it a list as some other specs have done with appropriate pointers, such as: Participate: Secondly, to set the expectations with regard to maturity, we could state something like: This document is not complete and is subject to change. Feedback from early experimentations is [1] http://w3c.github.io/presentation-api/#sotd |
This new paragraph mentions the provenance of the spec, most important change since publication by the CG, alerts users about missing or incomplete parts, and invites them to check the list of issues on GitHub. It builds on the text proposed by @anssiko.
Added a custom paragraph in Status of This Document section (#47)
The following text has been added to the Status of The Document to reflect that GH is the source of truth for open issues.
Therefore, closing this issue. |
The "Status of This Document" section should be updated before we publish FPWD:
http://w3c.github.io/presentation-api/#sotd
IIRC @tidoust volunteered to take this.
The text was updated successfully, but these errors were encountered: