Sort GPL3 incompatibilities

[kittsville]

There are numerous StackOverflow snippets used in the project and cited inline. A Creative Commons licence is generally assumed for SO responses, which is incompatible with GPL2. As such either of the following actions must be undertaken for each snippet: A - Contact the snippet's creator and ask for their permission to use the snippet in the plugin. If the creator does not want their snippet used then B:

B - Remove the snippet and write your own damn code, punk.

Option A would be preferable.

[kittsville]

Adeneo has been contacted with regards to his snippet adapted here.

Mike Schinkel gave permission for this adapted snippet to be used.

This leaves (according to GitHub's search) two SO users to contact about their snippets: Eleotlecram's answer about checking for the success of jQuery selectors and Cryptic's ISBN validator.

[kittsville]

Turns out Eleotlecram's code snippet wasn't actually being used anywhere so it's been removed as of 7590dc6cb1712d33819478e3600d2a65ce11ff7b.

[kittsville]

Unfortunately contacting Cryptic will require being able to post to the PHP chatroom on SO, which requires 20 reputation. This leaves the following options: Earn 20 Rep This would require asking several new and interesting questions on the site, something I'll be unlikely to achieve. Alternatively I could find unanswered questions I have specific knowledge about (such as this one) and write good answers.

Pester someone I know with 20 rep This is a lot more tempting

Learn how ISBN validation works

Hope they find this repository Considering submission of this plugin to the WordPress Plugin repository is a long way away, it's possible that just by mentioning her specific username she'll find this plugin and contact me. This isn't particularly likely but just in case: cryptic ツ

[kittsville]

Well I now have 20+ rep on the WordPress Stack Exchange. Unfortunately I can't participate in any SO chatroom until I have 20+ rep on SO itself. The best bet for getting that seems to be answering WordPress questions that stumble their way onto SO.

[kittsville]

I'm beginning to wonder if just sitting down and learning how ISBNs work would be easier and less convoluted.

[kittsville]

Rdllopes has been contacted with regards to the modified version of his code for diacritic normalisation in AdminSettings.js.

[kittsville]

The diacritics code snippet is licensed by Rdllopes under Apache V2.0, which is compatible with GPL V3.0 but not GPL v2.0. As such WP-Librarian's next release will be under GPL V3.0, which is permitted by WordPress while not encouraged.

Rdllopes used a modified version of an answer by SO user khel, who in turn copied a code snippet from lehelk.com (archive.org link). According to archive.org the website has either been a blank page or a misconfigured server for over a year now and when it wasn't it only contained two blog posts. One being the diacritics map and the other being a mention of a Userscripts script back from when Greasemonkey was a thing. While a mirror for Userscripts exists the page for the script has no useful information as to whom Lehel was. Further searches have failed to uncover any other profiles or information about Lehel.

With no mention of licensing on the publicly posted, now defunct, blog post (besides WP's default copyright footer dated 2012) and with no means to contact Lehel I would consider the diacritics mapping fair game for use in the plugin.

[ghost]

@kittsville Hi, this is 'cryptic ツ' from SO, my Github is linked in my profile . You have my permission to license the code snippet under GPLv3 =o)

P.S. You can always @ mention someone on the SO post.

[kittsville]

Many thanks. I somehow completely missed the GitHub link on your SO profile @_@