Guidelines for open source search?

Question

Step 1: Encourage my vertical president to consider open source code

Step 2:

To give a little more detailed information, I have already made sure that my boss and boss will consider an open source code, which was written mainly as a demo platform for our company. We have already determined that the code is useful and understands the benefits of opening code.

Now the question is where to go next? What are the next steps? The President said that he would like to see a project management proposal that would contain details such as:

• Who will manage the code changes?
• What will the process for releasing new code look like?
• How is the code verification process determined before code is released?
• Who will participate?
• What are the legal aspects that need to be considered first?

It seems to me that I need the manual "Open Sourcing Code for Dummies" or if there are some simple recommendations, instructions or templates for writing a proposal. I would like to hit home run in my first place at bat and put together a solid offer in my inbox. Any advice, resources, or ideas on how to structure such a proposal would be helpful.

Answer 1

I would consider the following:

• Think about the goals of openly searching your software and test all your solutions in this light.
• , , - . . , , .
• . copyleft (GPL, AGPL) (Apache, BSD, MIT).
• , ( ).
• . , , "make", , , , ..
• - . , -, .
• , . , , , X .
• , . , , . , , . . , .
• , , . .

, .