Re: Contributor List policy

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

On Mon, 10 Mar 2008 14:30:19 -0700
"Joshua D. Drake" <jd@commandprompt.com> wrote:


> I don't expect this to be resolved today or tomorrow but doing things
> the wrong way for the sake of expediency isn't helpful either.

JoshB asked me to post this:

(02:41:47 PM) linuxpoet: YOu basically want to rush through a bunch of
changes, that are wrong in the first place, for expediency sake

(02:41:49 PM) linuxpoet: there is no reason for it 

(02:42:12 PM) agliodbs: so, you're in favor of delaying an update to
the contributor listings for weeks or months while we work out a new
policy? 

(02:42:27 PM) agliodbs: just to be clear

(02:42:49 PM) linuxpoet: I would rather do it correctly, than do what
you suggest. Yes. 

(02:43:04 PM) linuxpoet: That means communication, transperancy, and a
plan 

(02:43:12 PM) linuxpoet: which includes documentation and understanding
of the purpose of the list 

(02:43:21 PM) agliodbs: and in the meantime, nothing gets updated,
correct? 

(02:43:31 PM) linuxpoet: It isn't like that is a change :P

(02:43:50 PM) agliodbs: mind posting that viewpoint on a list?

(02:43:56 PM) linuxpoet: I thought I had but sure 

(02:44:00 PM) agliodbs: I think it's liable to be controversial

Sincerely,

Joshua D. Drake


> 
> 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)

iD8DBQFH1azpATb/zqfZUUQRAkpgAJ9zJbKGlqvB4s9uzOTF7HPxvQhGSwCgli6E
7eWWR+DLTNJgotblTbOb84Q=
=jLgm
-----END PGP SIGNATURE-----