Step 1: Convince the president of my vertical to consider open sourcing a body of code
Step 2: ???
To give a bit more detail, I've already successfully convinced my boss and boss's boss to consider open sourcing a body of code that was written mainly as a demo platform for our company. We've already determined that the code is useful and understand the benefits to open sourcing the code.
Now the question is where to go from here? What are the next steps? The president said that he'd like to see a project management proposal which would contain details like:
- Who would manage changes to the code?
- What would the process look like to release new code?
- How is the code review process defined before releasing code?
- Who will participate?
- What are the legal aspects that need to be considered first?
What I think I need is a "Open Sourcing Code for Dummies" guide or if there are some simple guidelines, how-to's, or templates for putting together a proposal available. I'd like to hit a home run on my first at bat and plop a solid proposal in his inbox. Any advice, resources, or ideas on how to structure such a proposal would be helpful.