On 8/17/12 4:30 AM, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote:
> Hi Flex mentors and PPMC,
> (especially Alex and Carol, I think you've been involved in all donations)
>
> Several code packages have been donated to Flex, and I trust whoever's
> been committing those has checked that the ASF did receive the
> corresponding software grants, but I don't think we have sufficiently
> documented this. The Incubator PMC might (rightly) ask us to provide
> tracking info for those donations to make sure everything's clean and
> traceable.
>
> The standard process is explained at [1] - I don't think we
> necessarily need to use the forms provided there, IMO what's important
> is to have a trace of which code donations have happened, including
> md5 of other digests of the code archives that were imported and
> pointers to the corresponding software grants.
>
> How do we best handle this without complicating things?
> The simplest might be to create a JIRA issue about documenting those
> donations, and add the required info there.
>
> We can then just add a link to that jira issue at
> http://incubator.apache.org/projects/flex.html to make that info
> available.
>
> Thoughts?
>
> -Bertrand
>
> [1] http://incubator.apache.org/ip-clearance/index.html
Wish I'd read that before...
We have most of the information, but I'm not sure how to organize it.
Adobe has donated the following:
1) Initial Frameworks Donation via SVN Import. MD5 was computed for the
import file. I have email acknowledgement from Secretary for Software Grant
2) Modules/Compiler Donation via SVN Import. MD5 was computed for the
import file. I don't have email from Secretary (probably went directly to
Adobe VP) but I know Apache received it because Infra wouldn't have done the
import without it.
3) Basic Mustella Test Engine. This was committed directly to SVN. No
archive of these files was created and no MD5 computed. I have email from
Secretary for the grant.
4) Automation/Samples/FABridge. This was committed directly to SVN. No
archive was created, no MD5 was computed and some files listed in the grant
were updates to files already donated. I have email from Secretary for the
grant.
5) The Mustella Test Media. This was committed directly to SVN. No archive
was created, no MD5 was computed and some files listed were updates. I have
email from Secretary, but the document title does not clearly denote the
content of the grant.
6) The Flex 5 Components. This was committed directly to SVN. No archive
was created, no MD5 was computed. I have email from Secretary, but the
document title does not clearly denote the content of the grant.
7) The Text Layout Framework. This was also committed directly to SVN. I
have an archive as that was how it was transferred within Adobe to me. I
have email from Secretary, but the document title is again non-specific.
If I understand the goal of the document, it is to guarantee correct license
and copyright handling before code goes into an Apache repository. I am a
bit surprised by that as I thought one of the jobs in incubation is to fix
up this stuff. In fact, donations 1, 2 and 4 were cleared by Adobe for
donation but required more fiddling in Apache to pass RAT so we could
release. Certainly you don't want folks to commit stuff that is not Apache
compatible, but Adobe made sure that no third-party content was contributed
without a compatible license (although Adobe legal tools wouldn't catch
files not having any copyright/license or having an Adobe license, although
we did visually scan for that).
Could we argue that releasing got us to a correct place legally and now we
only need to prove out the correctness for donations 3, 5, 6, and 7?
Would running RAT be sufficient?
How do we resolve the MD5 issue for things we checked in directly,
especially if the net commit of some of those files were updates to
previously donated files?
How do we provide links to the grants?
Thanks,
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
