Add documentation on how to do good OSS documentation

[jordangov]

Feature

We would like to have better documentation on how to create good open source software documentation as guidance for Department organizations wishing to open source things. This should include things like relevant sections of a "contributing" doc (not just a link to an example), how to write and review PRs, good commit messages, how to write a good GH issue, etc.

Page(s) Affected

This could go on https://www.code.mil/how-to-open-source.html ("How to Open Source"), but it could live on it's own page, linked a couple of places.

[jbjonesjr]

helpful resource: http://opensource.guide/home/

[jbjonesjr]

also i have a bunch of stuff here: https://github.com/jbjonesjr/open-source-docs YMMV

[jordangov]

w00t! Thanks Jamie. Ya know, PRs welcome as well. ;)

[jbjonesjr]

don't want to take away from that great help wanted opportunity.

and anyway, i already signed myself up to make a new code.gov API client, so i'm contributed out right now. 😉

[jotasprout]

I'd love to bring my tech writing experience and help out with this.

[jordangov]

I think this is related to #180, it's all about how to maintain an OSS project.

[jotasprout]

Okay. I'd like to take this and #180 on simultaneously so I can work on them together since issue 180 will be a part of this issue.

[jotasprout]

@jordangov Is it okay to combine these?

[jordangov]

Fine by me

[jotasprout]

Working on this and #180 today.