Hi Chris,

yes, the next issue hunting party will be held on 13th of January.
The Wiki page for this event is in preparation until now ;-). So
stay tuned. I will also work out a blog entry for this event at Gullfoss (blogs.sun.com/gullfoss) together with Stefan Baltzer. He will coordinate and lead this event.

Wiki page :
http://wiki.services.openoffice.org/wiki/Issue_hunting_party#Issue_hunting_party_13th_of_January_2009

Thorsten


Christoph Lukasiak schrieb:
just for memory .. for further hints, questions or just to work on issues together with other new or more experienced community members, supported by experts from different areas you can join the next irc chat:

"cleanup coordination chat"
irc://irc.freenode.net/
in the group #qa.openoffice.org

Christoph Lukasiak wrote:
moin all qa'ing and bug writing folks,

as we recently got a new OOo version (3.0) and soon get a new year (2009), right now is a very good point to clean up the issue tracker (especially issues for versions before the OOo3.0 ;) .. so please recheck your older and maybe several other issues, if they are still valid and write your comment into the issue or close them if not.

if anyone reworks only a few of them, it would really help to have a better start into the next year and next version (also the attention for the newer ones will increase much) => so do not ask what OOo can do for you (i think everyone of you is using it for a long time and appreciate it), but what you can do for OOo .. only a small step from you can became a big step for OOo :) thx


happy and successful new year for everyone
bye chris

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to