http://ofbiz.116.s1.nabble.com/best-practices-for-contributors-tp168876p168890.html
> Hi,
> Everything Si said is cool by me, except one bullet point:
>
> On 6/27/06, Si Chen <
[hidden email]> wrote:
> > Ok, so as a follow up to the write up of guidelines for committers, I
> > thought we should have some guildelines for contributors as well to
> > help them work with the project.
> >
> > 1. Send in a signed ICLA to Apache.
>
> Why? This is not necessary unless one becomes a committer. A
> contributor can contribute code without an iCLA: someone else with an
> iCLA must commit this code. By contributing in a public mailing list
> or attaching their patch to an ASF issue tracker, the contributor
> acknowledges his or her contribution may be included in a product
> licensed under the Apache License. And in a happy world, we get and
> process many such contributions.
>
> The reason we don't want to require an iCLA from new contributors is
> to not raise the bar for them: let the community grow with the lowest
> possible barriers to entry.