Everything is a Freaking DNS problem

Fosdem 2010 was my 10th fosdem Edition (including the first OSDEM)
As every year Fosdem suffered even more from it's own success.

On Friday evening ther was the obligatory Beer event... however as people need to eat to .. the Devops crowd fled the scene

I had made reservations for a 20 something group and with the CentOS crowd joining us (as there was some overlap anyhow) we were 25 when we arrived in the restaurant .

Dinner and Discussions were great .. I learned about some new projects and we had some insightfull dicussions on how fat your thin foil should be ...

After dinner we went back to the Beer Event were lots of Free Beer was tasted ...

Saturday was the first full day of Fosdem, as usual Fosdem was the victim of it's own success , too much interresting stuff to see .. too little time.

Lots of Devrooms had the "FULL" sign put up more than you want as a visitor ...
I never even made it into the Drupal or NoSQL rooms :(

Sadly I had to correct Ploum's first law but for a lot of people .. Fosdem each time means the battle choosing which presentation you'll go to ... If you can even make it to the talk .. as usually the the hallway track is much more interresting :)

The MySQL devroom was on sunday but on saturday the crowd met in an Italian place nearby the Fosdem campus to get to know each other and chat a lot ..
The discussions ranged from French vs Canadaian and the future of Forks

During Saturday afternoon @patrickdebois suggested a Devops Meetup for Breakfast ... and some how that also happened ...

When I arrived at Fosdem on sunday morning they were still there :)

I spent the biggest part of Sunday in and around the MySQL devroom listening to a bunch of interresting talks

My own talk went fairly well given the time constraint .. sqeezing content for an hour in 20 minutes means you can't really go deep into the topics ...
My initial plan was to only focus on Pacemaker integration however the community had voted for the overview talk :)

After my own talk it was almost time to head to the Janson auditorium for the Footnote of Greg Kroah-Hartman, and as on any Fosdem .. there once again had to be Beer

Fosdem is coming up again .. It's going to be the 10th edition already So it's going to be 2 days and nights of fun, tech and geek stuff

Lenz already posted the announcement , but allow me to recapitulate.

The MySQL & Friends meetup is on saturday evening , we'll meet around 1900 in front of the under the big tree in front of the AW building...

As with the Devops Meetup you can once again vote for your preferred food

The crowd voted and Favoured an Italian place , so I've made reservations for a 15+ persons group at Sogno d'Italia which is walking distance from the conference location, so there'wont be any hassle with cars and transport

The schedule for the Devroom is also already available

See u there :)

So when you setup an aggregator there's this one thing you miss from a regular planet ...the list of blogs with their individual Feeds.

I wanted to use this for planet.loadays.org again and realized I don't know where I got this snippet from or if I wrote it myselve or whatever .. but I do realize that unless I document it here I won't be able to point other people to it again :) So just create a block like this one :

<?php
 
 
 $subscriptions = db_query('SELECT title,link,url FROM {aggregator_feed} ORDER BY title');
 while ($list = db_fetch_object($subscriptions)) {
      print "<a href=\"$list->link\">$list->title</a> (<a href=\"$list->url\">feed</a>)<br>\n";
 
      }
 
?>

Dear Drupal Community,

If any of you are interrested in getting a packaged version of Drupal 6 into Fedora's EPEL repository (Extra Packages for Enterprise Linux) and therefore usable in RHEL and Centos,
please comment on the Bug I filed to get it's introduction started.

Any pitfalls, benefits etc are welcome ..

thnx in advance !

A couple of weeks ago I was once again manually installing Drush as there were no packages for CentOS / EPEL or whatever, apart from the needed patch to get it running on a 5.1.X RHEL php

I had found this thread on Drupal.org mentioning that a package already exists
however David had not answered the exact location yet
So I created a drush package with a with the above mentionned patch and sent it to Jon Ciesla again he gave some suprising feedback ;)

Drush itself might need to be modified in Fedora. It seems
like one of the major functions of drush is to install and update
modules. That's great for modules we don't ship as rpms, but we can't
allow drush to modify modules that we ship.

This feedback pretty much leaves me with 3 options.

The first one is the easiest one, I just forget about packaging drush for Fedora.

The second one would require me to patch Drush so that for all existing drupal modules that have been packaged for Fedora, Drush will call yum to install them. This obviously would create a lot of work maintaining this excludelist.

The third one would be to disable the download functionality for Drush in a Fedora/Rhel enviornment, Jon suggested that this would probably be the saftest path.

(Jon also suggested a fourth option, namely removing all drupal modules from fedora and add a prohibition to package them in the Packaging Guidelines, which he immediately called ridiculous.)

