geekstuff.org
Things have been hectic since the beginning of the PyRoom project. All my free nights tend to be squeezed by this process. Things are fantastically new to me, and I'm learning a lot from this ; even if I'm not doing the right thing at the right time, I try to do my best to follow the quick rate of my fellow team-mates.
- The Pyroom Team (contributors of-all-trade) has now 13 active members. Any contributor is accepted: translators, designers, hackers, writers (for the documentation), bug hunters,... I do accept anyone on this workgroup.
- This gang usually gathers on IRC, on the #pyroom channel on freenode. The discussions are logged to keep track of the debated topics. Discussions are really constructive, it's a real pleasure.
- To avoid annoying team members by the amount of emails sent by launchpad at any bug report change, I had to setup a Bugsquad team. It's the absolute best way to be aware of anything related to PyRoom, as the bug reports are getting opened / close. On some bug reports discussions / debates are open to anyone, and not only the Team. Very nice. Registration to this Bugsquad team is completely open and unmoderated. If you want to get spammed, that's not my problem...
- I've created a Pyroom Dev Team at the same time. This team is closed, since you can only get in if you're invited. This team is only for people allowed to branch / merge / push code on the main branch and releases. At first, I was the only one to have permission to update (push) the trunk branch: it was pretty uneasy, because hackers tend to push their branches faster than me having the time to pull theirs, compare / merge and repush back. It has been decided to pick a small group of commiters ; this means that pushes could happen faster, and they're pretty secured, because we only accept people we can trust. We're six at the moment, and this figure shouldn't change much, I guess.
- It's damn simple. Monocolored. Without bling: the PyRoom.org website is online, powered by a Django module nicknamed "Fatpages". My favorite framework web already owns a "flatpage" module. But I missed a few features, and Model inheritance is still only available on an experimental branch. Then I decided to borrow code from django.contrib.flatpages and hack "fatpages", that is to say: "flatpages that ate too much". The code is shamefully ugly, but it's functional. It might be refactored when my todo-list will nicely decrease.
- While we're at it: we decided to publish a "legacy forum edition" of PyRoom. It's a slightly improved version of the one found on ubuntuforums.org. Half a dozen of tongues are now supported, and a few features added. This version has been ditched from the main branch before the grand code reorganisation we decided and put together last week.
- CALL TO ARMS: The kind translators that did translate the pre-code-release would be very nice to update their translations in Rosetta. There are only a couple of changes, but it would be very nice to have a clean translation in every language on earth
Well.
Here is what's happening when you wait too long...