On Wed, 20 Oct 2010 09:59:26 -0600 "Eric Schulte" <schulte.e...@gmail.com> wrote:
> Mike Meyer <mwm-keyword-googlegroups.620...@mired.org> writes: > > > It was also more work than submitting patches looks to be for apache, > > django, gnu > > FWIW in gnu projects if your patch is >10 lines long then they do > require you to go through a fairly lengthy attribution process. > > http://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html Two things. First, the limit is "around 15 lines of code", excluding repeated changes, and it applies over all patches, not just one: http://www.gnu.org/prep/maintain/html_node/Legally-Significant.html More importantly, this doesn't happen until *after* the patch has been submitted and a contributor decides it should be included. Putting roadblocks in front of people who want to submit patches or bugs - and not being able to update the bug database qualifies, since you can't report on the results of suggested fixes or at the very least add another case to the existing ticket without a developer having to notice the duplicate and flag it - is a bad idea. Again, maybe it's possible to submit bugs to assembla without the CA; but finding the assembla tickets list itself requires wading past the verbiage about the CA. If bug reports (with or without patches) doesn't require a CA, then it should be a lot easier to find. <mike -- Mike Meyer <m...@mired.org> http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
