- From: Aram Zucker-Scharff via GitHub <sysbot+gh@w3.org>
- Date: Thu, 31 Mar 2022 23:24:42 +0000
- To: public-patcg@w3.org
Ok, I have made a number of alterations here to try and incorporate requirements and objections stated on this thread and acknowledge that this may be too much process. It may make sense to remove lines 275 through 312 and not deal with any question of deciding what is in or out of scope, except I would like to preserve some mechanism to remove irrelevant proposals from even a basic space. The new changes aim to do as follows: - Create an open space in the form of a GitHub organization (as suggested by @ekr) that any author can bring a document for coverage by IPR protections that the W3C provides that would generally be considered an "incubation" space for relevant proposals. - Create a mechanism where the community group may consider these proposals and list them in the `proposals` repository as being in scope of our work. - Create a mechanism where the community group may eject a proposal as being irrelevant to the work of the community group. - Make it clear that proposals in that space are not in any way blessed by the community group or its participants. (Towards @martinthomson's concerns.) - Create a clear distinguishing set of features in that: it is not clear that the work is `likely to lead to independent interoperable implementations`; that it may not provide an acceptable web experience for users; and that it may not even follow our group or W3C principles. (Towards @martinthomson's concerns.) - Make it clear that incubation is not a guarantee that a proposal will be raised to adoption. Clear options for alteration: - Remove the "in scope / ejection" process - Add a step where a proposal must be supported by at least one member of the group belonging to an organization different from that proposal's author (similar to WICG) I agree that this will require some discussion by the group in the upcoming call, but do the participants on this thread believe that this new process has moved the PR towards a state that could be acceptable? Please feel free to bring forward suggested changes or corrections. -- GitHub Notification of comment by AramZS Please view or discuss this issue at https://github.com/patcg/patcg.github.io/pull/7#issuecomment-1085226233 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 31 March 2022 23:24:43 UTC