savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of xmlBlaster message oriented middle


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of xmlBlaster message oriented middleware - savannah.nongnu.org
Date: 16 Jun 2003 16:59:37 +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
> 
> Marcel Ruff <address@hidden> described the package as follows:
> License: lgpl
> Other License: 
> Package: xmlBlaster message oriented middleware
> System name: xmlblaster
> Type: non-GNU
> 
> Description:
> XmlBlaster (http://www.xmlBlaster.org) is a publish/subscribe and point to 
> point MOM server (message-oriented middleware) which exchanges messages 
> between publishers and subscribers. The message is described with XML-encoded 
> meta information. Messages may contain everything, GIF images, Java objects, 
> Python scripts, XML data, a word document, plain text - just anything.
> 
> Communication with the server is based on CORBA (using JacORB) or RMI or 
> XmlRpc or native SOCKET, clients are free to choose their preferred protocol. 
> Other protocols like email or SOAP may be plugged in.
> 
> Subscribers can use XPath expressions to filter the messages they wish to 
> receive.
> 
> This is the publish/subscribe middleware server you have needed many times 
> before, now available for free to glue together your distributed 
> client/server application.
> 
> The xmlBlaster server is pure Java and under LGPL.
> Note that PHP, Perl, Python, C/C++ and Java (applications, servlets) client 
> demos are in the xmlBlaster distribution available.



The key question here is to figure out if your project
can run on a Free Software Java suite
(see http://www.gnu.org/software/java/ for more
information).  Could you give us some explanation about
this point?



Also, note that 
to release your project under the (L)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,



-- 
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]