[Python-Dev] Encouraging developers (original) (raw)

Phil Thompson phil at riverbankcomputing.co.uk
Tue Mar 6 09🔞29 CET 2007

On Tuesday 06 March 2007 5:42 am, Martin v. Löwis wrote:

Phil Thompson schrieb: > 1. Don't suggest to people that, in order to get their patch reviewed, > they should review other patches. The level of knowledge required to put > together a patch is much less than that required to know if a patch is > the right one.

People don't have to review patches. They just can do that if they want expedite review of their code. > 2. Publically identify the core developers and their areas of expertise > and responsibility (ie. which parts of the source tree they "own"). I doubt this will help. Much of the code isn't owned by anybody specifically. Those parts that are owned typically find their patches reviewed and committed quickly (e.g. the tar file module, maintained by Lars Gustäbel).

Doesn't your last sentence completely contradict your first sentence?

> 4. Acceptance by core developers that only half the "job" is developing > the core - the other half is mentoring potential future core developers.

So what do you do with core developers that don't do their job? Fire them?

Of course not, but this is a cultural issue not a technical one. The first step in changing a culture is to change the expectations.

Phil

More information about the Python-Dev mailing list