Re: [Savannah-hackers] submission of LMS (LDAP Management System) - savannah.nongnu.org

[Jaime E . Villate]

On Fri, Apr 25, 2003 at 08:19:00PM -0400, address@hidden wrote:
> A package was submitted to savannah.nongnu.org
> Duck <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: LMS (LDAP Management System)
> System name: lms
> Type: non-GNU
> 
> Description:
> The project is called LMS.
> LMS stands for LDAP Management System. It is designed to help managing 
> network objects on a network : Users / Groups / Hosts / Servers / Services / 
> ... It is based on a LDAP server holding all network information. Interfaces 
> will allow the administrator to manage the network, and users will be able to 
> view and edit their personnal information. Subsystem components are modules 
> able to reconfigure or talk with external applications in order to be managed 
> with LMS. The main goal is to create an object-oriented central point of 
> network administration.
> 
> LMS depends on an OpenLdap server and is pure PHP4 programming.
> LMS is to be released using GPL.
> 
> You can find our project page with access to source code here :
> https://www.duckcorp.org/projects/lms/
> 
> 
> Other Software Required:
> PHP4
> OpenLdap
Hi,

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

To release your project under the GPL, you should put
copyright notices and copying permission statements
at the beginning of every source-code file, and
include a copy of the plain text version of the GPL
(http://www.gnu.org/licenses/gpl.txt).
Put it in a file named COPYING.

Please follow the advice of http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explain the reason behind these recommendations.  For
example, there is an entry explaining why the GPL requires including a
copy of the GPL with every copy of the program:
 http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude

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
understanding.

Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.

Regards,
Jaime