Re: Last gasp - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Last gasp
Date
Msg-id ef899d7632579d983a29b4512e5c984f@biglumber.com
Whole thread Raw
In response to Re: Last gasp  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> I want to caution against adjusting things to improve funding
> possibilities.  There is nothing wrong with increasing funding
> possibilities, per say, but such changes often distort behavior in
> unforeseen ways that adversely affect our community process.

I don't see this as much of a problem. If somewhat arbitrary labels 
and powers allow the project to succeed, we should think long and 
hard before rejecting the idea. It's not like we are going to make 
anyone who asks a committer, like MediaWiki does. Indeed, we have 
been super cautious about handing out both commit bits, and labels 
(e.g. "Major Developer").

One wrinkle is the subsystems: there are some people who only work on 
certain parts, yet have a commit bit (with the understanding that 
they won't start editing core or other parts). From an outside 
perspective however, a "Postgres committer [of certain subsystems]" 
is a "Postgres committer".

One thing I think would help potential and current developers, and 
act as a further code review and safety valve, is to have a mailing 
list that actually shows the committed diffs. Links to a webpage 
showing the diff is just not the same.

pgsql-commit-diffs@postgresql.org, anyone?

- -- 
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201204121121
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8

-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk+G8/sACgkQvJuQZxSWSsh7HACgn7Wf/AQyUJwtvxgjYSHSIHkJ
hq4AnjMgPlDakupg4mo204+N1p4C0mMZ
=z+cR
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Joshua Berkus
Date:
Subject: Re: Last gasp
Next
From: Thom Brown
Date:
Subject: Re: CREATE FOREGIN TABLE LACUNA