It's time for another
Meetup of the Hamburg MySQL User Group! As for previous events, we'll meet on Monday, 2nd of April at 19:00 in the Chinese restaurant
Ni Hao in Hamburg-Wandsbek.
This time there will be a presentation about "Xing/OpenBC growing pains", held by Erick Dennis und Michael Otto from epublica, the company behind Xing.com.
The talk will be held in english and is a rehearsal for their presentation at our upcoming MySQL Conference and Expo, which will take place from April 23rd-26th in Santa Clara, California. Please subscribe to our mailing list and RSVP, if you plan to attend the Meetup. Thank you!
So far, the MySQL Server RPM packages as provided by MySQL AB used to automatically start the mysqld process after the package has been installed. It has been like that since the very beginning and we think of it as a convenience for our users when they want to get up and running quickly.
However, Kristian raised an interesting point in BUG#27072 where he points out that automatically starting mysqld during the RPM installation might not always be the desired behaviour, especially in automatic installation environments or during a fresh installation (where the system might not be fully configured yet). Therefore he proposes to change this behaviour to not start mysqld as part of the installation.
While I personally agree with his proposal, this is of course a tricky decision: our users are familiar with this behaviour and it's never a good idea to cause surprises. Therefore this change could only be done in future versions of MySQL, where they can be properly announced and documented and don't cause too much confusion.
Then again, there are several options here. Should we just disable it for the Enterprise Linux RPMs (RHEL/SLES) and keep it enabled in the "generic" RPMs? This would be inconsistent and harder to document/explain. Should the server never be started at all, or should we keep the behaviour for updates at least (when the server was already running before the package update)?
We would like to get your take on this. Please post your comments and suggestions to the bug report (preferred) or leave a comment on my blog, so we can get an impression on what you would expect to be the correct behaviour here. Thanks!
I just stumbled over Sebastian's blog entry:
The second Free and Open Source Conference "FrOSCon" takes place on August, 25th and 26th 2007 in Sankt Augustin, near Bonn, Germany. The conference is once again hosted by the faculty of computer science of the University of Applied Sciences Bonn-Rhein-Sieg in collaboration with the student body and the Linux/Unix User Group Sankt Augustin.
I attended FrOSCon last year and found it a very pleasant conference to be at. I gave two sessions about MySQL Backup and Security and the MySQL Business model, which both had a good audience and went quite well. I will definitely consider going there again this year, still pondering about the topics of my talks... The CfP ends on June, 4th, so make sure to turn in your suggestions in time!
If you are looking for a very well organized OSS event with lots of good technical content in a relaxed atmosphere, consider visting FrOSCon this year! I look forward to being there again.
Due to a small mail filtering glitch we did not notice a number of new feed submissions for Planet MySQL that had been sent to us via the submission form since the beginning of the year. Doh!
Today I discovered them in a separate mail archive and have now added all the ones that were not spam or unrelated to MySQL.
So if you recently submitted your RSS feed and you don't see it aggregated on Planet MySQL by now, please resend your submission. Thanks and we're sorry for the delay and inconvenience!
Long time no blogging! I hope PlanetMySQL finally picks up my posts again, I really miss the additional audience
We recently received a request from the OpenISR project about adding the Eclipse public license to our FLOSS License Exception. As it turns out, it is almost identical to the Common Public License (CPL), which was already included in the exception. So the decision was fairly easy - version 0.6 of the FLOSS License Exception now also covers the Eclipse public license.
What is the FLOSS License exception all about anyway? Our intent:
We want specified Free/Libre and Open Source Software applications to be able to use specified GPL-licensed MySQL client libraries despite the fact that not all FLOSS licenses are compatible with version 2 of the GNU General Public License.
In other words, we want to make it possible for more non-GPL applications that are licensed under any of the listed OSI-approved licenses to link against the MySQL client libraries. The term
exception may be misleading here, what it really does is widen the scope of the client license and make it more compatible to applications that are not under the GPL.
