In January, Jiří Eischmann started organizing the GNOME 3 Launch Party in the Czech Republic, with the obvious goal to celebrate the major release of GNOME 3, to promote and talk about the next generation of the GNOME Desktop in front of the Czech audience interested in FLOSS and technology generally.
A rather informal event in its form, organized by the Czech Translation Team, will be hosted on Saturday, April 9, 2011, at the Student Facilities in Strahov (Strahov Dormitory Campus), Block 7, Prague (Areál kolejí Strahov, blok 7, Praha 6). See Google Maps.
We will start at 15:00 with the following talks:
- Tomáš Bžatek & Tomeu Vizoso: GNOME 3 from users’ and developers’ perspective
- Vojtěch Trefný: Unity as an alternative way
- André Klapper: Release and bug management in GNOME (in English)
- Petr Kovář: Czech localization
Visitors will be offered fresh Live USB Images running GNOME 3 based on Fedora. After the conference part (around 19:00), there will be a social event/informal meeting in a near pub.
There may be some further news from organizers regarding this event, so follow the appropriate Czech GNOME 3 Launch Party page, or this blog.
Come to visit us and join the GNOME 3 fun in Prague!
You are a developer and you want to keep your project moving forward. You set up various communication channels and organize an open community around. Your vivid project starts to attract new people, amongst them are people who intend to contribute code to the project. Great, because that’s what you were waiting for when you started building your FLOSS community.
Naturally, you do not allow anyone on the net to directly contribute code without any, more or less formal, review process. That’s good, since you care about happy community of contributing members, but you also want quality that you can be proud of.
And then there’s the world of community localization. You are most likely not a polyglot, and you can hardly do a review process with tons of languages from around the world, apart from making sure that the localization work you’ve been provided is not missing some obvious bits of technicalities. So you simply open the submit process for l10n to anyone, or reach to some nice outsourcing tool, hoping that translators will eventually cope with it and the project’s l10n will be worthy, as is the code. But really?
But Really, It’s For Your Own Good
That is, not to stick to the openness at any cost. The fact is that, quite similarly to the code contribution, the quality work in l10n will not miraculously show up. It needs reviews, proper management, suitable workflow. It needs community.
One of the first things you need to do if you want to facilitate building a real l10n community is to set up, more or less formal, rules. So you turn the translation teams option on. You encourage work in translation teams & projects, so your translators can interact with each other and share knowledge. You keep an eye on l10n. You are responsive to the needs of your translation team members. Then you are a great developer with FLOSS project that deserves quality & efficiency in l10n very much comparable to that of the professional (as in commercial) translators with plenty of ISO & DIN certificates. And your project has it. For free. (Almost.)