drupalcon szeged

Szeged and the future of MediaRSS

For the first time I gave a presentation at a Drupalcon. I was a bit nervous at first, but all ended up well with some nice reactions from other people. It also convinced me completely that I should separate all MediaRSS functions in the PicLens module into a separate contrib called MediaRSS API. Not sure when I'll get to this, but it's the most logical thing todo, but I first need to clean up my issue queue since I didn't had a lot of time this week to work on my existing projects.

On the contrary, I had a good time networking at Szeged Drupalcon meeting a lot of new people and catching up with the ones I knew. I also started working on Views UI Permissions after some brainstorming with old colleagues after the last session on thursday. The first version was online friday morning, so in a way I did my own code sprint. And I was one of the winners of the Testing Party, hurray! And a first little test ended up in MediaRSS support for Kris Vanderwater's Imagefield Gallery project.

Anyway, back in Belgium now, allready counting off to the next Drupalcon. Big thanks to the Drupal community, you guys so rock!

Getting more reviewers involved for Drupal 7: unofficial BOF

There has been some discussion on the mailing list previous week concerning lack of reviewers for drupal patches. One of the reasons that came up was the fact it takes some time to set up a new clean environment to test a new patch. Given: download latest head (or better checkout from cvs), create or empty (existing) database, setting permissions, apply patch, add content, test by hand, run all simpletests, do some benchmarks (with every possible caching in mind) .. it does involve some point and click.

While doing some benchmark tests this week for the DBTNG patch (congrats Crell!), I probably repeated this complete set of tasks a couple of times - however, I didn't mind, it's for the benefit of everyone: Drupal, patch writers and also myself. Wow, that really sounds terribly squishy right ?

Anyway, at DrupalCon Boston, Roel and I experimented at bit with DAST, got it working on command-line and also within an eclipse environment, but never really worked out a clean battle plan to make it perfect. Our plan for Szeged is to work again on this, make it completely perfect so anyone on a *nix environment should be able to setup a new head with only one command (or click in eclipse) in like only 30 seconds. We'll create a dast profile and come up with some other tricks - maybe one or two other small bash scripts and after that, following should be possible:

  • CVS checkout from HEAD
  • Install database
  • Generate content with devel/drush
  • Apply patch
  • Run all simpletests (optional)
  • Run benchmark tests (optional)
  • Generate reports from previous two actions

I know, this sounds ambitious, but it really isn't *that* hard to achieve. If you have other ideas or if you're interested in helping out, contact us, we are those guys carrying tons of chocolate for the Testing Party!

Shameless promotion

I just submitted my session proposal for DrupalCon Szeged. I got a mail from Nathanial/catch asking me if I'd be interested demoing the piclens module at the core/contrib/trends track. It won't be a very long session, so if someone else has an interesting topic to talk about cool (third party) applications/integration, step up and submit your proposal. Let's show how sexy your site can be with Drupal!

Oh, and don't hesitate to vote for my session of course ;)

Joined forces in porting?

Drupal 6 is out now for almost 5 months, but a lot of modules haven't been ported to D6. Yet people seem to screaming for them and with cck and views 2 almost being ready, maybe it's time to join forces and help out other contrib module maintainers. I've got a couple of thoughts I want to throw out in the wild and see if anyone else is interested in this topic.

Which modules?

This won't be easy to decide. It's not because I'm not using module foo for reason bar while other people use it everyday that we should ignore this. Au contraire, there are a lot of them out there used by many people (read: non-technical-geeks with little programming knowledge) which can't be ignored at all. There is a list on http://groups.drupal.org/contributed-module-status where mostly maintainers themselves post the status of their module. Maybe we could create a list (wiki-style) in this group with modules people would like to see ported where activity in that direction seems to be non-existant.

When ?

Anytime! We could even submit a session or a BoF at the upcoming Drupalcon in Szeged or even sit down with some people during the code-sprint and see who's willing to take up what during that time. I'm also proposing a new irc-channel called #drupal-porting (duh) to announce your porting time. After that, your idle time should at least be one hour before you may speak again ;)


Easy: submit patches into the issue queue so people can review and test. Using the coder module, you should be able to get small modules ported in no time at all. You're free to use vim and your knowledge of the api any time if you rather want to do it the hard way of course.

Who will do what ?

That's for every individual to decide. But, if we have a list, we can somehow try to delegate so not everyone is working on the same port at the same time. Everyone is invited to help out, but let's organise and make Drupal 6 a pre-killer release :)

Off topic, I just signed up to Drupalcon Szeged. I you haven't , now is the time as the deadline untill the 1st of july is almost there. It's cheap, just go for it!

Subscribe to RSS - drupalcon szeged

You are here