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. thanks, Ted On Sun, Jul 28, 2024 at 5:23 AM Lucas Pardue <[email protected]> wrote: > Hi folks, > > During the standardisation of QUIC, we made a lot of use of GitHub's wiki > capabilities in the primary base-drafts repo that housed all drafts at that > time [1]. This was a community effort. Everyone had write access and the > wiki tracked the leading edge of development closely. > > Since the RFCs were published things have matured and stabilised. We've > seen several new documents get adopted and worked on in their own repos. > Yet the base-draft remained the spiritual centre of wiki, especially when > it came to listing implementations or tools. Even if they weren't updated > as frequently. > > Unfortunately, last year the wiki was vandalised and needed restoration. > At the same time, to prevent further vandalism, we restricted access to > wiki edits to GitHub accounts that had certain repo privileges. However, > that's had the unfortunate effect of preventing useful grass roots > contribution and maintenance. Further investigation into this area has > indicated to me that the GitHub access control approach and UI for wikis is > not suited to our regular ways of working: issues and pull requests from > anyone, merges by authorised users only. > > The quicwg.org homepage is intended to be an easy-to-use hub for the QUIC > WG. It's also powered by GitHub [2]. It links off to the wiki for some, but > not all, content there. > > 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. > > I've already floated the idea in the QUIC slack, and the general sentiment > is in support of doing the migration. So I'm opening up the proposal to a > broader participant list. I'm especially interested if you have objections, > or if you have thought or ideas about how best to migrate and present the > content (especially if you'd like to volunteer on UI design or other > related matters). > > Cheers > Lucas > > > [1] https://github.com/quicwg/base-drafts/wiki > [2] https://github.com/quicwg/quicwg.github.io > >
