El Blog de Pacho

La comunidad hispanoparlante de usuarios de Mandriva Linux (BlogDrake) esta teniendo un problema temporal con el dominio blogdrake.net , los usuarios del sitio por favor diríjanse a http://blogdrake.org , si no carga por favor limpien la cache de su navegador e inténtenlo nuevamente.

Hello!

Yes, I am again asking for help to people that want to see new releases being even better. If Triage Team is better and, then, faster triaging bugs, assigning them, handling them better... you will see that upcoming Mandriva releases will become even better, because assigning and handling reported bugs properly, will allow maintainers to get them faster and to be able to fix them sooner.

For doing this task, is important to have a bigger team because, currently, we rely on free time from every team member as we are volunteers, then, for example, this last week I have been unable to do much triaging because I got sick (due flu) and, once I got better, I had to do a lot of job in real life. Then, as we are volunteers, Triage Team needs to grow more to allow us to make triaging tasks shorter and easier.

If you are, for example, a forum/mailing list member with a bit of experience with linux systems (you don't need to even know about programming, for most bugs, knowing about simple system administration will be enough), we will really be happy to see you joining us :-)

For that, simply visit:
http://wiki.mandriva.com/en/Triage_Team_-_How_to_triage_bugs

Thanks a lot

After one month of inactivity, I returned to the work and triaged some remaining bugs. Thanks to recent recruits, the list was shorter than other years :-) but still a bit large (more than 100 untriaged bugs). This is logical because, even with the great help from new people, we are near the next Mandriva release, then, more bug reports are sent.

As it's really important to keep untriaged bug list as short as possible (I think that having near 25-30 untriaged bugs would be fine), help is still welcomed :-), then, remember to read:
http://my.opera.com/pacho/blog/2009/06/16/mandriva-triage-team-needs-your-help if you are interested on help us.

Thanks a lot to all!

http://blog.launchpad.net/general/launchpad-is-now-open-source:

This is a post I’ve been looking forward to for a long time:

Launchpad is now open source!

We released it today under the GNU Affero General Public license, version 3. Note that although we had previously announced that we’d be holding back two components (codehosting and soyuz), we changed our minds: they are included — all the code is open.

Big congratulations (and thanks) to the Canonical Launchpad team, who worked overtime to make this happen sooner rather than later, and to Mark Shuttleworth, whose decision it was to open source Launchpad in the first place.

Rather than repeat the various release announcements, I’ll just point to them:

* launchpad-users mailing list
* Blog post at Canonical.com
* Press release
* The development wiki
* Instructions for getting the code.

The Canonical Launchpad developers will be on IRC in channel #launchpad-dev on irc.freenode.net. That’s the place to go for real time development discussion and questions. For usage issues, #launchpad is still the place, as before.

The mailing list is launchpad-dev {AT} lists.launchpad.net, which you can subscribe to by joining the ~launchpad-dev team. Again, that’s the development mailing list; user questions should still go to launchpad-users {AT} lists.launchpad.net.

Please bear with us as we learn how to be an open source team. Many of the Launchpad developers have open source experience already, of course, but as a team we’ve been working on Launchpad in-house for some years. This is a big change. We’ve been looking forward to it, though, and are ready and eager.

That’s all. Happy hacking :-).

-Karl Fogel

Great to see this great tool opensourced :-D