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

(repeat) Please help with the free software catalog



RMS mailed me saying that with the submissions from Debian developers
(and others) the free software directory has become very nice, but he
asked me to ask you guys again to please submit a description for
your packages to the free software directory if you haven't done so. 

I've attached the original request with more info on the directory
and submission info.

Wichert.

-- 
  _________________________________________________________________
 /       Nothing is fool-proof to a sufficiently talented fool     \
| wichert@wiggy.net                   http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |
--- Begin Message ---
The FSF is currently building a database of all free software. The
reason they are not using a happy with existing databases like freshmeat
is that their database has a lot more details, and they don't want any
non-free software in there.

They already have one person (Janet Casey) working on the database. At
the moment they have most of the software to manage the database
written, but in order to get make it useful it needs to be filled.  Most
of the GNU software is in there, but of course that is only a small
portion of the available Free Software. This is where the FSF would like
our help: if every developer could submit an entry for his package(s) it
would give them a reasonably big database to start with. At least
enough for it to grow on its own momentum.

If you have any comments on this please mail them to Janet Casey
<jcasey@gnu.org>. Entries can be submitted to the address
database@gnu.org .

Attached to this mail are a couple of files:
* spec: complete specification of the format for a database entry
* template: an empty template that can be filled in. Fields that aren't
  filled in can be left out.
* example1: entry for textutil
* example2: entry for lilypond

Wichert.

-- 
  _________________________________________________________________
 / Generally uninteresting signature - ignore at your convenience  \
| wichert@liacs.nl                    http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |
Each entry in database is a separate file.

Every field starts with %% as the first character of line immediately
followed by field name and a colon.  Then comes the contents of the
field.  You can use newlines as you wish in the contents of a field,
but each field name should start at the left margin.

When we speak of a "list", use commas to separate items,
and put a newline after a comma wherever you feel that looks nice.

For dates, use DD MON YYYY, as in 5 Oct 1999.

Each entry must contain following fields:

name - name of package
short description - one-line description.
       If necessary, you can use two lines.
full description -
       full description, in plain text plus a basic set of HTML
       formating tags.  Tags <BR>, <P>, <UL>, <LI>, <DL>, <DT>, <DD>,
       <CODE> and <EM> are allowed.  You can also use &lt;, &gt; and &amp.
       Links (normally to GNU pages) are also allowed, but would only
       be appropriate in unusual situations.

       If you think some other HTML features should also be allowed here,
       please suggest them to me.

category - category name(s).  This is a list of high-importance keywords.
keywords - list of other keywords.

license - name of license, or the full license text
       if it is an unusual license.
updated - Last updated date of this record
interface style - command-line, library, text interactive, console, or X.

programs - list of programs included in this package.
	   This should include all the shell command names
	   that become meaningful as a result of installing the package.
	   If there are programs that the user involves but in some
	   other way, it is good to mention them too.

	 Don't bother with this field if the only important program
	 has the same name as the package itself.

GNU - include this with contents "yes"
         if the package is a GNU package.
web page - URL for web page describing the package.
support - One or more items of the form  BASIS TYPE from {PHONE | URL}
	  or  See also URL.

	 BASIS is either "free" or "paid".
	 TYPE is what kind of support is offered.
	   You can give more than one TYPE with "and" between.
	 You can give more than one instance of {PHONE | URL}
	   with "or" between.
	 For example, it could be
	    free user handholding from phone 1-617-555-1212
	    paid extension/consulting from http://www.wedoit.com/
	 Do not mention the help mailing list or help newsgroup here,
         because that is redundant.

doc - One or more items of the form
         [LANGUAGE] AUDIENCE TYPE [in FORMAT] [as MEDIUM]
	   [{at|from} LOCATION | included]

         LANGUAGE is the language this documentation is written in.
	      Omit it if it is English.
         AUDIENCE is the type of person it is addressed to
	      (typically "user" or "programmer" or "sysadmin").
         TYPE is the kind of information and presentation
	      (typically "introduction" or "reference" or
	       "intro & reference" or "reference card").
	 FORMAT is the file format, for machine-readable publication
	      (typically "Postscript" or "DVI" or "Texinfo" or "HTML").
	      For documentation included in the package itself,
	      which is available or can be produced in various formats,
	      this is omitted.
	      You can list several formats with "and" between them.
	 MEDIUM is the publication medium (typically "book", "card"
	      or "CD-ROM").  For Internet distribution or distribution
	      with the package itself, MEDIUM is omitted.
	      You can list several formats with "and" between them.
	 LOCATION is the URL, either for the documentation itself
	      or for how to order a copy.
	      Use "at" if the URL contains the documentation itself.
	      Use "from" if it contains ordering information.
	 "included" means the doc is in the package itself.

	 For example, it could be
	   English user reference in HTML at http://www.gnu.org/doc/foo.html

	 Each separate work of documentation should be
	 given a separate item.  If the work is included in
	 the package, mention that; otherwise, if it is available
	 on line in another way, mention that.  Meanwhile, if it
	 is also available as a printed book or card, or as a CD-ROM,
	 mention that *also*.

