Jordan Kasper
Jordan Kasper
## 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...
Users visiting the site might want to see some of the neat projects that have been open sourced within the DoD. It would be good to have a snapshot of...
## Content I would like the instructions on "how to open source" to include information on how to use the Code.gov "help wanted" labels so that GH issues can be...
## Feature Right now the only way to see projects on Code.mil is to look at the `code.json` file. I would like to have a user-friendly view of the projects...
I would like to provide specific language and guidance for DoD organizations that are still negotiating a contract with a custom software developer such that delivery can be made via...
This is more about the code repo itself (and related docs), not the policy side of it. We could base this on GSA's (which was worked on by the Code.gov...
This is the guidance coming out of #67 on FOIA, records retention, and git history rewrites. This language needs a little review, but I'm generally in favor of it. @shawoods:...
## Expected Behavior I would like to be able to list external JSON files that other groups within my agency are maintaining so that the central office maintaining the primary...
## Expected Behavior I would like to add more than one contact name / email per released project. This is mostly to allow for both an administrative and technical contact...
I would like to have templates for submitting issues and PRs. We could look at [code.mil](https://github.com/Code-dot-mil/code.mil/tree/master/.github) for how they do it if we want.