incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein" <>
Subject Re: How to bring code to Apache?
Date Sat, 18 Nov 2006 21:35:21 GMT
For the IP clearance stuff... yes.

But code developed outside of the Apache community, then brought in...
that can be a problem. Especially when that is the "standard operating
procedure". I can think of a couple communities where a lot of code is
migrated from external locations into Apache. The net effect is code
is developed *outside* of the Apache consensus model. That isn't good.


On 11/4/06, Jeremy Boynes <> wrote:
> The "important part" here is not to validate the process but the
> provenance of the code being contributed. It does not matter whether
> the code was developed in an open or closed manner, by one individual
> or by many, what we have a responsibility to establish is that the
> code can legally be contributed to the ASF.
> Unlike an employer, the ASF has no initial rights to any code; those
> are granted to it through the ICLA when the code is contributed. We
> operate on an ongoing assumption that the committer abides by the
> ICLA and does actually have the rights to contribute that code.
> However, for any body of code we (the ASF) should have the ability to
> ask the committer to reconfirm this, especially if there is increased
> potential that the IP for the code is not owned solely by them (as
> would be the case if it was developed by multiple people or for an
> employer outside a CCLA). AIUI, that is the role of the IP Clearance
> process: to obtain that confirmation.
> The openness of the development process used is only relevant here to
> the extent that it exposes the provenance of the code - an open
> process allows us to backtrack and see who created the code and owns
> the IP. It's much more of an issue for the receiving PMC in gauging
> the health of the community.
> I'd suggest changing that part to something like "the important part
> is whether anyone else may own any of the code, for example if it was
> developed with other people or as part of your job"
> --
> Jeremy

Greg Stein,

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message