savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of xine-net - savannah.nongnu.org


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of xine-net - savannah.nongnu.org
Date: 13 Sep 2003 16:51:25 +0200
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

Hi,

I'm evaluating the project you submitted for approval in Savannah.



address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Dave Baker <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: xine-net
> System name: xine-net
> Type: non-GNU
> 
> Description:
> A network frontend for xine based on the GPL project sxfe. Developed on 
> Slackware Linux and designed to run on UNIX based systems which xine will run 
> on. Designed to be left unattened and be given commands by a separate system. 
> Commanded by a standard TCP network connection, giving single letter 
> commandsm some of which take arguments. Supports a playlist to run through 
> once, or in 'loop mode'. Also uses POSIX threads to handle multiple clients, 
> and an X Event loop. Aims to be a simple, stable piece of software to run on 
> video server, i.e. playing out videos at certain times. Scheduling is 
> currently done by a separate system sending commands at the right time, and 
> there are currently no plans to change this.
> 
> Full source code at: http://ystv.york.ac.uk/~dave/xine-net.tar.gz

 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 your case, the headers are truncated and the copyright holder is
not mentioned.

Additional instructions are available from
http://www.gnu.org/licenses/gpl-howto.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, go to
http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude

Please register your project once more with the changes
mentioned above.  

We cannot track projects that have been answered but not approved, so
we must ask you to register the project whenever you change the
registration. Make sure to apply all changes so you need to reregister
only once.

The re-registration URL found in our acknowledgement of your earlier
registration will direct you to the proper location.

Regards,



-- 
Mathieu Roy
 
  Homepage:
    http://yeupou.coleumes.org
  Not a native english speaker: 
    http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english




reply via email to

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