Skip to content

Add documentation on how to do good OSS documentation #240

Open

Description

@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.

Activity

  1. jbjonesjr commented on Sep 6, 2018

    @jbjonesjr
  2. jbjonesjr commented on Sep 6, 2018

    @jbjonesjr

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

  3. jordangov commented on Sep 6, 2018

    @jordangov
    ContributorAuthor

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

  4. jbjonesjr commented on Sep 7, 2018

    @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. 😉

  5. jotasprout commented on Sep 20, 2018

    @jotasprout

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

  6. jordangov commented on Sep 23, 2018

    @jordangov
    ContributorAuthor

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

  7. jotasprout commented on Sep 26, 2018

    @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.

  8. jotasprout commented on Oct 3, 2018

    @jotasprout

    @jordangov Is it okay to combine these?

  9. jordangov commented on Oct 3, 2018

    @jordangov
    ContributorAuthor

    Fine by me

  10. jotasprout commented on Oct 8, 2018

    @jotasprout

    Working on this and #180 today.

  11. jotasprout commented on Oct 8, 2018

    @jotasprout

    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?

  12. jordangov commented on Oct 9, 2018

    @jordangov
    ContributorAuthor

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

  13. jotasprout commented on Oct 9, 2018

    @jotasprout

    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.

  14. jordangov commented on Oct 9, 2018

    @jordangov
    ContributorAuthor

    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?

  15. jotasprout commented on Oct 9, 2018

    @jotasprout

    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.

  16. jordangov commented on Oct 9, 2018

    @jordangov
    ContributorAuthor

    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)

  17. GrooveCS commented on Sep 1, 2020

    @GrooveCS

    Is this still an Open Issue?

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions