Requesting GitHub repos (and using wikis)

[stuartpb]

I'm about to propose a couple of these, so I'm starting out with a meta-issue for describing/discussing the overall pattern.

Basically, a GitHub repo is a great way of encapsulating an initiative within the WICG: it gets a README for an introduction / sort of meta-charter. Other files in the repo can be used for other documents whose content should be curated, with changes discussed in pull requests.

It also has its own wiki that can be edited by any user via GitHub, for gathering non-prescriptive informal thoughts together.

[stuartpb]

I was initially going to say "users should be able to request the WICG admins create repos for them and they just do so casually", but now I'm realizing it'd be better for users to just create the repo under their own username and then file an issue requesting the WICG admins to adopt the repo (changing the owner to @WICG), as that is much more in the non-blocking don't-let-gatekeepers-stop-you-from-doing-your-thing spirit of the group.

[stuartpb]

I guess the adoption thing is basically like "intent to migrate", but without all the stuff around browser implementation (because I'm talking about non-tech initiatives here).

[marcoscaceres]

This is the model (adopting) we have been using. I'm not sure what action to take with this issue, so closing.

[stuartpb]

The action to take on this is to have this model documented somewhere - is it documented somewhere? Where?

[marcoscaceres]

Ok, we should document that here:
https://github.com/WICG/admin/blob/gh-pages/README.md

[marcoscaceres]

@yoavweiss, can we add the "2+ LGTM should be needed to spin up repo" requirement as part of this.

[travisleithead]

I think this is pretty well documented on the wiki https://github.com/WICG/admin/wiki/Process-to-transfer-a-repo and in the README.md which links to it. Closing this issue.