- From: Aram Zucker-Scharff via GitHub <sysbot+gh@w3.org>
- Date: Fri, 11 Mar 2022 20:07:40 +0000
- To: public-patcg@w3.org
I do see that mandate in WICG, though I personally find the fracturing of proposals that are arguably directly related to our mission difficult to manage and have heard that complaint from others. I can see the solution @bmayd suggests making sense, but my sense is that @martinthomson's objections are just as valid if the proposal enters WICG as it is if it enters here. So I'm not sure that having it noted here and living in WICG is any more fairly addressing his concern, just sort of moving it out of our domain. (Unless @martinthomson says otherwise) As @ekr noted in the meeting: > But we need a word for “work item for the group”, not just a thing being talked about. And it seems to me the lack of that being established as something significantly different from "intended to become a Community Group Report" is going to be a recurring problem? Better to resolve it in such a way that we feel it settles this case not just as a one-off but as a process if we can? I will note that having it in this repo as a submodule would make it a clear candidate for discussion without portending a more formal state. It would also give it a clear and easy to use link and note the current repo as the "official" repository that can help sort the confusion about personal repositories while giving it its own issues and space in it's current location. Then, should that space progress the proposal to a state where we have consensus that it is ready to become the subject of a formal report, we can bring it in as a full repo inside the PATCG org. I think then the only thing we need is to assure the language makes this process clear in the README here, and, if people feel the charter doesn't sufficiently cover this use case, we could discuss an amendment. -- GitHub Notification of comment by AramZS Please view or discuss this issue at https://github.com/patcg/proposals/issues/4#issuecomment-1065472139 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 11 March 2022 20:07:42 UTC