On 01/17/2013 02:14 PM, Chris McMahon wrote:
Compared to the current situation, this wheel looks powerful and at the same time relatively easy to set up. There will plenty of things to improve and fine tune, but probably none of them will require to stop the wheel.
What do you think?
Our object here is to foster a community interested in participating in bug and testing projects. You've described one way we might create some projects, but I'd like to know more about your ideas for communicating with, creating, and supporting the communities for such projects. What makes the wheel valuable to such a community, and how do they know?
We don't (and I don't aim to) have the perfect answers. What we now is that every iteration will be probably simpler and better than the previous one, because we will learn and acquire an inertia.
For instance, in my previous message about the Language features testing week I was proposing already specific tactics to reach out to potential participants in non-Latin-script Wikipedias. Once the goal for the following week is defined I'm sure we will have good ideas to reach the appropriate audience.
The wheel is basically a way for us to get started without more delays and then keep organizing sprints like a clock.
It is also a way for testing & bug management contributors to know what to expect. Every week there is something. Every month there is at least one activity of the specific flavor.
Maybe you know paella? http://en.wikipedia.org/wiki/Paella
There is one basic rule for a good paella:
"Paella doesn't await guests: guests await paella."
If we serve paella every week in a timely manner, people will come. If they enjoyed it they will repeat another week, bringing more guests.