> We could argue about whether your license really makes PilRC
> free or not, but the fact is that Wes *did* give permission to
> distribute PilRC under GPL two years ago. Since neither he or
> you have indicated any change in the license until now it could
> indicate that all versions up to version 2.5b5 has been released
> under GPL. Wes and you are entitled to change the license, but
> any version that was released under GPL will stay under GPL,
> i.e. you can't stop anyone from continue developing the last free
> (as in speech) version.
i dont want to argue with you or continue the discussion abuot
about the previous license (if any) of PilRC - but please let me
make these issues clear:
there has been no "inclusion" of a copy of the GNU GPL license
nor any mention of the GPL license with any copy of PilRC that
has been bundled for download from my website nor Wes's.
http://www.gnu.org/copyleft/gpl.html
---
1. You may copy and distribute verbatim copies of the Program's source
code as you receive it, in any medium, provided that you conspicuously
and appropriately publish on each copy an appropriate copyright notice
and disclaimer of warranty; keep intact all the notices that refer to
this License and to the absence of any warranty; and give any other
recipients of the Program a copy of this License along with the Program.
---
THIS is taken from the GNU GPL definition. there is no "license"
anywhere with the PilRC distribution - hence it fails to have
complied to ever being under GNU GPL.
as a distributor, you MUST include the GNU GPL license when you
distribute your software - otherwise the license does not exist.
> I hope you will come to your senses and agree to continue
> developing PilRC under GPL, but if not, it would always be
> possible for someone else to add a new project for PilRC
> at SourceForge...
sourceforge is not the best maintainance system - as it does
not allow for flexibility and adjustment to the general tree.
forking of PilRC is something we dont want - and thats why we
have the Michael Sokolov "program" with prc-tools.
i have discussed this with Wes, and forking is not something
we want - because people like Michael Sokolov screw it up. i
believe this is in the best interest of PilRC.
i generated the license by reviewing the licensing issues
at the following url:
http://www.gnu.org/philosophy/license-list.html
the license encourages everything to keep the software FREE,
the only restriction we are placing is to have the distribution
at a SINGLE place. you dont realize how many questions i get
from users who are using OLD versions of PilRC - this is why
the license is the way it is.
keep a single repository, and link to it.. it is not part of
prc-tools, nor any other toolkit. the idea is to keep the PilRC
distribution at ONE place, not many and reduce the issues of
forking (for no real good purpose) and outdating of releases.
PilRC has a very frequent update schedule, which is different
from all the toolkits being distributed. i can update PilRC
as often as two times a month.
i took care writing the license agreement and discussing it with
John Marshall - the prc-tools 2.0 maintainer to ensure i cover
everything that was required. we want to do what is best for
PilRC..
now, may we please just get on with writing the software and keep
developing - there are a load of improvements we can make to this
software, lets just do it!
if anyone wishes to discuss the "license" issue, please lets
not keep it going on the list - if it is really important to you,
please call me on +46 70 656 1143, and if you feel you would like
me to modify the license (yet still keep the goals i have listed)
we can discuss it..
cheers.
az.
--
Aaron Ardiri
Java Certified Programmer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 656 1143 A/H: +46 8 668 78 72
if you enjoy it, then it aint work :) - rule #106 of life
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
