[wp-hackers] The problem with Contributions and This Thread

Fri Dec 31 01:52:05 UTC 2010

On the projects when I used to work in the labs (afrl) this was always a 
huge concern, so what we did was assign them to the most experienced dev on 
the team that knew the ramifications of what would happen.   Boss man 
decided at one point to make a sub release just specifically for making all 
the code up to date with the functional code because at one point some of 
the tertiary code became too old to work with it properly and we had to keep 
making concessions in newer code.

----- Original Message ----- 
From: "William P. Davis" <will.davis at gmail.com>
To: <wp-hackers at lists.automattic.com>
Sent: Thursday, December 30, 2010 3:23 PM
Subject: Re: [wp-hackers] The problem with Contributions and This Thread

Having managed a project or two, I can say that it's often the little bugs 
that can throw a wrench in the whole operation. I can understand why the 
core team wouldn't want to give someone commit access only for the 'little' 
things — that's kind of like handing someone a gun to swat flies. A better 
solution might be to have trusted users without access review patches and 
leave their comments on tickets.

P.S. Trying to get things by whining rarely works past the age of 5.
Sent from my BlackBerry® wireless device

-----Original Message-----
From: Vid Luther <vid at zippykid.com>
Sender: wp-hackers-bounces at lists.automattic.com
Date: Thu, 30 Dec 2010 17:12:28
To: <wp-hackers at lists.automattic.com>
Reply-To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] The problem with Contributions and This Thread

So.. why not let Jacob become a core committer and be the person who
handles the low hanging fruit? If his claims about being the # 5
contributor are true,
he's definitely given his time, and if he's willing to put in the work..
why not let him?

I think what Doug is asking, is what proof do we have that having Jacob
handle this is going to make WordPress suck?
If so many of his patches have been accepted, it's a safe bet he's got
the hang of things..

Being an outsider to WordPress, but not open source projects.. I don't
see how getting bugs resolved is a bad thing...especially if the bug
made it through the triage process and was marked as low priority..

> ------------------------------------------------------------------------
>
> Pete Mall <mailto:pete at jointforcestech.com>
> December 30, 2010 4:58 PM
>
>
> Core team is always expanding... Just look at the all the new committers
> this year. I don't think the core team will (or should) ever give up on
> reviewing all changesets and rely on others for regression testing.
>
> Cheers!
> Pete
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> ------------------------------------------------------------------------
>
> Doug Stewart <mailto:zamoose at gmail.com>
> December 30, 2010 4:49 PM
>
>
> Then perhaps the core team ought to either 1) expand or 2) not worry
> so much about each changeset and allow others to regression test.
>
> --
> Doug Stewart
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
> ------------------------------------------------------------------------
>
> Peter Westwood <mailto:peter.westwood at ftwr.co.uk>
> December 30, 2010 4:43 PM
>
>
>
>
> The core team try and review every change that is made to the code to
> ensure that it is correct, doesn't introduce bugs etc.
>
> There time should be focussed on the most important bugs.
>
> Giving someone access to rush through all those easy trivial lower
> priority tickets with patches and commit them increases the workload
> for the core team and anyone else who reviews all the changesets.
>
> Therefore less time is available for important bugs.
>
> Cheers
> ------------------------------------------------------------------------
>
> Doug Stewart <mailto:zamoose at gmail.com>
> December 30, 2010 2:44 PM
>
>
> On Thu, Dec 30, 2010 at 5:52 AM, Peter Westwood
>
> With all due respect, where's your proof for this? I suppose that a
> good bit of this judgement would need to be made on a ticket-by-ticket
> basis, but still...
>
> If the tickets are legitimate yet somehow lower priority, how could
> there possibly be no benefit?
>
> ------------------------------------------------------------------------
>
> Peter Westwood <mailto:peter.westwood at ftwr.co.uk>
> December 30, 2010 4:52 AM
>
>
>
> Giving someone commit access to focus on lower priority tickets
> benefits no-one.
>
> It just causes code churn, lack of project focus, and makes it more
> likely that important bugs will get ignored.
>
> Cheers
_______________________________________________
wp-hackers mailing list
wp-hackers at lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-hackers
_______________________________________________
wp-hackers mailing list
wp-hackers at lists.automattic.com
http://lists.automattic.com/mailman/listinfo/wp-hackers