Submission + - Corporate Open Source Policy?
Phiro69 writes: Does anyone have any best practices/experience they would like to share on how their corporate entity put Open Source Software out on the internet? Historically at my engineering firm, we've followed the model that we internally build a 1.0 release of something we want to open source, then the product owner & legal do a deep review of the release, then we push it out to a platform like github where it typically sits and rusts.
Our engineering interns have started down a new paradigm; starting out on github from the beginning (I set the repo private) and after they have a bare minimum done, flip the repo public and continue to develop it out on github, in full public view. How do PO & Legal reviews fit in? How can we ensure we're not exposing ourselves or diluting our IP if we're doing semi-constant development, publicly, sans a heavily gated review process? What does everyone else do? Or does corporate America avoid this entire opportunity/entanglement/briar patch?
Our engineering interns have started down a new paradigm; starting out on github from the beginning (I set the repo private) and after they have a bare minimum done, flip the repo public and continue to develop it out on github, in full public view. How do PO & Legal reviews fit in? How can we ensure we're not exposing ourselves or diluting our IP if we're doing semi-constant development, publicly, sans a heavily gated review process? What does everyone else do? Or does corporate America avoid this entire opportunity/entanglement/briar patch?
