--
Sylvain
> At 19:57 2004-12-14, you wrote:
> >Hello,
> >
> >Here is how we consider Java: Sun's version of Java is proprietary
> >software, and hence we do not want applications to depend on
> >it. However, the GNU project develops a free version of the Java
> >language compiler, of the JVM, and of the Java API. So, the version of
> >Java we expect you to use is one that is free; it should become the
> >Java suite you use, not a casual testing platform.
> >
> >For more information, check "Free But Shackled":
> >http://www.gnu.org/philosophy/java-trap.html
> >
> >Besides, the ant build file you use is clearly planned for MS Windows,
> >as it contains hard-coded Windows-style paths with drive letters. The
> >primary platform for Savannah-hosted software has to be a completely
> >free operating system such as GNU/Linux.
> >
> >We have adopted this policy because now that completely free operating
> >systems exist, we do not want to encourage users of those systems to
> >start using proprietary operating systems so that they can use your
> >program.
> >
> >If you are willing to maintain a version for free operating systems,
> >which work as well as or better than other ports, you can then provide
> >versions for non-free systems as well. The idea is that at no point
> >should only-free users be at a disadvantage compared to users of
> >proprietary software.
> >
> >Your project should always work equally well in free systems as in any
> >other version you provide; if you have some modules for non-free
> >systems, you can delay their release until you have released the free
> >operating system version.
> >
> >If you accept this commitment then please tell so and your project
> >should be approved in Savannah.
> >
> >
> >Getting more practical, in order to release your project properly and
> >unambiguously under the GPL, please place copyright notices and
> >permission-to-copy statements at the beginning of every file of source
> >code.
> >
> >In addition, if you haven't already, please include a copy of the
> >plain text version of the GPL, available from
> >http://www.gnu.org/licenses/gpl.txt, into a file named "COPYING".
> >
> >For more information, see http://www.gnu.org/licenses/gpl-howto.html
> >and http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html
> >
> >The GPL FAQ explains why these procedures must be followed. To learn
> >why a copy of the GPL must be included with every copy of the code,
> >for example, see
> >http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.
> >
> >If you are willing to make the changes mentioned above, please provide
> >us with an URL to an updated tarball of your project. Upon review, we
> >will reconsider your project for inclusion in Savannah.
> >
> >Regards,
> >
> >--
> >Sylvain
> >
> >
> >On Mon, Dec 13, 2004 at 07:04:58PM +0000, Sebastien Lechelle wrote:
> >>
> >> Hi Sylvain,
> >>
> >> As promised please find attached to this email the Java source for
> >> PESPSolver. I did not have the time to compile PESPSolver with GCJ but
> >I am
> >> pretty sure it would be ok. As I explained, PESPSolver is mostly about
> >> number crunching of matrix, etc. so there is nothing fancy in the code.
> >>
> >> Let me know if you require more from me.
> >>
> >> Cheers
> >> Sebastien
> >>
> >> At 11:51 12/12/2004 +0100, Sylvain Beucler wrote:
> >> >Hi,
> >> >
> >> >I'm evaluating the project you submitted for approval in Savannah.
> >> >
> >> >> Sebastien Alain Lechelle <address@hidden> described the
> >> >> package as follows:
> >> >> License: gpl
> >> >> Other License:
> >> >> Package: PESPSolver
> >> >> System name: pespsolver
> >> >> Type: GNU
> >> >>
> >> >> Description:
> >> >> PESPSolver is a command line tool for solving Periodic Event
> >Scheduling
> >> >> Problems (PESP).
> >> >>
> >> >> Given a set of periodic events and periodic constraints linking those
> >> >> events, PESPSolver does either one of the following:
> >> >>
> >> >> - Demonstrate that the PESP instance is infeasible, or
> >> >> - Generate a working periodic timetable for the set of events.
> >> >>
> >> >> PESPSolver is being developed in SUN Java 1.4 programming language by
> >> >> Sebastien Alain Lechelle.
> >> >>
> >> >> PESPSolver can be used for solving Periodic Event Scheduling
Problems,
> >> >> i.e. for finding time-tables (or schedules) for sets of events that
> >are
> >> >> T-periodic. Such sets of events can be found in railway systems,
> >> >> production chains, etc.
> >> >>
> >> >> Homepage: http://www.chez.com/lechelle/pesp/
> >> >>
> >> >> Other Software Required:
> >> >> JAMA, Java Matrix Library, available at
> >> >> http://math.nist.gov/javanumerics/jama/
> >> >
> >> >You must determine whether your project can run on a Free Software
> >> >Java suite (see http://www.gnu.org/software/java/ for more
> >> >information).
> >> >
> >> >We recommend you to test your project using GCJ and GNU Classpath, and
> >> >ensure that your Java code runs on this Free Software Java suite.
> >> >
> >> >GCJ is the GNU Compiler for Java, part of the GCC (GNU Compiler
> >> >Collection). The Classpath project aims to develop a free and
> >> >portable implementation of the Java API (the classes in the 'java'
> >> >package).
> >> >
> >> >More information is available at http://gcc.gnu.org/ and
> >> >http://www.gnu.org/software/classpath/,
> >> >
> >> >Please provide us with more information about this point.
> >> >
> >> >Also please include a (perhaps temporary) URL pointing to the source
> >> >code. The description you gave when registering will not be read by
> >> >the general public. If you are still concerned with privacy, however,
> >> >you can forward the code to me by email (address@hidden).
> >> >
> >> >We wish to review your source code, even if it is not functional, to
> >> >catch potential legal issues early.
> >> >
> >> >For example, to release your program properly under the GPL you must
> >> >include a copyright notice and permission-to-copy statements at the
> >> >beginning of every file of source code. This is explained in
> >> >http://www.gnu.org/licenses/gpl-howto.html. Our review would help
> >> >catch potential omissions such as these.