Posted by Itangalo on March 19, 2011 at 11:41am
I just started a wiki page that describes the objectives of the new helper team for the Rules project – currently only in preliminary terms.
Since you can't write comments to wiki pages here at g.d.o, this is a post for discussing the content of the wiki page.
Comments
Rules Enforcer Squad?
Just for the fun of it, I would like to propose the team name Rules Enforcer Squad. What do you think about that?
+1
Well, what can I say other than "yes please!"? Fago and I do not have the time to deal with all issues (especially with support requests), so we already rely on a strong Rules user community that helps us to manage the issue queue (thanks to you Johan and opensanta ;-). I think this initiative can be a success if you manage to recruit some more community members that have a passion for Rules and make them feel responsible for the issue queue.
The wiki page looks good, the only thing that I feel a little uncomfortable about is the assigning of issues to either me or fago. I want to know about an issue before I get assigned to it, otherwise it feels like somebody just wants to load off some work on my shoulders. I want to pick my work voluntarily. We can use the issue priorities to make important issues more visible.
Also, we should use the full power of the issue queue states. Has a patch been inspected and tested successfully by someone? ==> Mark it RTBC. People tend to classify everything as a bug report ==> filter out the support requests and change the status accordingly.
Sounds great
This sounds great to me. Do you think we can start this without waiting for fago to return from vacation?
//Johan Falk
I'm still here! It's my last
I'm still here! It's my last day though.
I can just second everything klausi wrote, the idea is just awesome and I'm really looking forward to see how it goes :) The wiki page looks great to me, so let's get it started asap!
Maybe we need to clarify how
Maybe we need to clarify how maintainers work, so that a bug squad can work efficiently along the process. Depending on the time available a maintainer must at least check the RTBC issues and either commit or reject the patches on a regular basis. Otherwise the work of new contributors gets lost or delayed, which is obviously bad and harms the evolution of the project. If there is more time a maintainer should check the critical bugs list (issues that render the project useless, security stuff etc.) and propose solutions or code. If there is even more time a maintainer should look at the "needs review" patches and comment on them. And if there is still time left a maintainer will probably look through the newest issues with the highest priority and work on them.
Currently our RTBC, critical and major issue lists are pretty small, so that works out in principle. The normal bug report list is quite long and I can spot at least one issue that does belong to the Entity module, not Rules. The support request list is overwhelming, we should think about how we close old support requests.
So the main tasks of a Rules issue squad would be handling the support issues and the normal/minor bug reports.