db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: [jira] Commented: (DERBY-681) Eliminate the parser's rewriting of the abstract syntax tree for queries with GROUP BY and/or HAVING clauses
Date Tue, 13 Feb 2007 17:13:29 GMT
A B (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/DERBY-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472754
> A B commented on DERBY-681:
> ---------------------------
> Manish Khettry (JIRA) wrote:
>> Thanks for reviewing the patch. It will take me sometime to make
>> the patch current and look at your comments. It has, after all, 
>> been a while since I submitted the patch.
> Thank you for willingness to continue working with the patch.
>> I am curious-- is it typical for a patch to gather dust for a 
>> few months before someone finds the time to look at it?
> I don't think it's "typical" for this to happen, no.  But given the "fry your own fish"
philosophy of open source development, this kind of thing does (unfortunately) happen on occasion.
>That said, though, it's up to people in the community (users, developers, anyone--doesn't
just have to be committers)
 >to review patches and/or comment on the various issues according to 
their own interest/expertise.

And if anyone is concerned about such delays they can help by reviewing 
patches that they didn't submit, possibly allowing a committer just to 
perform the actual commit. Then hopefully someone else will spend the 
effort to review their patch.

Community is a key word here, it takes people being active to make a 
community. There is not a fixed set of folks working on Derby who are 
responsible for the project, the community is, and that's only exists 
when people participate and interact. People frying their own fish is 
perfectly acceptable, but if that's all everyone does then we don't have 
a community.


View raw message