> -----Original Message----- > From: Andrew Dunstan [mailto:[EMAIL PROTECTED] > Sent: Monday, May 02, 2005 7:05 PM > To: [EMAIL PROTECTED] > Cc: Dave Held; [EMAIL PROTECTED]; > pgsql-hackers@postgresql.org > Subject: Re: [pgsql-advocacy] [HACKERS] Decision Process WAS: > Increased > company involvement > > [...] > I nat happy avout that last point - personally, I value most > highly the views of those who contribute code or similar and > least highly the views of those whose principal contribution > is opinions.
Maybe so, but if you were a new contributor, why would you write a bunch of code with no assurance that it would go anywhere? It seems wiser to invest your time familiarizing yourself with the ins and outs of the codebase and the coding style of patches by looking at other people's work. It also seems smarter to lurk and see what kinds of changes are likely to be considered. I doubt you would think highly of a newcomer that contributed code that was not in the style of the codebase and was for a feature not on the TODO list and that didn't get community buy-in first. But then, how do you get community buy-in if you don't contribute code, according to you? __ David B. Held Software Engineer/Array Services Group 200 14th Ave. East, Sartell, MN 56377 320.534.3637 320.253.7800 800.752.8129 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
