juerd / p6-mqtt Goto Github PK

I am spearheading the effort to get all Perl 6 ecosystem modules to have "license" tags in their metadata for the module. You can see more about my effort by reading my blog post here: https://cry.nu/perl6/ecosystem-license-module-tagging/

I see your license says:

Pick your favourite OSI approved license :)

http://www.opensource.org/licenses/alphabetical

I wrote a quick script to see how that would look using SPDX standardized notation (our new Metadata license field specification, the most widely used identifiers in the open source world).

use JSON::Fast;
my %hash = from-json qx{curl 'https://raw.githubusercontent.com/sindresorhus/spdx-license-list/master/spdx-full.json'}; 
%hash.keys.grep({%hash{$_}<osiApproved> eq 'True'}).join(' OR ').say;

Here is what it looks like:

APSL-1.1 OR LGPL-2.0+ OR AGPL-3.0 OR Artistic-2.0 OR MPL-1.1 OR EFL-2.0 OR LPL-1.0 OR PHP-3.0 OR Multics OR LPPL-1.3c OR ECL-2.0 OR BSD-2-Clause OR BSD-3-Clause OR GPL-3.0 OR Python-2.0 OR GPL-3.0-with-autoconf-exception OR IPL-1.0 OR Entessa OR GPL-2.0-with-autoconf-exception OR EPL-1.0 OR LGPL-2.1 OR Artistic-1.0 OR Nokia OR GPL-2.0-with-font-exception OR CDDL-1.0 OR IPA OR APL-1.0 OR Motosoto OR MS-RL OR LGPL-3.0 OR GPL-3.0+ OR NTP OR SPL-1.0 OR LGPL-2.0 OR SimPL-2.0 OR RSCPL OR AFL-2.1 OR Apache-2.0 OR GPL-2.0+ OR LGPL-2.1+ OR Artistic-1.0-Perl OR Sleepycat OR Naumen OR Fair OR AFL-1.1 OR CUA-OPL-1.0 OR AFL-1.2 OR OFL-1.1 OR W3C OR LGPL-3.0+ OR LiLiQ-P-1.1 OR GPL-2.0-with-bison-exception OR RPL-1.1 OR EUPL-1.1 OR GPL-2.0-with-GCC-exception OR QPL-1.0 OR LiLiQ-R-1.1 OR Xnet OR OSL-2.0 OR AAL OR LiLiQ-Rplus-1.1 OR GPL-2.0-with-classpath-exception OR OCLC-2.0 OR APSL-1.0 OR Zlib OR MS-PL OR NPOSL-3.0 OR Watcom-1.0 OR LPL-1.02 OR APSL-2.0 OR CPAL-1.0 OR CNRI-Python OR RPSL-1.0 OR BSL-1.0 OR CPL-1.0 OR EUDatagrid OR ZPL-2.0 OR WXwindows OR SISSL OR GPL-3.0-with-GCC-exception OR MirOS OR OSL-3.0 OR NASA-1.3 OR ISC OR Frameworx-1.0 OR OSL-2.1 OR EFL-1.0 OR CECILL-2.1 OR AFL-3.0 OR NCSA OR VSL-1.0 OR MPL-2.0 OR OSL-1.0 OR MPL-2.0-no-copyleft-exception OR HPND OR GPL-2.0 OR RPL-1.5 OR CATOSL-1.1 OR Artistic-1.0-cl8 OR OGTSL OR OSET-PL-2.1 OR MIT OR MPL-1.0 OR Intel OR UPL-1.0 OR PostgreSQL OR ECL-1.0 OR Apache-1.1 OR AFL-2.0 OR NGPL OR 0BSD OR APSL-1.2

A bit ridiculous, though it would by a fully valid license identifier.

Could I recommend you choosing Artistic-2.0 or another permissive license (most of our modules are Artistic-2.0)? Or you could even license it under Artistic-2.0 or any other OSI-Approved license like you had before, but I'd like to make the license field usable. Thanks.

Hi,
Thanks for the great module.

It works fine, but I've spent a fairly long while questioning my sanity and/or ability while testing something with ActiveMQ until I discovered that if multiple connections have the same client-identifier it silently disconnects the earlier ones from the message flow so it looks like there are no messages being sent and/or received.

I've been using UUID to generate unique client-identifier, but I guess making the default something with $*PID appended might stop this catching someone by surprise.