Document and consolidate branches

[dushoff]

Do we have a place where I can understand which branches are active, which branches I'm allowed or encouraged to edit, which branch is currently serving the schedule, and which branch we would like to have serving the schedule when temporary things are merged (hint for this last one: gh-pages)? Can anything be merged (or just nuked) right now?

[pearsonca]

There is not.

I'm not sure off the top of my head what can be merged / deleted now.

The practice that I prefer (because I've found it to work well) is issue => use the create a branch feature (right side, just above "unsubscribe"). That makes a branch associated with the issue, which then gets merge-deleted when the issue is resolved.

E.g., what I think would address this issue would be some mix of updating the (github) wiki + a .github/CONTRIBUTING.md file or the like. Basically, the typical practices for capturing how we work on the repository. I think that would be mainly changes to ICI3D.github.io repo, but then some knock-on changes to workshop repos to refer back to that guidance.

[dushoff]

did you use cleanpages? Can I nuke it? What branch is serving the current MMED site? Can it be merged into gh-pages?

[dushoff]

Carl is the only person who even knows which is the active private and which is the active public branch here. This is what Bolker calls the "bus problem" (as in, "how screwed would we be if X got hit by a bus"). Please make sensibly named primary branches and delete decoy branches (e.g., gh-pages unless it is the main pages branch). Or ditch the branch-page paradigm and just serve web content from docs. The main branch would ideally be called "main".