Re: source code release policy for US Army ERDC Coastal and Hydraulics

[John Scott III]

thanks Chris that helps!

On Oct 17, 2012, at 11:05 AM, Chris Kees wrote:

> Notes from CODICE discussion
>
> *Sites like mil-oss.org with all the DoD policy guidance and OSI
> (opensource.org) and (www.fsf.org) and with license guidance is really
> helpful
>
> * It would be nice to have some more explicit how to documents (i.e.
> I'm a govie and want to release my code. I'm a govie and I want to
> release my contractor's code. I'm a gov contractor and want to release
> my code.) The idea is that people will do things that seem like
> they're easy, and we need to provide good defaults
>
> *I'm really interested in the path forward for using github and cloud
> services in general. Does putting government code on a private github
> repository constitute public release or are github's privacy
> protections sufficient.
>
> *We need a path forward for how to push changes to open code (go
> through the public release process for every diff? maybe just get
> blanket authority for minor releases 1.2.x and 1.x.x based on the
> basic trust between PM and PI/contractor)
>
> *Could OSI or mil-oss do the job of CODICE instead of standing up a
> new organization? This whole issue is confusing enough.
>
> *I was interested in the discussion on the topic of industry-lead
> versus government-led. I tend to agree that we need some kind of
> hybrid leadership model. I'm not familiar with act-if, but it sounded
> like an interesting idea to have matching organizations on both sides
> of the fence.
>
> Thanks again for putting on a great conference.
>
> Chris


-----------------------------------------------------------
John Scott
240.401.6574
< jms...@gmail.com >
http://powdermonkey.blogs.com
@johnmscott