I once again understand the problem of the Distribution maintainer, but on the other hand if I were the upstream Drush developer I wouldn't want to see my software severely disabled in a distribution.

So what do you folks think, disable the functionality or not ?

PS. Yes I've contacted upstream , but I haven't gotten a reply yet.

Some of you might have noticed that Fedora 11 and up already have an up to date Drupal6 version, but EPEL , which is what a lot of people are using on their CentOS or RHEL builds only has a Drupal5. I asked Jon Ciesla, who is maintaing the Drupal packages in Fedora why :

Because when Drupal was initially built for EL-5 and EL-5, the 5.x
branch was the current release. It's up to date, 5.20 is the most
recent release, and is still supported upstream in terms of security
fixes. 6 is out, and has been for awhile, but we have the following:

http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies

Since 5.x isn't broken or insecure, it'll be a tough sell to move to
6.x. Once upstream drops support, this may change.

It's a correct answer from a Distribution point of view, but the fact is it is widening the gap between the Ops and the Devs. If the ops want to keep their platform clean we need to have our software packaged on the platform we want to use, which is most often an Enterprise Linux distro, on the other there is understandably no hair on a dev's head that he will be building a new site on a Drupal 5 platform.

So until the Drupal community doesn't declare Drupal 5 dead, RHEL and CentOS users will have to use 3rd party Drupal6 RPMS , or rebuild the F12 rpm from Source again .

Lots of people writing about Snorkle again today ,Monty Says, help saving MySQL

He gives us different options, a , b or c .. but I , and some others, want an option d

No I don't trust Oracle, it's not like they have been a very good Open Source Citizen, yes they contribute to the kernel and other projects but my feeling says it's only because they have to (Kernel, Xen and others ) not because they Want to (thinking about Unfakable etc) , if they would really want to they probably would work with the CentOS community more etc, and as Monty mentions their InnoDB track record could be better.

But on the other hand I don't think the EU should block the deal because Monty wants his baby back , cheap , as honestly imvho that's what they really want, be able to buy MySQL back for a nice price, either beceause Oracle is being forced by the EU to split up Sun, or eventually the deal doesn't come trough and they can buy MySQL back when Sun really goes belly up (which is what probably happens when option a) is chosen.

According to CNN , Oracle has made some pledges about MySQL earlier today.
My main question there however is about the Opposite of option 5. which is exactly what created the problem.

5. Support not mandatory. Customers will not be required to purchase support services from Oracle as a condition to obtaining a commercial license to MySQL.

Yes we want support, but no we don't want a commercial license with it, we want support on the GPL version, which is a problem lots of Open Source vendors struggle with , some of them
force people wanting to buy support to go for the commercial license. And it is exaclty that upselling that got MySQL in the troubles it has today .

Josh Berkus has a point declaring
Dual Licensing dead, just as I he sees much more future in the Percona like model than in the Dual License model MySQL used to have ..

Dries points to one of the comments on
Lukas Kahwe Smith 's Come On Money er Monty article stating
Monty walks away with several millions in hard cash, while [PHP +] MySQL cheerleaders who bet on "MySQL" franchise only walk away with a cute dolphin T-shirt

Which makes me wonder when I`ll be getting a nice Acquia T-shirt :)

As posted earlier Packt was so kind to send me their Drupal 6 , Social Networking for review.

My hopes were high, I was hoping for some info on how to integrate with different existing networks, content about existing frameworks, maybe some mentioning of openAtrium or so, or integrating with Twitter or other existing platforms.

Sadly the book only briefly touches similar content, the Google API , in Chapter 7

While a good read, and a good introduction to Drupal for new users I didn't learn anything till chapter 7 and anything after Chapter 7 ;( And I don't consider myselve as a Drupal Expert

So would I advise the book to anyone, it depends, on who's asking. Personally I'd title the book different, it's a good introduction to Drupal with guidelines on getting userinteraction on your site, but to call that a Social network .. no....

I'd advise the book to an enduser new at Drupal, not to a developer with experience in other frameworks, or even Drupal

by @botchagalupe
on Virtualization, Open Source tools and DNS Problems

What I would like as a feature from Santa,

I would like to be able to report a comment as URL Spam , you know the case where the content of a comment is perfectly OK, but the URL the commenter uses is a link to a NSF, pure spamming or absolutely unrelated site.

There's nofollow etc , but to keep my site clean I'd have to report these commen
ts as spam, however when you start analysing the content of the message and comparing that content to other posts you will eventually get false positives.

So a small option "URL Link is spam, content is acceptable" would probably help all of us