| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Catalin Iacob <iacobcatalin(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: No Issue Tracker - Say it Ain't So! |
| Date: | 2016-01-06 23:57:53 |
| Message-ID: | 568DAA01.5060002@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/6/16 5:51 PM, Tom Lane wrote:
> Having said that, it occurs to me that one way to contribute without
> actually writing C code would be to try to drive those unfinished
> discussions to consensus, and come up with specs for features that people
> agree are well-thought-out. Conversely, establishing a consensus that a
> proposal is a bad idea and it should go away from the list would be a
> useful activity.
+1.
Somewhat related to that, I don't believe there's any reason why commit
fest managers need to be committers; it seems like the job is really
just about reading through email activity to see where things are at.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2016-01-07 00:02:24 | Re: No Issue Tracker - Say it Ain't So! |
| Previous Message | Tom Lane | 2016-01-06 23:51:53 | Re: No Issue Tracker - Say it Ain't So! |