Model policies / process for publishing open source projects?

[David Cantrell]

Howdy all,

I have an org (mil) looking to publish some (extremely simple) code examples and templates online so other mil orgs can take advantage of them without needing to manage access to any sensitive source repos. There's nothing sensitive in the code at all so github seems a perfect fit, but that would entail establishing an official account, building internal policies regarding account ownership and boundaries of use, policies on what can or can't be published, etc.

Are there any lists of what DoD / Air Force policies apply to the act of reviewing and publishing itself? I'm looking for some helpful guidance in navigating the process of (1) setting up this type of internal process so we can have good policy in place to help reduce the burden when more people ask "can I also do X" which is inevitable, and (2) ensuring we check the right boxes along the way so we don't run afoul of any policies.

Thanks!

Dave

[John Scott]

there is this: 

https://dodcio.defense.gov/open-source-software-faq/

Also: Sounds like an excellent question for the OSI licensing workshop next month 

js

-------------------------------------------

John Scott

 240.401.6574

< jms...@gmail.com >

ionchannel.io 

--
--
You received this message because you are subscribed to the "Military Open Source Software" Google Group.
To post to this group, send email to mil...@googlegroups.com
To unsubscribe from this group, send email to mil-oss+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/mil-oss?hl=en

www.mil-oss.org

---
You received this message because you are subscribed to the Google Groups "Military Open Source Software (Mil-OSS)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mil-oss+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mil-oss/BDE76461-2937-476B-8B0D-BAF5105A3D8F%40gmail.com.

[Deb Bryant]

Oh gentlemen thank you for the opportunity to shamelessly plug an entirely relevant resource your way, better than a list, rather short stack of experts on the topic.  Besides having policy work Dan Risacher contributing to the program, the clinic will be attended by lots of agencies, including .mil; it's a question that might be asked there (and we promise to write down the answer and include it in the proceedings).  Next Tuesday April 4, 2023 in downtown D.C. , see the link and registration page for details.

Free to folks with .gov and .mil email addresses

https://blog.opensource.org/osi-to-hold-in-person-license-clinic-workshop/

If you have any questions or would like to contribute drop a line to me at my OSI email address-  deb dot bryant at opensource dot com.  

Cheers,

Deb

[Mark Bohannon]

There was also a useful submission by Deb, Dave Egts and myself done in 2016 in response to the Obama Federal Source Code Policy which had some good considerations for releasing code.  I can't seem to find it (unlike so much else) on the 'Net now ....

To view this discussion on the web visit https://groups.google.com/d/msgid/mil-oss/09838716-22e8-4f10-8fef-7675c21a8263n%40googlegroups.com.