April 24, 2009 at 00:00How to create your own opensource project
I have a project that I would like to do opensource. But as they say - hurry up - you make people laugh.
I would like to do as in the best houses of Paris, London and Syktyvkar. Correctly organize the svn (git? Mercurial?) Repository, choose a convenient bug-tracking system. Organize a convenient code exchange, easy connection to the developers project, easy assembly of new versions. Probably in OpenSource projects roles should be distributed, a hierarchy of developers, control of commits, 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. I google it, but no google can 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. Go for LGPL. But I have a couple of business ideas related to the project. They do not impose restrictions on the code itself, but their presence already makes changes to the license, right? Can I, based on the existing license, make my changes to it and release the product under my license. Is it eligible?
Vkracii about the project. The project site is here . There are, as it were, two parts
1. Envos.Framework - MVC PHP Framework. A fairly old version is now available (although the principles are the same). When I deal with organizational matters, I’ll post a new one.
2. Envos.Blogs- Multiblogging 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, in return obliging users of the engine 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 ability to manage this content for your own purposes.
I would like to know the opinion of the community on this matter.
I would like to do as in the best houses of Paris, London and Syktyvkar. Correctly organize the svn (git? Mercurial?) Repository, choose a convenient bug-tracking system. Organize a convenient code exchange, easy connection to the developers project, easy assembly of new versions. Probably in OpenSource projects roles should be distributed, a hierarchy of developers, control of commits, 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. I google it, but no google can 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. Go for LGPL. But I have a couple of business ideas related to the project. They do not impose restrictions on the code itself, but their presence already makes changes to the license, right? Can I, based on the existing license, make my changes to it and release the product under my license. Is it eligible?
Vkracii about the project. The project site is here . There are, as it were, two parts
1. Envos.Framework - MVC PHP Framework. A fairly old version is now available (although the principles are the same). When I deal with organizational matters, I’ll post a new one.
2. Envos.Blogs- Multiblogging 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, in return obliging users of the engine 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 ability to manage this content for your own purposes.
I would like to know the opinion of the community on this matter.