Re: New year cleaning up database unconfirmed issues party

On 3/16/2010 2:45 PM, Marc Santhoff wrote:
> Am Montag, den 15.03.2010, 11:02 +0100 schrieb Christoph Lukasiak:
>> Christoph Lukasiak wrote:
>>> moin database testing folks,
>>>
>>> i would like to start a 'new year cleaning up db unconfirmed issues'
>>> week (or two) to reduce this issues maybe under 50 (~120 last week,
>>> under 100 at the moment, after diligent work mainly from drew, as i
>>> know), not let any issues untouched and to check if they are still
>>> valid (specially the older ones) .. so please support the OOo QA Base
>>> team with this work and let us keep our area clean and up-to-date.
>> now we are down to 95 issues .. that is still pretty much and not many
>> people had helped (excluding a few very diligent ones, thx) .. that is a
>> rather easy job and everybody can help and support us with rather little
>> time and engagement .. so please stop your 'what can the community do
>> for me' attitude and give a little bit of the support back, what you get
>> here every day
>>
>> .. so let us stretch this action for another week and see if we can more
>> than this !
>
> Facing the danger to sound stupid I'd like to say:
>
> I'm not really sure what the expectations and the formal necessities
> are. E.g. I'm not actually a project member of "dba" but "de". And I do
> not know if I can set issues to "confirmed" state or if I need special
> permission or so.
>
> The small amount of time I can spend every now and then on helping
> would be eaten up totally by digging up all relevant information pages
> on the projects site and the wiki.
>
> Could you give a short guideline in a few sentences or point me to a web
> page explaning without to much verbosity?
>

Hi Marc,

Great questions.

Two things come to mind.

One is that really all one needs do is request the ability - the 
question is to how I suppose?

Secondly Christoph has on a few occasions, as have others with other 
projects, tried to setup bug hunting days and issue confirmation days.

This usually included the use of irc as a meeting place for participants.

The response was less then stellar - I suppose - as I was one that 
didn't make it. OK, I have good excuses but you know what they say about 
excuses.

With regard to the second thought - I feel that this use of 'a day' is 
still valid, but instead of hit and miss days rather more scheduled days.

What I would propose is that I just start this by picking a day of the 
week perhaps and schedule my work on confirmations with an explicit 
commitment to be on the irc channel at that time. Then let people know 
they are welcome to join me, perhaps I can help others be more efficient 
with their time. I will just put up a reminder now and then - if that 
sounds ok to the group?

For the first part - how to get can confirm rights and who to ask - ?

A few days ago I was responding to a email on the users mailing list and 
before I did took the time to enter the OO.o website as if I where a new 
user (I tried anyway), no logon account and had to read all the menu's 
to find my way around, that wanted to report a bug. I rather thought it 
was getting fairly good given the last changes to the QA pages.

Wondering as I type this now, is there a good 'I want to be a QA 
community tester', survival guide style perhaps, page - don't know, 
suppose I'll go look.

Drew