GitHub organizations

[aridyckovsky]

Is your feature request related to a problem? Please describe.
When creating a GitHub organization, there are many decisions made that can impact future productivity for participating in the organization's work.

Describe the solution you'd like
A clear set of conventions for GitHub Organizations, including naming, descriptions, pinned repositories, which templates to use or not, how to handle licensing and lab-wide docs like .github community health details, public vs. private repos, etc. Should also have a potentially separate section on permissions levels (read vs write vs admin vs owner).

Additional context
Can use GitHub official docs, but needs tailoring to specified lab audience.

[aridyckovsky]

This issue in particular could use some "what worked and didn't work for me" as a PI starting on GitHub context. Potentially @psokolhessner you have some ideas from your experience?

[psokolhessner]

I think my major takeaways would be to a) do it early, b) get everything/everybody on board, c) do it with support (which is also [b]), and d) try to make consistent, top-level choices e.g. about licensing, so everyone knows what to do. Beyond that, think of it as an extension of your other online presences (website, twitter, facebook, etc) - and so make it consistent with those, and create it as if lots of other people will be crawling your stuff, even if you doubt they will.