In general terms to the associated ones apply:
- the owner of a ca2 subproject may choose to distribute its/his/her ca2 subproject
- freely: as the sun when walking or at the beach - it is freedom, it is natural:
The ca2 subproject owner may choose its ca2 subproject to be free. But for the next item to be true, and that real freedom be free to, ca2 subprojects based in the ca2 subproject may be free or not.
- for profit: as the gasoline from sun in petroleum, as the price of a child for a animal or parent or the services for getting an orange juice - it is freedom, it is natural:
Remember that a ca2 subproject owner may be a individual, or people that are owner of a ca2 subproject, or all ca2 Developers. These plural people may be called collective person. In ca2 original license type, which is the preferred one, the profit is distributed as working time share between the owner or owners. This working time can be kinecticely active or not.
The ca2 subproject owner or owners - in case of a collective person owner - may choose its ca2 subproject to be for profit. His software, that may be
following sofware, mixed or not:
- leaf software or application: top level sofware that uses other sofware;
- trunk sofware or core or api software: software that provides services for other software;
- root software or driver or operational system sofware
may be for profit, using many type of licenses - that may be ca2 original license type or other types of licenses - managed by ca2 licensing system - in development.
Examplse:
- I use a ca2 freware video player, but pay for the ca2 released codec - and the codec license is priced anually per user some price. For protection, the source code for the closed software should not be in the tree, only the final binary code, for the ca2 release system and ca2 licensing system software release and shopping.
- access all ca2 project source code, excepting special sensitive code like passwords, that requires special attention. The source code cannot be distributed to non-associated ones.
It is "free" to be an ca2 Developer. The cost is to work - or not, I should also say - in some way for ca2 goals. Take care with subjectivity here.
- change all source code, respecting the rules at the current point in the development way and with the adequate permission of all.
This may be achieved pragmatically when someone want to be associated exclusively to a ca2 subproject, leaving the responsability to the associates of the other ca2 subprojects. But every one at any time have the right to interfere. Also be careful with the subjectivity here!
[email protected]
http://twitter.com/qamilox
http://www.google.com/profiles/qamilox
>> environment
