Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation on how to do good OSS documentation #240

Open
jordangov opened this issue Sep 6, 2018 · 17 comments
Open

Add documentation on how to do good OSS documentation #240

jordangov opened this issue Sep 6, 2018 · 17 comments

Comments

@jordangov
Copy link
Contributor

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
Copy link

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

@jbjonesjr
Copy link

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

@jordangov
Copy link
Contributor Author

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

@jbjonesjr
Copy link

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
Copy link

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

@jordangov
Copy link
Contributor Author

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

@jotasprout
Copy link

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
Copy link

@jordangov Is it okay to combine these?

@jordangov
Copy link
Contributor Author

Fine by me

@jotasprout
Copy link

Working on this and #180 today.

@jotasprout
Copy link

Where will this writing-good-documentation page live in the site? Where do there need to be links to it? Might it fall between "How to Open Source" and the FAQ in the nav?

jotasprout added a commit to jotasprout/code.mil that referenced this issue Oct 8, 2018
Includes guidance for README and CONTRIBUTING pages, standards for Issues and Pull Requests, and instructions for applying and creating labels for issues.

Resolves: Code-dot-mil#180, Code-dot-mil#240
@jordangov
Copy link
Contributor Author

Suggest something! We're pretty open, and will comment if it doesn't look right.

@jotasprout
Copy link

I like the idea of having it "beneath" How To Open Source with a similar submenu -- how do you do that with YAML? I could copy and alter the one for HTOS if you can direct me to it.

@jordangov
Copy link
Contributor Author

Hmm... I think this is a lot of content to nest "beneath" How to Open Source. In any case, that's a single page with jump links, and I think this would be a separate page, right?

@jotasprout
Copy link

I don't mean inside the How to Open Source menu as a sub-item ... I mean between "How to Open Source" and the FAQ in the left nav (beneath HTOS and above FAQ) ... so it would be a separate page with jump links of it's own.

@jordangov
Copy link
Contributor Author

Ah, yeah...
So all of the main nav is specified in the _data directory: https://github.com/Code-dot-mil/code.mil/blob/master/src/_data/navigation.yml

But the side subnav is specified in the page's md file itself (see the top of the "How to Open Source" page: https://github.com/Code-dot-mil/code.mil/blob/master/src/how-to-open-source.md)

@GrooveCS
Copy link

GrooveCS commented Sep 1, 2020

Is this still an Open Issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants