Hi, I'm evaluating the project you submitted for approval in Savannah.
[EMAIL PROTECTED] said: > A package was submitted to savannah.nongnu.org > This mail was sent to [EMAIL PROTECTED], [EMAIL PROTECTED] > > Dave Malcolm <[EMAIL PROTECTED]> described the package as follows: > License: other > Other License: Combination of GPL and LGPL > > (i) I hope to get some of the code refactored into the core GNOME platform,, hence > this needs to be LPGL > (ii) I want to allow linkage to non-free libraries for certain plugins, whilst > providing a high-quality app if those libraries are not available; I believe the > plugin API needs to be LGPL for this reason > (iii) everything else can be GPL > Package: Conglomerate > System name: conglomerate > Type: non-GNU > > Description: > Conglomerate is a user-friendly XML editor, aiming at the \"great mass\" of > Microsoft Word users, to try to get them to convert to opn formats like DocBook. > Wherever possible, the complexity of XML is hidden from the end-user. > > The project is currently hosted at http://www.conglomerate.org > > To get at the latest code, use CVS: > export CVS_RSH=ssh > cvs -z3 -d:ext:[EMAIL PROTECTED]:/cvs checkout conge > It asks for a password. > The code is currently licensed under the GPL, but I would like to > relicense large portions under the LPGL. > > Other Software Required: > The program is built on top of the GNOME 2 platform. > > In addition, I want to allow plugins to connect to other libraries/APIs, for > instance, potentially the OpenOffice.org runtime, the pdflib library for outputting > PDF files etc. I may want to support plugins that access non-free libraries at some > point in the future. > > > However the core functionality will be built solely on LGPL and > other free libraries. In fact, every functionalities must be working on a completely free system. Your software can run with proprietary libraries but it should not make it better - which would means that your software incitate to use non-free software. 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, -- Mathieu Roy Homepage: http://yeupou.coleumes.org Not a native english speaker: http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english _______________________________________________ Savannah-hackers mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/savannah-hackers
