copyright/licensing feedback

[andhe]

Hello,

While preparing a package of garagemq for Debian I had to investigate the licensing and copyright status in great details. I'd like to provide some feedback from my findings of some things that are problematic for Debian and some details you might want to make more clear that might benefit others.

• The readme/*.jpg screenshots seems to contain an embedded ICC profile in their EXIF data which Apple claims copyright on. It's not clear which license these are provided under (if any?).[1] It would be nice if you could strip off the ICC profile from the images to save us the time having to think about legality of redistributing your screenshots.
• LICENSE mentions your copyright and license, but it could possibly be nice to more clearly/explicitly point out that protocol/*.xml has a different copyright holder and license.
• You spell your name diffently in LICENSE vs in the source (which makes your preference of how to be attributed in the Debian package copyright non-obvious), might want to make it consistent? (first last vs last first) :)
• Possibly point out that admin-frontend/build directory contains compiled/obfucated nodejs files -- without providing the corresponding source files in the garagemq repository.[2]

[1]: Apple copyright claims in readme/*.jpg

$ grep -i copyright readme/*.jpg
Binary file readme/channels.jpg matches
Binary file readme/connections.jpg matches
Binary file readme/exchanges.jpg matches
Binary file readme/overview.jpg matches
Binary file readme/queues.jpg matches
$ for a in readme/*.jpg ; do echo ===== $a ; identify -verbose $a  | grep -i copy ; done
===== readme/channels.jpg
    icc:copyright: Copyright Apple Inc., 2018
===== readme/connections.jpg
    icc:copyright: Copyright Apple Inc., 2018
===== readme/exchanges.jpg
    icc:copyright: Copyright Apple Inc., 2018
===== readme/overview.jpg
    icc:copyright: Copyright Apple Inc., 2018
===== readme/queues.jpg
    icc:copyright: Copyright Apple Inc., 2018

[2]: In Debian, and probably more places, this is problematic for two reasons. a/ a clear separation between "source" (preferable form of modification) and built files are desired. b/ corresponding source (and its licenses) must always be available to be allowed into Debian.

[valinurovam]

@andhe thx for feedback
Fixed issues about licence and icc profile #87

LICENSE mentions your copyright and license, but it could possibly be nice to more clearly/explicitly point out that protocol/*.xml has a different copyright holder and license.

How should I mention about protocol?

Possibly point out that admin-frontend/build directory contains compiled/obfucated nodejs files -- without providing the corresponding source files in the garagemq repository.[2]

Source files provided into the repo.