[Mono-dev] [PATCH] Upgrade RabbitMQ libraries to version 1.5.3

[Mirco Bauer]

On Sun, 24 May 2009 11:13:12 -0400
Miguel de Icaza <miguel at novell.com> wrote:

> > Well the generated .cs file is already there, but contains parts
> > of the
> > specification, those are non-free bits too :) So someone has to
> > generate a naked C# interface from that, that's what I meant with my
> > first post.
> 
> Please provide details in the mailing list.   Vague details like
> this are not useful to me, I cant do anything about it

Well if you take a look at the xml and then the cs file it is very
obvious (ok, at least to me).

So here it is:

qpid-amqp.0-8.xml says

> License
> =======
> JPMorgan Chase Bank & Co., Cisco Systems, Inc., Envoy Technologies
> Inc., iMatix  Corporation, IONA Technologies, Red Hat, Inc., TWIST
> Process Innovations, and  29West Inc. (collectively, the "Authors")
> each hereby grants to you a worldwide, perpetual, royalty-free,
> nontransferable, nonexclusive license to (i) copy, display,
> distribute and implement the Advanced Messaging Queue Protocol
> ("AMQP") Specification and (ii) the Licensed Claims that are held by
> the Authors, all for the purpose of implementing the Advanced
> Messaging Queue Protocol Specification.

That's cleary not an open-source license (as it's an specification
license). You are not allowed to modify nor to redistribute the
modified version.

Now the specification file contains interface descriptions like this:

> <field name="mechanism" type="shortstr">
> selected security mechanism
> <doc>
> A single security mechanisms selected by the client, which must be
> one of those specified by the server.
> </doc>
> ...
> </field>

The used and needed source code file autogenerated-api-qpid-0-8.cs now
contains for example:

>    /// <summary>
>    /// 
>    ///       A single security mechanisms selected by the client, which must be
>    ///       one of those specified by the server.
>    ///
>    /// </summary>
>    string Mechanism { get; }

The description was copied from the non-free specification (and no otherwise
defined licensed for the documentation strings) into the generated C# interface
definition.

This makes this C# code as is non-free, too.

This is exactly the same matter when developers implement RFC standards and copy
documentation from it into their source. The license of the specification is not an
open-source license.

> >
> 
> > If I would have the time and interest I would have done that already
> > long time ago.
> 
> WEll, it seems that the XML files are not used, so it is a non- 
> issue.   You can continue stripping the XML files.

That's what I did, the .xml files and .cs file is gone, everywhere else remained, as
covered by the Apache 2.0 license (but doesn't compile anymore).

I hope it's now clear what I tried to point out.

> 
> Miguel.


-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developer    meebey at meebey.net  http://www.meebey.net/
PEAR Developer    meebey at php.net     http://pear.php.net/
Debian Developer  meebey at debian.org  http://www.debian.org/