Finalize instructional information for authors on how to use this material

[davidlmobley]

@mrshirts - I think I volunteered to curate the GitHub side of things. Any thoughts on what I should be doing on here? Things that come to mind offhand are:

Basic repo:

• Make sure there are good README's explaining what this is about, linking to journal, etc.
• Make sure there are examples of using the template (the template itself provides one; we can add more later)

In a new "paper writing as code development" document:

• Likewise give some brief explanations of "paper-writing as code development" and why

In some instructional documents (here or somewhere else? Update: I like here for things which should get attached to their repo, which will be quite a few of these), deal with GitHub practicalities for authors:

• Explain how authors should set up their GitHub repo (protecting master, enabling issue tracker, etc.)
• Explain how to handle versioning and dates of changes
• Explain how to do a release
• Explain the branch-pull-merge/fork-pull-merge models
• Have them protect master
• Give LaTeX formatting tips for easier handling of revisions on GitHub (e.g. one sentence per line)
• Give concrete examples of specific scenarios and handling via GitHub

What else am I missing?

I've added several of the above in #1 (some PR, not that one).

[mrshirts]

Updated a bit in #8

[davidlmobley]

Closed by #42