Re: Commitfest problems - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Commitfest problems
Date
Msg-id 57659fca2d35146fe7bfea5d9fe4a23a@biglumber.com
Whole thread Raw
In response to Re: Commitfest problems  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> #2 is solved by my previous comments about giving the CFM/C the 
> authority. -Core could do that, they are in charge of release.

I don't think authority is the solution. Or certainly not one that 
would work with an open source project like ours. What *would* 
work is to identify and fix the friction points that prevent 
people from joining, make the work harder than it needs to be, 
and makes people stop reviewing? I could quickly identify a handful 
of things, primarily among them the awful link-to-the-archives 
to gather up all the patches process. We have git, let's use it 
as it was intended.

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

iEYEAREDAAYFAlSNqK8ACgkQvJuQZxSWSsiewwCffAxv8xSZEyLWFz/b2+PxXOXS
xB4An2ubr7ovELtFMKZOZCsFHQAyVca4
=S6ZQ
-----END PGP SIGNATURE-----





pgsql-hackers by date:

Previous
From: Mark Cave-Ayland
Date:
Subject: Re: Commitfest problems
Next
From: Ali Akbar
Date:
Subject: Re: [REVIEW] Re: Fix xpath() to return namespace definitions