On Wed, Jul 28, 2010 at 4:09 PM, ERIC CLONINGER <
dcp874@xxxxxxxxxxxx> wrote:
> I just want to make sure there are no unintentional problems that we
> create for ourselves in the movement of the code. If it can be freely
> moved by the terms of the EPL, then I'm not going to argue with you.
> Your experience in these matters leading CDT is what I'm looking for,
> not a fight.
>
> -E
>
> On Wed, Jul 28, 2010 at 2:51 PM, Doug Schaefer <
cdtdoug@xxxxxxxxx> wrote:
>> Uh, wow. You guys have licensed the code as EPL. You must abide by
>> that license. You own the copyright on what you contribute, but
>> redistribution is governed by the license and allows anyone to take
>> the source and redistribute it as they see fit (as long as they redist
>> the changes, which is what the intent is here) and that would include
>> publishing it in another repository.
>>
>> BTW, this is about growing the Android Eclipse community. I'm
>> suggesting it's probably easier to build such a community over at
>> AOSP. It already has a huge community with the platform. It would
>> probably be easier to attract Android tooling developers there too,
>> especially given Xavier is already trying to do that.
>>
>> Now, of course, anything common and can be reused by other platform
>> tooling, like Symbian and RIM should stay here in Sequoyah. The native
>> stuff is really specific to Android though. Anything common there
>> would probably be best in CDT anyway. Speaking of which, if I would be
>> proposing the same thing if I had stuck with my original plan of doing
>> this in CDT. This isn't anything against Sequoyah, it's all about
>> doing what I think is best to build a community and spread Eclipse
>> technologies out to the masses.
>>
>> Doug.
>>
>> On Wed, Jul 28, 2010 at 2:41 PM, ERIC CLONINGER <
dcp874@xxxxxxxxxxxx> wrote:
>>> Keeping my Eclipse project manager hat on (and keeping my corporate
>>> hat on the hat stand)...
>>>
>>> I hate to see a piece of the project move out of the project so soon
>>> after we've started working with it. Obviously, I also hate to see an
>>> active committer stop being active on the project. But, I do see that
>>> there are concerns about dependencies between components and those
>>> dependencies may be confusing to our consumers, which is definitely
>>> not in anyone's best interests.
>>>
>>> There are some mechanics that will need to be resolved regarding where
>>> the code would be taken from before given to the AOSP. Motorola
>>> contributions to AOSP have to go through a different review process.
>>> You won't be able to take trunk from Sequoyah and commit to AOSP
>>> because there are Motorola contributions after your original
>>> contribution. Can you take your original contribution or perhaps code
>>> from your own repo prior to committing to Eclipse? If there is a
>>> desire to recontribute our code to AOSP through our review process,
>>> we'll certainly work on it as soon as we're able to.
>>>
>>> There is a question of ownership rights. I'm very unsure about this,
>>> because I don't know if the term "ownership" even applies to anything
>>> we do. I'm sure there are other precedents in the Eclipse ecosystem
>>> where code has left a project and begun life somewhere else. Since ADT
>>> is EPL, at least the licenses are presumably compatible, but I'm not
>>> sure about whether the Eclipse Foundation itself has some claim on the
>>> code once it's been contributed. Obviously, your experience as CDT
>>> lead is useful here.
>>>
>>> -E
>>>
>>> On Fri, Jul 23, 2010 at 2:26 PM, Doug Schaefer <
cdtdoug@xxxxxxxxx> wrote:
>>>> Very cool. Then we can focus the discussion at the summit on technical
>>>> items.
>>>>
>>>> Thanks,
>>>> Doug
>>>>
>>>> On Jul 23, 2010 2:43 PM, "Xavier Ducrohet" <
xav@xxxxxxxxxxx> wrote:
>>>>> Hi Doug,
>>>>>
>>>>> I'm glad you raised this point, as I was planning on talking to you
>>>>> and Eric about it at the CDT summit.
>>>>>
>>>>> Quick note on our current status:
>>>>> Yes we are very much open to contribution on the tools. Right now
>>>>> development for the SDK tools (including the ADT plug-ins) is done
>>>>> entirely in the open (since a bit before IO), and we intend to move
>>>>> development of the NDK (scripts and tools) to the open soon.
>>>>>
>>>>> I'll admit we haven't yet move discussions to the open, because since
>>>>> we're the only ones contributing so far, it's a lot easier (especially
>>>>> when you sit in the same office), but we're going to work on this. The
>>>>> recent android-contrib mailing list is the place to start talking
>>>>> about contributions, roadmap, etc...
>>>>>
>>>>> I also plan on having more documentation about tools specific
>>>>> contribution, roadmap, todo list, etc.. on
source.android.com (just
>>>>> need to find time to write it).
>>>>> Finally, we started using the external bug tracker a bit more, we did
>>>>> some cleaning up, but there's much more to do there.
>>>>>
>>>>> By the way, a quick side note. I don't think we've ever rejected tools
>>>>> contributions. It's just been hard for external contributors when they
>>>>> had no idea what was going on in our internal repository and I think
>>>>> that prevented the creation of a community.
>>>>>
>>>>> I would love if the NDK integration was done in ADT. It just makes
>>>>> more sense to me. Also, I'm concerned about whether or not it can be
>>>>> fully done in Sequoyah without dependencies on ADT. I think we can do
>>>>> a better integration directly in ADT (or as an extension to ADT)
>>>>>
>>>>> If you want to contribute to AOSP, we are ready to support you and
>>>>> help in any way we can.
>>>>>
>>>>> Xavier
>>>>>
>>>>> --
>>>>> Xavier Ducrohet
>>>>> Android SDK Tech Lead
>>>>> Google Inc.
>>>>>
>>>>> Please do not send me questions directly. Thanks!
>>>>> _______________________________________________
>>>>> sequoyah-android-dev mailing list
>>>>>
sequoyah-android-dev@xxxxxxxxxxx
>>>>>
https://dev.eclipse.org/mailman/listinfo/sequoyah-android-dev
>>>>
>>>> _______________________________________________
>>>> sequoyah-android-dev mailing list
>>>>
sequoyah-android-dev@xxxxxxxxxxx
>>>>
https://dev.eclipse.org/mailman/listinfo/sequoyah-android-dev
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Eric Cloninger (
ericc@xxxxxxxxxxxx)
>>> Senior Product Manager, MOTODEV Studio for Android
>>> Eclipse Sequoyah Project Lead
>>> _______________________________________________
>>> sequoyah-android-dev mailing list
>>>
sequoyah-android-dev@xxxxxxxxxxx
>>>
https://dev.eclipse.org/mailman/listinfo/sequoyah-android-dev
>>>
>> _______________________________________________
>> sequoyah-android-dev mailing list
>>
sequoyah-android-dev@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/sequoyah-android-dev
>>
>
>
>
> --
> Eric Cloninger (
ericc@xxxxxxxxxxxx)
> Senior Product Manager, MOTODEV Studio for Android
> Eclipse Sequoyah Project Lead
> _______________________________________________
> sequoyah-android-dev mailing list
>
sequoyah-android-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/sequoyah-android-dev
>
_______________________________________________
sequoyah-android-dev mailing list
sequoyah-android-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-android-dev