[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [rt-pmc] Google API Approval
|
I am also a firm believer that the work-with must be for an optional piece of functionality or an optional implementation of core functionality that does not have a works-with dependency.
If RAP requires visualization to do its most basic/common functionality and this Google integration was the only option to provide this functionality then it would not be a works-with.
Since this is not the case, to the best of my knowledge, I agree with proceeding with this works-with dependency approach.
Doug
-----Original Message-----
From: Jeff McAffer [mailto:jeff@xxxxxxxxxxxxxxxxx]
Sent: February 2, 2010 4:53 PM
To: Runtime Project PMC mailing list
Subject: Re: [rt-pmc] Google API Approval
Other PMCers should comment (if they are so inclined) on the "work with" characterization... It is not simply my decision. Just my opinion.
Jeff
On 2010-02-02, at 3:08 PM, Austin Riddle wrote:
> Jeff,
>
> Thanks for the insight and explanation.
> I have just opened CQ3765 regarding the works-with dependency.
>
> Thanks.
>
> Jeff McAffer wrote:
>> You need a CQ for everything. In this case the PMC is involved at two points. first we help determine if it is a works with or pre-req dependency. Then someone from the PMC approves the CQ requesting the use of the lib as a works with or pre-req dependency as determined in the first step.
>>
>> The first step should be somewhat of a "group" decision. It doesn't have to be an official vote etc but simply taking the first +1 seems incomplete. Not to make it complicated but as we have seen, the dependency determination is open to different opinions. The second approval requires only one PMC member to +1 the CQ.
>>
>> Austin, you will need to state what kind of dependency you are requesting and why it is that kind of dependency.
>>
>> In the interest of expediting this particular approval, from a RAP point of view I think this is a works with dependency. RAP works just fine without this. A particular part of RAP needs the lib but people can use RAP very effectively without that part.
>>
>> Note also that if there is part of this code (e.g., the calling side) that you are planning to actually ship from Eclipse.org then I think you will need second CQ for that part as it would would not be a dependency so much as a contribution.
>>
>> Jeff
>>
>>
>>
>> On 2010-02-02, at 1:40 PM, Jesse McConnell wrote:
>>
>>
>>> AFAIK the part of the CQ process workflow where it needs a +1 from PMC
>>> member is the only specific blocking point for something like this
>>>
>>> cheers,
>>> jesse
>>>
>>> --
>>> jesse mcconnell
>>> jesse.mcconnell@xxxxxxxxx
>>>
>>>
>>>
>>> On Tue, Feb 2, 2010 at 13:35, Austin Riddle <austin.riddle@xxxxxxxx> wrote:
>>>
>>>> Hello,
>>>>
>>>> Not to be a bother, but could anyone tell me what the next step for
>>>> approving the Google API dependency is?
>>>>
>>>> I am expecting the CQ to be approved shortly for the contribution. Does
>>>> there need to be a separate CQ opened for the Google dependency?
>>>> Or is it just a matter of obtaining a +1 from the mailing list?
>>>>
>>>> Thanks.
>>>>
>>>> --
>>>> Austin Riddle
>>>> Software Engineer
>>>> Computing and Information Technology Division
>>>> Texas Center for Applied Technology
>>>> Texas Engineering Experiment Station
>>>>
>>>> _______________________________________________
>>>> rt-pmc mailing list
>>>> rt-pmc@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>>>>
>>>>
>>> _______________________________________________
>>> rt-pmc mailing list
>>> rt-pmc@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>>>
>>
>> _______________________________________________
>> rt-pmc mailing list
>> rt-pmc@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>>
>
>
> --
> Austin Riddle
> Software Engineer
> Computing and Information Technology Division
> Texas Center for Applied Technology
> Texas Engineering Experiment Station
> Ph. 979-458-7680
>
> _______________________________________________
> rt-pmc mailing list
> rt-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/rt-pmc
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
