incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: Proposal for contributing code from GraniteDS
Date Tue, 13 Nov 2012 18:51:29 GMT

On 11/13/12 9:49 AM, "Franck Wolff" <> wrote:

> Om,
> Yes we are.
> I think the best would be to commit our sources in the
> trunk/frameworks/projects/experimental/src/ directory, changing our package
> names to:
> org.apache.flex.math (BigDecimal implementation)
> org.apache.flex.reflect (Reflection API)
> org.apache.flex.validation (Bean Validation implementation)
> We would also need to change our headers, reflecting the Apache License (as
> well as filling some legal forms I guess).
> Then, the community could review the new source code and test a build
> including the experimental new code. I'm not very familiar with the Apache
> vote process but this submission could be accepted (or rejected) through a
> vote and then included into the general framework release.
> Does it sound reasonable? Would it be possible to get a full SVN access
> during this process?
Is this a lot of code?  If so, there is a software grant process you have to
execute before donating the code.  If not, you can probably just attach the
source to a JIRA issue for review.  You have to be the copyright owner and
have permission from any other copyright owners in your code base, plus you
can't have dependencies on code that isn't licensed in an Apache-compatible

In general, we can't give out SVN access until all of this process is dealt
with and there is some initial review of the code.  But if you are the
shepherd for a significant donation, you will likely be given access

It is done this way as an extra check to try to make sure some code that
shouldn't be donated doesn't get into SVN because once it is there, you
can't really get rid of it.

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message