[development] Time to take away RTBC from every Joe

Omar Abdel-Wahab owahab at gmail.com
Thu Feb 21 09:07:09 UTC 2008

+1 for what Angela said.

I also see we might need to document somewhere that marking a patch as
RTBC is a responsibility towards that patch in terms of testing,
reviewing, etc...

We can't have rules for everything, sometimes pointing out problems
and mistakes is a better approach.

On Thu, Feb 21, 2008 at 9:19 AM, Angela Byron <drupal-devel at webchick.net> wrote:
> Karoly Negyesi wrote:
>   > Onwards, I would like to see a small handful people (me not
>   > necessarily included!) to be able to RTBC core patches. As we go on,
>   > more and more people will misunderstand what this means. A nice
>   > pyramid, a few people on top deciding the patches, a few more culling
>   > the flood of patches for them. As there is already a permission for
>   > this, a little hacking (which I am willing to do) surely would make it
>   > possible to have it just for project 3060.
>  No thanks.
>  My guess is that this small handful of people who'd have this permission
>  are the same small handful of people who are already doing a bazillion
>  other things in core, and suddenly moving issues to RTBC would become
>  their full-time jobs (or at least part-time).
>  Further, instead of these "problem" users changing the status
>  themselves, they now start PMing and e-mailing this small handful of
>  people "RTBC my patch!!" which I can tell you right now is going to
>  cause even further grating of nerves. :P
>  A better approach? Education. Document the best practices, *teach*
>  problem users what the proper usage of "RTBC" is, and they'll teach
>  others, and so on and so on.
>  -Angie

More information about the development mailing list