Whether the author of an original software work prefers to maximize value for the community or for the bottom line, changing the parameters of a copyflex license makes this possible.

The author of an original software work will make available a portion of that code under open source terms in order that any third party can use, enhance, and extend it. Under one form of open source license (e.g. GPL), all subsequent developers surrender their rights to control redistribution of anything they create based on open code.  Under another form of open source license (e.g. BSD), subsequent developers never surrender these rights. 

• The former hurts trade because a developer can only exchange his or her intellectual contribution once before access becomes theoretically universal.
• The latter hurts users and code base consistency by forking the code into closed and open systems.

Copyflex benefits the original author, subsequent developers, and users whoever they may be.  If the author operates for profit, then the firm or individual retains a complementary resource which they sell into a growing community.  As the value of peanut-butter rises, sales of jelly also rise.  If the author was not-for-profit, then opening the entire code base grows the community faster.  The author may also benefit from royalties on any subsequent developer sales so that the community becomes self-sustaining instead of subsidized.

How it works