[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-hackers] Re: submission of Chronicle Lite - savannah.nongnu.or
[Savannah-hackers] Re: submission of Chronicle Lite - savannah.nongnu.org
01 Jun 2003 22:56:46 +0200
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
I'm evaluating the project you submitted for approval in Savannah.
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> Paul Hawke <address@hidden> described the package as follows:
> License: mbsd
A part of your license seems problematic to me:
* This software is not designed or intended for use in on-line control *
* of aircraft, air traffic, aircraft navigation or aircraft *
* communications; or in the design, construction, operation or *
* maintenance of any nuclear facility. Licensee represents and warrants *
* that it will not use or redistribute the Software for such
It constitute a Discrimination Against Fields of Endeavor
And to be GPL-compatible, a license must not restrict anyone from
making use of the program in a specific field of endeavor. For
example, it may not restrict the program from being used in a
business, or from being used for genetic research.
We cannot host a non-GPL compatible project. The usual modified BSD,
without this clause, is GPL-compatible.
> Chronicle Lite currently has users worldwide and is at version 1.2. A binary
> version can be installed using the web installer -
> http://chronicle.caffeinatedbliss.com/lite/install - and source is available
> at http://chronicle.caffeinatedbliss.com/lite/ChronicleLite-src-v1.2.zip
> Chronicle Lite was initially released through Freshmeat.net on 15th September
> 2002, with the current release (v1.2) announced 1 June 2003.
> Other Software Required:
> Chronicle Lite is a desktop application and uses Swing.
The key question here is to figure out if your project
can run on a Free Software Java suite
(see http://www.gnu.org/software/java/ for more
information). Could you give us some explanation about
Please register your project once more with the changes mentioned
above. The way we handle pending projects makes it difficult to keep
track of projects that have been answered but have not been approved
yet, so we erase them and we ask you to register the project again every
time some change has to be done to the registration, and users might
have to register their projects several times. Thank you for your
Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.
Not a native english speaker: