FrOSCon CFP closing up, Drupalcon Barcelona (web) registration open!

This year, for the first time, a big two day Drupal event is going to be organized in Sankt Augustin, Germany as part of the FrOSCon 2007 conference (25th-26th August, 2007). Robert Douglass has more to say on this on the dedicated Drupal group, looking for speakers and sponsors for the event. The call for papers deadline of FrOSCon is closing up, you only have one week to propose a session on Drupal (or any other FrOSCon fitting topic) for the conference! Update: The Drupal session submission deadline for FrOSCon was extended to 1st July!

In the meantime, the organizers of Drupalcon Barcelona 2007 (19th-22nd September, 2007) are going forward too. The web registration is already open, which allows you to send a session proposal to the organizers. Although it is not clearly communicated whether the so-called "web registration" actually means a conference attendance registration too. The session description field also sports a limited WYSIWYG editor, which I don't think was a very good idea, but anyway, let those sessions go in! On a related note, Drupalcon Barcelona also has a design contest for the conference logo, which will be printed on t-shirts, name tags, leaflets and so on. This design contest dealine is even closer, only three days left to participate! The design contest deadline was extended until June 10th, and some nice proposals are already in!

Being an organizer of several conferences here in Hungary, I very much appreciate the work that goes into organizing these great events, and I can't wait to be there to meet some Drupal developers I did not meet for some time now (or even not at all)!

Workflow access permissions and workflow support for XLIFF tools

Lately I have been poking around workflows to better support translators. The localizer module suite has no built in workflow support, and i18n module suite has a very simple and limited built-in workflow, so for complex workflow requirements, people need to look elsewhere. Luckily, respected members of the community maintain the workflow and actions modules, which allow for setup of more complex workflows.

Pro Drupal Development book in the mail

Pro Drupal DevelopmentI received my signed copy of Pro Drupal Development around an hour ago from John K. VanDyk, and immediately rushed to the 18th chapter (on localization), to see how it shaped up at the end. I was helping out with reading the manuscripts of that chapter to help readers get the most realistic view of how locale module helps their life, what are the culprits, possibly bad routes to avoid, as well as side effects of some settings. It was a pleasure to help out on the book, and (as a result) a long time waiting for the book arriving at my house.

I thought I can beat Dries with posting Dries-style photos of the book (evil grin), but just found that he published his usual photo shoot pieces earlier today. Anyway, my photos are up on Flickr for more sharing pleasure.

Being a visual type, I would ensure you that the visuals (flow charts, figures) in the book are very informative, and help a great deal in understanding how things work in Drupal 5. This is a must have book for aspiring professional Drupal developers! To quote Dries' foreword: "... there is nothing that stops you from becoming the best Drupal developer in the world. The only limitation is your willingness to learn."

Tags: 

Busy months ahead for me

Well, back in 2003 when I joined the Drupal developer community (got my welcome mail from the drupal-devel list on September 15, 2003), I haven't thought I will be that involved with the system a few years down the road. It was (and is) a rather cool tool for a big Hungarian web development community website I was migrating from some ugly CMS... Now I do so many things around Drupal that it is not easy to track:

More friendly translators guide with Gliffy

On the heels of my recent announcement that thanks to Raimund Bauer stepping in, the translation template extractor is now a separate project, I decided to look into where does this change need to get propagated into the Drupal Handbooks. To be honest, I have not really been around in this part of the handbooks before (although I am a lead member of the Drupal Hungarian translation project), and what I found was not actually pleasing. The Translator's guide seemed to be intimidating for newcomers, basic questions are sprinkled all around the guide's pages. The start page was in the first paragraph talking about what is *not* documented there, instead of trying to help people grasp how things work here.

So I decided we need a little rewrite, and I should put my keyboard and mouse where my mouth is (pun intended). While writing up the new introduction page, it turned out that a figure would show a lot more than what can be described in a reasonably short introduction (so people will actually read it). I tried to come up with a figure showing how Drupal core and contrib translations work, how translation templates are generated, tried to emphasize that existing work should be reused, where should translators put these files, and in what package these files will end up in. This resulted in a seemingly complex figure, but with using some hopefully sensible colors and text, I managed to simplify it as much as I was able to. The most important for me was to provide an overview and to communicate the tasks of a translator, and it' connection to the packaging system.

Drupal translation processes

Doing the actual figure was easy, given a great tool to visualize my thoughts. Gliffy is an incredibly fun tool, and it does a lot! It is a complex Flash application, so desktop like I always right-clicked (and got the Flash context menu which did not help in creating the figure). It is a free and easy to use online tool to create figures such as the one shown above. And it is not a closed tool, as far as exporting as SVG, PNG and JPEG goes. Unfortunately it does not export in a diagram format, so you cannot reuse your figures in Dia for example, but that was perfectly acceptable in this case.