Hi Lucas, Thanks for the reply. Given that reply, I think it would make sense for the wg to see a more worked description of how the contribution mechanics would work. At the moment, updating the wiki requires certain permissions for the repo; if the end state after you've worked this out is functionally the same, then this change doesn't really improve things and can probably be safely put aside. If there is a way to do this that allows "useful grass roots contribution and maintenance" without similar permissions, it would be useful for the working group to understand it when making this decision and also to document that for other groups that might have similar issues.
Just my personal opinion, of course, Ted Hardie On Tue, Jul 30, 2024 at 10:36 AM Lucas Pardue <[email protected]> wrote: > Hi Ted, > > On Tue, Jul 30, 2024, at 10:15, Ted Hardie wrote: > > Hi Lucas, > > I think I am missing something fundamental here: > > I'd like to propose that we migrate away from using GitHub wikis for all > repositories in the quicwg org, towards using the quicwg.org pages. This > is intended to improve the contribution and change process. It is hoped > that this will also improve the discoverability of content on the wiki. > During any migration, content will continue to reside on the wiki. > > There is nothing on those pages that I could see that indicates how you > can propose a change to the pages. If the aim here is to enable "useful > grass roots contribution and maintenance.", I think it would be appropriate > to say more about how this migration does that, because I don't understand > it. The quicwg website doesn't even indicate how to contact the > maintainers, so it's hard to see how it enables a grassroots effort. > > Indeed, the current quicwg.org has been mostly operated by the chairs, > with a small number of contributions from those that might have stumbled on > the repo. > > Consolidating useful information to a single place would come with > improving the documentation on how to contribute, whether it be an issue or > a PR to the repo [1]. And of course, we would cover the requisite notes on > contribution code of conduct and note well. > > Cheers > Lucas > > [1] https://github.com/quicwg/quicwg.github.io > >
