Use ARL policy as a starting point for code.mil
See original GitHub issueMuch of the discussion here to date has been around licensing. There are many other practical considerations about open sourcing.
I am interpreting the scope of this project to include everything DoD project managers need to open source a project. Therefore those practical considerations are in scope.
I am working on PR #92 to start a document for those items.
DDS employees are welcome to call me. I want to make sure I am taking this is a direction you approve. It will be very helpful for me to understand the nuances of what contributions you are likely to accept.
Work plan
- Copy ARL policy to this repository on the
gh-pages
branch- Note / cite that origin is ARL
- Update style as necessary (ARL uses title case for headings, I will use sentence case for headings as per https://standards.usa.gov/design-principles/)
- Turn it into a SIMPLE web page that can be hosted at code.mil
- Use styling & templates per https://standards.usa.gov/page-templates/ from 18F
- Mention DRAFT/DISCUSSION status of the document
- Use Jekyll to convert markdown to html
- Replace all mentions of Army Research Lab with DoD
- Replace tone of document from “This is official ARL policy” to “DDS recommends you do this”
- Offer DDS assistance to other DoD agencies in implementing these recommendations
- Add links to other US Federal Government policies on publishing source code
- Update vague references to “DoD Legal” to be “your agency’s legal department” and similar.
- Change RFC 2119 wording “MUST”, “SHOULD”, … (which is appropriate for policy) to “should” and other language that is appropriate for a recommendation
- Check all links, footnote references and glossary entries
- Reword any language that appears like Defense Digital Service is speaking on behalf of DoD, because they’re not
- Clearly describe the role of the Defense Digital Service in supporting the DoD in the summary
- Include Defense Digital Service contact information and specific points of contact for this project
Acceptance plan
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (10 by maintainers)
Top Results From Across the Web
Frequently Asked Questions - ARL DSRC - HPCMP
Frequently Asked Questions about the resources, services, and policies at our center and within the HPCMP.
Read more >New Employee Handbook - Army Research Laboratory
www.arl.army.mil ... Initial Occupational Health Screening / Physical Examination 28 ... Note: ARL policy requires that a Form 1 be completed.
Read more >MILSTRIP.pdf - DLA
Establishes procedures for the DLA Distribution. Standard System (DSS) to provide supply status transactions (DLMS 870S/legacy. MILSTRIP ...
Read more >Code of Best Practices in Fair Use for Academic and ...
ARL, in conjunction with American University's Center for Social Media and Washington College of Law, developed a series of informational videos related to...
Read more >DoD Announces the Launch of “Code.mil,” an Experiment in ...
The Code.mil URL redirects users to an online repository that will house code written for a range of projects across DoD for individuals...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@shawoods Take a look at ARL’s stuff, and jump in where you want to. I expect that there will be significant work on the
develop
branch shortly.#92 is merged, closing this issue. Discussion continues at #126 which gets this code published to the world wide web.