[rabbitmq-discuss] [PATCH] Licensing issue with AMQP spec files and generated code

Alexis Richardson alexis.richardson at gmail.com
Mon May 25 17:15:29 BST 2009


Apologies.  The DFSG-safe spec in our repos is .json only but you
could very easily generate a .xml file from it.  This would also be
DFSG-safe due to the BSD license on the .json file.  Please note that
these files support AMQP 0-8.  If you would like to see a DFSG-safe
document for another spec version, please shout out about it here.


On Mon, May 25, 2009 at 4:50 PM, Alexis Richardson
<alexis.richardson at gmail.com> wrote:
> Michael,
> Thanks for that note and your patch.
> You should not use the AMQP-licensed XML files for DFSG compliant
> distributions.  Please use the BSD licensed .json and .xml from our
> repos, which are DFSG compliant.  How we got there is a long story
> that began when we noticed this problem in 2007 and set out to resolve
> it.  Note that we fixed the problem and that RabbitMQ is now
> disributed in Ubuntu universe and one of the Debian distributions.
> Let me know if you need more info and background on this.
> Best wishes
> alexis
> On Mon, May 25, 2009 at 4:43 PM, Michael Barker <mike at middlesoft.co.uk> wrote:
>> Hi,
>> In the process of building the Mono/AMQP integration, we've run into a
>> small problem with the licensing of the AMQP spec files and the
>> generated code.  The email from Mirco Bauer who handles the packaging
>> for the Debian distribution raised the issue which is detailed here:
>> http://lists.ximian.com/pipermail/mono-devel-list/2009-May/032255.html
>> We are going to resolve this by removing the spec files from Mono
>> source tree and change the generator so that it does not emit comments
>> verbatim from the spec files, which will be sufficient to adhere to
>> the DFSG.  I have attached a small patch to this email that does this.
>>  There is an additional command line option (/c) that can be used to
>> re-enable the comments.  It would be useful if this patch could merged
>> as it would save me from having to maintain this patch outside of the
>> main rabbitmq source tree.
>> Regards,
>> Michael Barker.
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list