Kevin Grittner wrote: > > We should be giving authors as much leeway as possible, or they > > may not come back. > > One phenomenon I've noticed is that sometimes a patch is submitted > because an end user has solved their own problem for themselves, but > wishes to share the solution with the community. They're not always > motivated to go to the lengths required to polish it up to the > standard required for inclusion in core. In such cases, unless > someone with the time to do so finds it interesting enough to pick > up, it is just going to drop. I hope such authors feel comfortable > submitting their next effort, as it might be something which > interests a larger audience than the previous effort. We should do > what we can to ensure that they understand the dynamics of that.
This brings up the larger issue of whether incomplete/unapplied patches are recorded on the TODO list or just ignored. We never really came up with a plan for that. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
