Skip site navigation (1) Skip section navigation (2)

Re: Contributor List policy

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-advocacy(at)postgresql(dot)org
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, bruce(at)momjian(dot)us, josh(at)agliodbs(dot)com
Subject: Re: Contributor List policy
Date: 2008-03-10 20:34:59
Message-ID: 20080310133459.43f37616@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-advocacy
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 10 Mar 2008 11:36:43 -0700
"Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
 
> In thinking about this I might have an additional solution:
> 
> A hacker is someone who:
> 
> In the last 24 months has contributed -n- number of patches or a patch
> of significant value to the project.

I just had an epiphany here. Solving the -hackers problem is pretty
easy. It can be handled as it is now, via oversight from core and the
initial list is what is listed under major contributors (as they are
all developers anyway).

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)

iD8DBQFH1ZtzATb/zqfZUUQRAnplAJ9appn4QnCI3OTkSZP2uFtM6scbKwCghF5g
RTenxvmiac6QY/9Rk5bBYrg=
=fW1A
-----END PGP SIGNATURE-----

In response to

pgsql-advocacy by date

Next:From: Josh BerkusDate: 2008-03-10 20:52:04
Subject: Re: Contributor List policy
Previous:From: Joshua D. DrakeDate: 2008-03-10 18:36:43
Subject: Re: Contributor List policy

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group