Skip navigation.

Log in | Sign up

El Blog de Pacho

"Antes o después tendrán que rendir cuentas"

La realidad de la central finlandesa de 3ª generación

Así combate la crisis Esperanza Aguirre

Mandriva Triage Team needs your help

Hello

I want to remember everybody that Triage Team is always needed of manpower. Currently, we are only 8 members. Most are volunteers that have other tasks to do in real life, then, you will see that we cannot triage your bugs as fast depending on our real life and available free time.

For example, some months ago, roudoudou and Skeletch did a really great job but, like me, we don't have enough time always, then, currently most of the work is being done by Ahmad because the remaining members are too busy for doing more. What would occur if Ahmad or anybody else is unable to dedicate as much time for triaging in the future?

This is the reason for suggesting you to join to BugSquad: if we are more people, everybody will have to do less work, having more free time and, also, being able to dedicate a bit more time to every report for triaging them better.

We don't expect you triaging 200 bugs, we welcome small contributions also ;-), as they will help all Triage Team.

The way for joining is really simple: if you have a certain level of familiarity with Linux in general, Mandriva Linux in particular, and the Bugzilla bug tracking system... simply subscribe to our mailing list and send us a message volunteering.

We will guide and help you to get enough knowledge about Bug Policy, triaging and bugzilla management and, then, give our aproval to you appliance.

As a start point, I suggest you to read the following links (if you detect any problem with them like inconsistencoes, outdated info or anything else, please contact me for fixing them):
Triage Team - How to triage bugs
Bug Policy
Triage Guide

Thanks a lot

Viñeta

Patch review week

Michael Scherer just announced this:

Hi fellows packagers,

( and fellow cookers too, by the way )

As announced by Anne some days ago, next week will be devoted to package cleaning. By package cleaning, this mostly mean patchs cleaning, as explained on http://wiki.mandriva.com/en/2010_patchreview

The goal are multiples :
1) be sure that our contributions, when relevant, are integrated upstream, since this ease the maintenance, and also enhance the free software ecology. After all, the sharing of code is the heart of our ideals.

2) be sure that the patchs are still needed, less patch means less problem when updating, less complexity, and less work the next time we do such a week.

3) be sure that patchs are annoted, so we can know why the patch is here, what problem does it solve, etc, etc.

For this event to be sucessful, we need some kind of coordination, and we also would like to be able to count how much packages where cleaned.

So here is what I suggest :

1) use a tag [prw] ( for patch review week, the shorter, the better ) in commit when we cleaned a rpm

2) go in the irc channel #mandriva-commits, and see what packages are currently cleaned,

3) even if I doubt many conflict while arise, it would be good to announce what packages or packages types you are trying to clean. For exemple, games, gnomes, kernel related, etc. Please announce it here, so people can organise them self in small team ( even if this is a team of one :smile: ). Priority is to clean main, but you are free to work on contribs too.

4) for each patch, see if it still applies, and if the patch is still needed. If not needed, drop it,

If needed, add a description, the origin of the patch ( ie, upstream, other distribution ), and a possible bug number or url, in the spec file as a comment.

If needed, and relevant for upstream, try to clean it and submit it upstream ( after checking the latest code of course ). Also add that it was sent upstream, how, and possibly with a url.


We do not plan to parse the information or anything, so the format of the entry is free.

Of course, we will not be able to clean everything in one week, even with our super packaging powers. The goal is to start, and to do the cleaning later when it is needed, when we see a package was not cleaned.

And we would also like to make sure that this operation will enhance the karma of the distribution, so do not hesitate to post about it on your blog ( and if you are a packager not syndicated on planet mandriva, just ask the PM team to add your blog ).


So to start, I announce that I plan to clean python, and python modules.

See you tomorow with your broom to clean the svn.

--
Michael Scherer

SoundWeek ends today

SoundWeek will end soon. Thanks to all people who reported issues and, of course, thanks a lot to Herton for helping us with this.

Only a few bugs have been send during this week, maybe because only a few read the BugWeek announcement or maybe because ALSA is working fine now ;-)

Anyway, this bugweek has helped to fix some issues in future kernel updates for 2009.1 and cooker.

New "bugweeks" will be organized soon, if you have some suggestions about what should be covered on them, feel free to comment on this post or simply mail me directly

Best regards!

Anatomía de Berluscolandia

Id y contad lo que habéis visto aquí

Sound BugWeek has started

You can start to file bugs related with this SoundWeek from today :-D

Sound BugWeek from Monday/June/01 to Sunday/June/07

Regards

Garzón y las casualidades

Download Opera, the fastest and most secure browser
July 2009
S M T W T F S
June 2009August 2009
1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31