How to create your opensource project
I have a project that I would like to do opensource. But as they say - hurry - make people laugh.
I want to do both in the best houses of Paris, London and Syktyvkar. Correctly organize the svn (git? Mercurial?) Repository, choose a convenient bug-tracking system. To organize a convenient exchange of code, easy connection to the project of developers, a simple assembly of new versions. Probably in OpenSource projects, roles should be distributed, a hierarchy of developers, control of committees, creation of patches should be organized ... In general, there are many subtleties. So, I ask the community to advise good documentation - step-by-step instructions or just good articles on the topic. Googling I googled, but no google will replace personal experience :)
There is also a question about choosing a license. The project will be completely free, the code is completely open, and free to use. I do not mind. Looks like a LGPL. But I have a couple of business ideas related to the project. They do not impose restrictions on the code itself, but already their presence makes changes to the license, right? Can I, taking the existing license as a basis, make my own changes to it and release the product under my license. Is it eligible?
Vkratsii about the project. Project site here . There are two parts
1. Envos.Framework - MVC PHP Framework. A rather old version is now available (although the principles are the same). When you deal with organizational matters, lay out a new one.
2. Envos.Blogs - Multiblog engine written in Envos.Framework. The code is not yet available. It is necessary to solve the problems described above.
The business idea is to make an automatic update system in Envos.Blogs, instead of obliging the engine users to give me the content of their blogs, photos and other services, allowing me to publish them at my discretion, with reference to the source. Do not want to give, update manually.
The second idea is to provide a central server API for storing content (video, photos), again in exchange for the opportunity to manage this content for their own purposes.
')
I would like to know the opinion of the community about this.
I want to do both in the best houses of Paris, London and Syktyvkar. Correctly organize the svn (git? Mercurial?) Repository, choose a convenient bug-tracking system. To organize a convenient exchange of code, easy connection to the project of developers, a simple assembly of new versions. Probably in OpenSource projects, roles should be distributed, a hierarchy of developers, control of committees, creation of patches should be organized ... In general, there are many subtleties. So, I ask the community to advise good documentation - step-by-step instructions or just good articles on the topic. Googling I googled, but no google will replace personal experience :)
There is also a question about choosing a license. The project will be completely free, the code is completely open, and free to use. I do not mind. Looks like a LGPL. But I have a couple of business ideas related to the project. They do not impose restrictions on the code itself, but already their presence makes changes to the license, right? Can I, taking the existing license as a basis, make my own changes to it and release the product under my license. Is it eligible?
Vkratsii about the project. Project site here . There are two parts
1. Envos.Framework - MVC PHP Framework. A rather old version is now available (although the principles are the same). When you deal with organizational matters, lay out a new one.
2. Envos.Blogs - Multiblog engine written in Envos.Framework. The code is not yet available. It is necessary to solve the problems described above.
The business idea is to make an automatic update system in Envos.Blogs, instead of obliging the engine users to give me the content of their blogs, photos and other services, allowing me to publish them at my discretion, with reference to the source. Do not want to give, update manually.
The second idea is to provide a central server API for storing content (video, photos), again in exchange for the opportunity to manage this content for their own purposes.
')
I would like to know the opinion of the community about this.
Source: https://habr.com/ru/post/58115/
All Articles