developers - list of primary developers' names, each optionally followed by an
	 email address in <...>.  For example, it could be
             Richard Stallman <rms@gnu.org>
maintainer - list of names of current principal maintainers,
	     with optional email addresses
	     If this is the same as the developers, omit this field.
contributors - list of assisting developers' names, each optionally followed
	 by an email address in <...>.
sponsors - list of sponsoring institutions' names, each optionally followed
	 by an email address in <...>.

source - list of designators for where to obtain source.
         A designator means a URL with * allowed as a wildcard.
	 It can also be a directory, followed by a | and a list of file names
	 *not* to use within that directory.
Debian package - designators for where to obtain Debian binary package.
Red Hat package - designators for where to obtain Red Hat binary package.
repository - HOSTNAME:DIRECTORY specifying the location of the CVS
	   repository, if the program has a publicly accessible repository.

related - related packages.  List of names of related packages.

human languages - list of human languages that the program has been
      internationalized for.  Use the two-letter standard language
      code, if the language has one.

supported languages - supported programing languages
	      (for a programming tool or library)
source languages - list of programming languages used in this package
use requirements - Prerequisites for using the executable
	 This might be a list of packages, or just names of programs.
build prerequisites - Prerequisites for building this package.
	 This might be a list of packages, or just names of programs,
	 that must be installed before you build this package.
weak prerequisites - Packages that are useful to install before building
	 this one, but not mandatory.
source prerequisites - Packages whose source code must be present
	 in order to build this package.

version - VERSION STATUS on DATE [for PLATFORMS] [Notes: NOTES]
	  This says which version the information about
	  and its status as of when the page was updated.

	 VERSION is the version number.  Don't end it with a period!
	 STATUS is "alpha", "beta" or "released".
	 DATE is the release date.
	 PLATFORMS is a list of supported platforms
	   given as names of systems or standard GNU configuration names.
	 NOTES are the release notes.

announcement list - email list to which announcements are made
		    *Every* GNU package must have an announcement list.
announcement newsgroup - newsgroup on which announcements are made
help list - email list for asking for help
            Do not give the maintainer's email address here!
	    That belongs in the %%maintainer: field.
	    If there is no list designated for people to ask for help,
	    omit this field.
help newsgroup - newsgroup for asking for help
bug report list - email list for reporting bugs
		    *Every* GNU package must have a bug report list.
		    Normally it should be bug-SOMETHING@gnu.org.

development list - email list for design discussion 
development newsgroup - newsgroup for design discussion 

%%name: 

%%short-description: 

%%full-description: 

%%category: 

%%license: 

%%maintainer: 

%%updated: 

%%keywords: 

%%interface: 

%%programs: 

%%GNU: 

%%web-page: 

%%support: 

%%doc: 

%%developers: 

%%contributors: 

%%sponsors: 

%%source: 

%%debian: 

%%redhat: 

%%repository:

%%related: 

%%source-language: 

%%supported-languages:

%%use-requirements: 

%%build-prerequisites:

%%weak-prerequisites: 

%%source-prerequisites:

%%version: 

%%announce-list: 

%%announce-news:

%%help-list: 

%%help-news:

%%dev-list:

%%dev-news:

%%bug-list: 

%%name: textutils

%%short-description: Text utilities

%%full-description: Textutils contains the following software:
<pre>       
       cat- concatenates and prints files on the standard output
       cksum- checksum and count the bytes in a file
       comm- compares two sorted files line by line
       csplit- splits a file into sections determined by context lines
       cut- remove sections from each line of files
       expand- convert tabs to spaces
       fmt- simple optimal text formatter
       fold- wrap each input line to fit in specified width
       head- output the first part of files
       join- join lines of two files on a common field
       md5sum- compute and check MD5 messsage digest
       nl- number lines of files
       od- dump files in octal and other formats
       paste- merge lines of files
       ptx- produce a permuted index of file contents
       pr- convert text files for printing
       sort- sort lines of text files
       split- split a file into pieces
       sum- checksum and count the blocks in a file
       tac- concatenates and prints files in reverse
       tail- outputs the last part of files
       tr- translates or deletes characters
       tsort- perform topological sort
       unexpand- convert spaces to tabs
       uniq- remove duplicate lines from a sorted file
       wc- prints the number of bytes, words, and lines in files              
