{"id":2752,"date":"2013-06-19T12:45:11","date_gmt":"2013-06-19T17:45:11","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/?p=2752"},"modified":"2013-06-19T12:45:23","modified_gmt":"2013-06-19T17:45:23","slug":"thanks-oracle-for-fixing-the-gpl-man-page-issue","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2013\/06\/19\/thanks-oracle-for-fixing-the-gpl-man-page-issue","title":{"rendered":"Thanks Oracle for fixing the GPL man page issue"},"content":{"rendered":"

Timing is everything. I wrote about how MySQL man pages were silently relicensed away from the GPL<\/a>. It was picked up by a lot of sites: Hacker News<\/a>, Slashdot<\/a>, LWN<\/a>, and probably more. That led to a bug report in Debian (#712730<\/a>) to complain that MySQL is no longer compliant with the Debian Free Software Guidelines (DFSG)<\/a>. That prompted Norvald Ryeng who’s active in Debian (thanks Oracle!) to file MySQL bug #69512<\/a>. Almost immediately Oracle said it was a bug, where Yngve Svedsen pointed to the buildsystem: “This is indeed a bug, where the build system erroneously and silently started pulling in man pages with the wrong set of copyright headers.”<\/em> That then prompted Tomas Ulin to write about how The MySQL Man Pages ARE Available under the GPL<\/a>. Case closed, many on Hacker News attributed<\/a> it to Hanlon’s razor<\/a>. Most news sites updated it with the bug, and The H also wrote an article:\u00a0Oracle bug accidentally removes GPL licence from MySQL man pages<\/a>.<\/p>\n

We learned about this issue from MariaDB Jira and spent some time looking at it. We looked at the MySQL source tarballs, and looked at 5.5.30\/5.5.31\/5.5.32. This issue is present in a release since 18 April 2013 (5.5.31) and a subsequent release on 3 June 2013 (5.5.32).\u00a0What is clear is that this also affects 5.1, 5.6, and 5.7. This has been an issue for about two months<\/strong>.<\/p>\n

So this issue is written off as a bug. Great. Its fixed because it was noticed. It’s noticed not because it was just reported in the bugs system, but because there was a huge amount of traffic around it. While Tomas might say,\u00a0“Reporting a bug is always a good way to communicate with us,”<\/em> I doubt this would have been fixed in record time any other way. Also, I don’t need to rehash all the issues with the public\u00a0bugs<\/a>\u00a0system.<\/p>\n

I’m not about to start conspiracy theories here because that isn’t my goal. Our frame of mind since last week’s RHEL Software Collections news has been focused on documentation as well. Sheeri Cabral<\/a>, an Oracle ACE Director, has had a rather interesting conversation<\/a> on Twitter about our documentation. man pages aside, we’re improving documentation tremendously, and have over 2,700 articles in the Knowledgebase<\/a>.<\/p>\n

One thing is for sure with Oracle as steward for MySQL: the public perception of Oracle isn’t at its best and generally no one assumed this to be an accident.<\/p>\n

Now let’s focus on something celebratory and positive: MySQL (NDB) Cluster 7.3 is now a GA<\/a>. I’m excited by the node.js connector and the auto-installer. Can’t wait to give it a try. Congratulations all round to the Cluster Team at Oracle.<\/p>\n

Share this:<\/h3>