[meta] Publish Candidate Recommendation #276
2 participants
@anssiko, I agree that #202 (Presentations without communication channel) can be considered a new feature and defered to v2. I updated issue labels accordingly.
Although not explicit in the CR requirements, publication as CR normally implies that known technical issues have been addressed and more generically that the group has solved all issues that could lead to normative changes in the spec. We also need to demonstrate that the specification has undergone wide review.
As such, I would add at least the following issues to the list of issues to be solved before CR:
- #162 Evaluate Presentation API against the Media Accessibility User Requirements spec
- #163 PresentationSession should have stream interfaces!
- #218 Possibility for a character to be interpreted differently depending on locale
- #241 bufferedAmount property on PresentationConnection
- #253 Have the receiving browsing context generate the presentation identifier?
- #254 When is the first presentation connection created in the receiving browsing context?
- #269 Only allow one PresentationAvailability per PresentationRequest
- #273 PresentationConnectionClosedEventInit.message needs to have a default value
Some of these issues may need to be discussed at the F2F, but most of them simply need some sort of "PR" (Pull Request or Proposed Resolution). Essentially, I'd like to propose the same game as in January: let's kill some issues so that the spec may be published as CR shortly after the F2F!
As suggested by @tidoust, let's apply the proven formula from January to the above issue list.
Anyone is free to pick any issue from the above list, address it by submitting a PR, or by suggesting text in the issue comments to be integrated. The results of this collaborative exercise is to be summed up at the F2F.
I updated the first comment in this issue to link to the known CR blockers, split in two buckets: (1) issues we think can be addressed before the F2F, and (2) issues that require F2F discussion. Please see:
We're making good progress in addressing the first bucket of issues -- contributions from all group participants are welcome!
The Candidate Recommendation (CR) publication of the Presentation API is looming in the horizon. By publishing a CR we:
While we're well on our way to satisfy the CR requirements, there are some things to be completed before we can hit this significant milestone, namely:
Resolve the open issues we can address before the F2F (thanks @tidoust):
#162 Evaluate Presentation API against the Media Accessibility User Requirements spec#163 PresentationSession should have stream interfaces!#218 Possibility for a character to be interpreted differently depending on locale#241 bufferedAmount property on PresentationConnection#253 Have the receiving browsing context generate the presentation identifier?#254 When is the first presentation connection created in the receiving browsing context?#269 Only allow one PresentationAvailability per PresentationRequest#273 PresentationConnectionClosedEventInit.message needs to have a default valueResolve the open issues tagged for F2F that likely require F2F discussion:
Provide a draft test suite to be able to say we have "document[ed] how adequate implementation experience will be demonstrated". Please get in touch with the Test Facilitator @louaybassbouss to contribute and help.
With continued active participation we're trending toward hitting CR after the May F2F, before the vacation period.