Hi,<br><br> Two additions:<br><br> * krush days could be helpful to check the new features in the beta phase (of course, it depends on being able to produce live media with up to date KDE SC).<br> * who to contact to get something published.<br>
<br>Regards.<br><br><div class="gmail_quote">2010/10/11 Michael Leupold <span dir="ltr"><<a href="mailto:lemma@confuego.org">lemma@confuego.org</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi everyone,<br>
<br>
I have to admit yesterday's BugDay organization lacked a bit. Part of it<br>
was my fault as I wasn't online from Wednesday to Friday (sorry for<br>
that), part of it was due to our announcement being pushed to the dot<br>
too late.<br>
<br>
However I figured that with more people knowing about how we organize<br>
BugDays and keeping an eye on it we could improve the whole process -<br>
even if that might take some time. As a starting point I assembled some<br>
ideas and thoughts about how stuff currently works on the following page:<br>
<a href="http://techbase.kde.org/Contribute/Bugsquad/OrganizingABugDay" target="_blank">http://techbase.kde.org/Contribute/Bugsquad/OrganizingABugDay</a><br>
<br>
I'd say half of it are hard facts about the current procedure, the other<br>
half is made of ideas and wishful thinking :-) I'd really appreciate if<br>
you all could have a read of the page and help improve it step by step.<br>
One major goal of me is to get a timetable which contains what to do and<br>
when to do it (eg. publish a dot article 2 weeks before the BugDay).<br>
<br>
Thanks and regards,<br>
Michael<br>
<br>
_______________________________________________<br>
Bugsquad mailing list<br>
<a href="mailto:Bugsquad@kde.org">Bugsquad@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/bugsquad" target="_blank">https://mail.kde.org/mailman/listinfo/bugsquad</a><br>
</blockquote></div><br>