www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Adopting non-ASF AL projects
Date Mon, 30 Nov 2015 17:58:15 GMT
On 30 November 2015 at 17:49, Alex Harui <aharui@adobe.com> wrote:
> On 11/30/15, 9:29 AM, "Jim Jagielski" <jim@jaguNET.com> wrote:
>>> 2) if the authors of that code base have no intention of working on it
>>> the future, do we require an ICLA from them or can they give consent in
>>> email, essentially like other folks do for patches?
>>Do you mean for the existing code or for future patches? The
>>question is not quite clear.
> Existing code.
>>My suggested course of action is to send an email to the
>>current project's development and user lists (maybe create
>>some Issue or Bugz entry, etc...) with the notice that a PMC
>>at the ASF wishes to fork the project and maintain and develop
>>it and to ask for comments. If there is dissent in that community
>>about this course of action, I would encourage you asking both
>>Legal and the PMC "what to do now".
> I forgot to mention in my re-cap that there really isn't a community
> associated with these code bases anymore.  So to me, asking folks who've
> made contributions in the past is the same as asking the community.  I
> will ask what to do if there is dissent, but my main question here is, if
> I send an email to 12 past contributors and only 4 respond after a week of
> waiting (which covers 90% of the code), can we take 100% of the code as
> long as we feel that if we do get any objections later we can kick out
> those changes with out ruining that code base?

It seems to me that waiting just a week is insufficient here.
Some people go on holidays and don't have e-mail access.
[Indeed the longer the holiday perhaps the less likely they will have
e-mail access.]

I think it would be polite to wait quite a bit longer - e.g. 4+ weeks
- before assuming that you won't get a response.

>>Please note that although the ALv2 gives us access to the code,
>>it does not provide us the ability to use their mark, unless the
>>current project maintainers explicitly assign us their mark.
> I will ask the founding contributors about the marks.
> Over on general@ I was drafting the email I would send to the past
> contributors.  Perhaps we can finish drafting it here. The current draft
> reads:
> ---- Draft 2 -----
> [Friendly intro]
> A major contributor of XXX has indicated a desire to have the Apache
> Software Foundation's Apache Flex project be the new home of future
> development of the XXX code.  Normally, this is called a "donation" and
> requires a bunch of legal paperwork, but because this code base is already
> licensed under Apache License 2.0, your contributions may be donated to
> the ASF by replying to this email to affirm that:
> 1) You agree that the code you wrote is licensed under Apache License 2.0
> 2) You understand that under the Apache License 2.0, you retain the
> copyright of the code you wrote.  You are only granting  a license to not
> only the Apache Software Foundation (the ASF), but to anyone else as well.
> 3) You understand that if we cannot get enough affirmative emails from
> enough contributors to this code base, the "donation" may be abandoned.
> 4) You understand that if this "donation" is completed, future downloads
> should come from, and changes applied to, the code base in an
> ASF-controlled code management and distribution system, and discussion
> about the code base should happen on Apache Flex mailing lists.
> 5) You understand that if you are not already an Apache Flex Committer and
> wish to have continued involvement in changes to this code base, we can
> discuss separately the steps to become a Committer.  We would love to have
> you come be part of Apache Flex if you are interested in making further
> contributions.
> Thanks,
> Alex Harui, for the
> Apache Flex PMC.
> ----- End Draft 2 -----

To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org

View raw message