savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] savannah.gnu.org: submission of Ly


From: Loic Dachary
Subject: Re: [Savannah-hackers] savannah.gnu.org: submission of Ly
Date: Wed, 20 Mar 2002 08:34:13 +0100

        Hi,

        I'm a bit confused with the license of Ly. The tarbal contains
the GPL, the LGPL and XPL. The files themselves do not contain a copyright
or license notice and I can't figure out which license applies to them.

        If you chose to use the GPL, could you please follow the instructions
below and submit the project again when you're done ? 

        Thanks in advance,

            How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
    the Free Software Foundation; either version 2 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with this program; if not, write to the Free Software
    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA


Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) year  name of author
    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
    This is free software, and you are welcome to redistribute it
    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License.  Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  <signature of Ty Coon>, 1 April 1989
  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs.  If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library.  If this is what you want to do, use the GNU Library General
Public License instead of this License.


address@hidden writes:
 > 
 > A package was submitted to savannah.gnu.org.
 > This mail was sent to address@hidden, address@hidden
 > 
 > 
 > Benja Fallenstein <address@hidden> described the package as follows:
 > License: gpl
 > Other License: 
 > Package: Ly
 > System name: ly
 > This package wants to apply for inclusion in the GNU project
 > 
 > Ly is an engine for elegant literate programming. (If you need information 
 > about literate programming not specific to Ly, please see 
 > <http://literateprogramming.com/>.) Ly aims for a syntax that is easy to 
 > type, easy to read, has as few special characters as possible, and looks 
 > very much like the human-readable output. You can interleave code with 
 > documentation (one code paragraph, one paragraph of text, two paragraphs of 
 > code and so on); Ly distinguishes code from text by indentation, thus 
 > avoiding the need for delimiting markup. Ly is written in Python and mainly 
 > targeted at outputting HTML, though other output formats are likely to be 
 > added in the future.
 > 
 > Ly is currently usable, but still in an early state (in a number of cases 
 > its error messages are not intelligible without reading the source code; 
 > there is too few documentation; not all of the code is literate itself, 
 > etc.). In the future, I want to modularize it enough to allow for easy 
 > modifications of its behaviors on all levels. There will be special support 
 > for some specific programming languages, easying the task of programming in 
 > them. Ly will use the StructuredTextNG package (now available under the Zope 
 > Public License 2.0), allowing Wiki-like formatting commands if desired. (If 
 > Ly is approved for inclusion in the GNU project, I would like to prepend 
 > \'GNU\' to its name.)
 > 
 > While I would like Ly to be customizable to any user\'s taste, I also want 
 > to maintain a standard distribution that makes literate programming 
 > *elegant* in my eyes. I also want to maintain an extensive archive of 
 > programs written using Ly.
 > 
 > So far Ly has been hosted at Sourceforge (sigh); you can find the download 
 > page at <http://sourceforge.net/project/showfiles.php?group_id=46322>. An 
 > introductory text is available in the distribution or at 
 > <http://lyterate.sf.net/intro.html>.
 > 

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
12 bd  Magenta         http://www.senga.org/      address@hidden
75010    Paris         T: 33 1 42 45 07 97          address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt



reply via email to

[Prev in Thread] Current Thread [Next in Thread]