On Sat, 5 Feb 2011 00:09:41 -0500
Christopher Petrilli <petri...@amber.org> wrote:
> For example, the following projects REQUIRE contributor agreements, in
> writing, signed and either scanned or on paper, prior to accepting any
> patches or commits:
>
> - Free Software Foundation
> - Apache, and everything under it
> - Python
> - Perl
> - Django
> - MySQL
> - Node.js
> - Fedora Linux
> - Neo4j
> - Sun (now Oracle)
I'm sorry, I'm going to call foul on this. I've contributed to Python
without ever signing a CA. And the current developers guide page
doesn't have anything on it about needing to sign a CA.
Seriously, the "snail-mail" requirement is the only one that's really
objectionable. Most places are quite happy with a scanned image of the
signed document (i.e. - the Chickasaw nation for my citizenship
papers).
Without that requirement, I would already have submitted one. With it?
I can submit most fixes/enhancements as patches (my most likely
contribution) via the ticketing system without having to jump through
that hoop. In the unlikely event I write something significant that
someone wants in core or contrib, I'll revisit the issue.
<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
