Hi !

First of all let me state here on how I'm pleased with svn - I know many 
developers out there prefer git, but
after digging bit deeper into git internals our team decided to gave up on git. 
Let them try to sort out their mess first, 
and may be after this I can move to it. Also git's GPL licence is another 
bottleneck for further improvement 
of git.

For long time I was disturbed with GPL licensing and open source code which is 
expensive to make, and no profit earned from it,
and also I'm disturbed by propitiatory source code base, such as Microsoft, 
which is basically only eating all knowledge without 
returning anything back for other developers to use.

Then eventually I've came up with licensing which would support both 
development approaches - 
open source code and closed platform base - and I've came up with license which 
I'm attaching below.

However - I don't have any source code repository (svn / git / mercurial) which 
would work under my license - basically my idea is
such that v1.0 is open source code, while v2.0 costs something, but after "1.0 
to 2.0" investment is returned - v2.0 also starts to be public.

I was thinking about helping you to change svn source code to work with my 
license, but this would basically mean to re-licence svn under my license
- also svn would become closed source code, till investments pays off. I would 
like to know your opinion on re-licensing svn - can I do it ?
And may be also someone would volunteer to help me to make changes to happen.

Attaching my idea of "Open platform license": (Gives you initial idea, text can 
still be tuned further):
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Open platform license
---------------------

Permission is hereby granted, free of charge, to any person obtaining current 
version of binary distribution copy of this software and associated 
documentation files (the "Software"), to deal in the Software without 
restriction, including without limitation the rights to use, copy, modify, 
merge, publish, distribute, sublicense, and/or sell copies of the Software.

Source code distribution or it's derivate works (including binary distribution 
of new versions)
can be sold for profit, however maximum profit earned from each change should 
be at maximum 3 times
of money invested into making change to happen. 
After receiving necessary profit author(s) must publish source code 
distribution along with changes for public.

Source code and binary distributions must remain standalone and testable in 
their
own environment - and if testability is broken - source code or binary 
distribution must be
extended to derivate work's source code or distribution. This license will be 
applicable to any derivate works raised from original distribution.

The software is provided "as is", without warranty of any kind, express or 
implied, including but not limited to the warranties of merchantability, 
fitness for a particular purpose and noninfringement. in no event shall the 
authors or copyright holders be liable for any claim, damages or other 
liability, whether in an action of contract, tort or otherwise, arising from, 
out of or in connection with the software or the use or other dealings in the 
software.



 
--
Have a nice day!
Tarmo.

Reply via email to