[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-hackers] submission of GSLDAPBrowser - savannah.nongnu.org
From: |
Frédéric PRACA |
Subject: |
Re: [Savannah-hackers] submission of GSLDAPBrowser - savannah.nongnu.org |
Date: |
Wed, 8 Oct 2003 17:20:43 +0200 |
User-agent: |
Internet Messaging Program (IMP) 3.2.1 |
Quoting Rudy Gevaert <address@hidden>:
> Hi,
Hi,
> I'm evaluating the project you submitted for approval in Savannah.
Thanks
> On Mon, Oct 06, 2003 at 11:50:32AM -0400, address@hidden
> wrote:
> >
> > A package was submitted to savannah.nongnu.org
> > This mail was sent to address@hidden,
> address@hidden
> >
> >
> > Frédéric Praca <address@hidden> described the package as
> follows:
> > License: gpl
> > Other License:
> > Package: GSLDAPBrowser
> > System name: gsldapbrowse
> > Type: non-GNU
> >
> > Description:
> > The aim of the project is to provide a LDAP browser utility for GNUstep.
> >
> > it can only be used to look at data in LDAP directories using LDAP URL
> according to the RFC 2255.
> >
> > It's based on GSLDAP provided with the GNUstep framework, OpenLDAP
> libraries and the whole GNUstep framework (AppKit and Foundation).
> Currrently, the source code is not available on Internet.
> >
>
> Please register your project again and include an (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.
Well, even if I provided a website where the source code temporary is , I send
it to you.
> We wish to review your source code, even if it is not functional, to
> catch potential legal issues early.
Shouldn't have but who knows ;-)
> 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.
Yep, I read it but I could have forget anywhere.
> 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.
Done
> Regards,
>
> Rudy
Fred