Re: Contributor listing policy

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 7 Mar 2008 17:57:25 -0800
"Joshua D. Drake" <jd@commandprompt.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Fri, 7 Mar 2008 15:14:08 -0800
> Josh Berkus <josh@agliodbs.com> wrote:
> 
> > Folks,
> > 
> > *speaking* of being open about policies, I'm requesting comments on
> > the Core Team's draft contributor listing policy:
> > http://developer.postgresql.org/index.php/ContributorListings
> > 
> > Here's what's changing from current practice:
> > 1) period for dropping people who have not been around is set to 2
> > years. No explicit period was set before.
> > 
> > 2) non-code contributors now get listed in the "Contributors"
> > section, but are not eligible for the "Major Developers" section.

Of note on this is:

Editing the contributor listings will be carried out by the Core Team. 

This is outside the scope of core purpose as they portray themselves.
Which is as a steering committee/release manager.

Although members of core could certainly be part of the process, I
think that like everything else in the infrastructure contributor
management should be lead by a team of individuals, a committee if you
will.

Sincerely,

Joshua D. Drake


- -- 
The PostgreSQL Company since 1997: http://www.commandprompt.com/ 
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate     PostgreSQL political pundit | Mocker of
Dolphins

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH0gehATb/zqfZUUQRAkuhAJoD8hFH11fPqkWE8ytKbzr1cuT77gCfZlm7
lx0TjDJB6ZYzAlt1+qx0uKQ=
=L3aN
-----END PGP SIGNATURE-----