</pre>		     
%%category: word-processing, editing, web-authoring

%%license: GPL

%%maintainer: Jim Meyering <meyering@ascend.com>

%%interface: Command line, interactive

%%updated: 03 Apr 2000

%%keywords: Text, editing, word-processing, editing, file management,
documentation, administration

%%programs: cat, cksum, comm, csplit, cut, expand, fmt, fold, head,
       join, md5sum, nl, od, paste, ptx, pr, sort, split, sum, tac,
       tail, tr, tsort, unexpand, uniq, wc 

%%GNU: yes

%%web-page: http//www.gnu.org/software/textutils/textutils.html

%%support:

%%doc: User manual available at http://www.fsf.org/manual/textutils/index.html
 
%%developers: David Mackenzie, Jim Meyering <meyering@ascend.com>

%%contributors: Francois Pinard <iro@cs.umontreal.ca>, Karl Berry,
Richard Stallman <rms@gnu.org>

%%sponsors: 

%%source: ftp://ftp.gnu.org/pub/gnu/textutils

%%debian:

%%redhat:

%%repository:

%%related: Emacs, diction, diffutils, wdiff

%%source-language:

%%supported-languages:

%%use-requirements: 

%%build-prerequisites: 

%%weak-prerequisites:

%%source-prerequisites:

%%version: 2.0 released 7 Aug 1999

%%announce-list: 

%%announce-news:

%%help-list: 

%%help-news: 

%%dev-list: 

%%dev-news: 

%%bug-list: bug-textutils@gnu.org
%%name: lilypond

%%short-description: Music typesetter
 
%%full-description: Produces sheet sound using a high level
descriptive file as input. It excels at typesetting classical sound,
but you can also use it for pop sound.

%%category: hobbies, publishing

%%license: GPL

%%maintainer: Hans-Wen Nienhuys <hanwen@cs.uu.nl>, Jan Nieuwenhuizen
<janneke@gnu.org>

%%interface: Command line

%%updated: 16 Feb 2000

%%keywords: Music, sheet sound, sound, editing, typesetting

%%programs: midi2ly, abc2ly, mup2ly

%%GNU: yes

%%web-page: http://www.gnu.org/software/lilypond/lilypond.html

%%support:

%%doc: User tutorial available from
       http:www.cs.uu.nl/~hanwen/lilypond/ 
       User guide available from
       http:www.cs.uu.nl/~hanwen/lilypond/ 
       Developer reference manual
       available from http:www.cs.uu.nl/~hanwen/lilypond/

%%developers: Han-Wen Nienhuys <hanwen@cs.uu.nl>, Jan Nieuwenhuizen
<janneke@gnu.org>

%%contributors: Mats Bengtsson, Roy Tankin, Alexandre Oliva, Adrian
Mariano; full list at
http://www.cs.uu.nl/~hanwen/lilypond/documentation.topdocs/out-www/AUTHORS.html

%%sponsors:

%%source: ftp://ftp.gnu.org/pub/gnu

%%debian: ftp://ftp.debian.org/pub/debian/dists/unstable/main/binary-i386/tex

%%redhat: ftp://ftp.cs.uu.nl/pub/GNU/lilyPond/RedHat/RPMS

%%repository:

%%related: GNU Octal, GNU Denemo

%%source-language: Guile, C++, Python

%%supported-languages:

%%use-requirements: TeX, a PostScript printer/viewer (such as
GhostScript), GUILE 1.3

%%build-prerequisites: EGCS 1.1 or newer, Python 1.5, Guile 1.2, GNU
make, flex (v. 2.5.4 or newer), bison (v. 1.25 or newer), Texinfo

%%weak-prerequisites:

%%source-prerequisites:

%%version: 1.2.6 released 03 Sept 1999

%%announce-list: info-gnu-sound@gnu.org

%%announce-news:

%%help-list: help-gnu-sound@gnu.org

%%help-news: 

%%dev-list: gnu-sound-discuss@gnu.org

%%dev-news:

%%bug-list: bug-gnu-sound@gnu.org

Attachment: pgpHXcSYATl6w.pgp
Description: PGP signature


--- End Message ---

Attachment: pgpSh5L94GxFJ.pgp
Description: PGP signature


Reply to: