Hi, Chris, Oliver,
There's a special flavor of CQ for this purpose: the "ATO" (add-to-Orbit) which is an even more stream-lined Contribution Questionnaire than the PB (piggy-back). It omits the step of justification of the contribution by describing how/why the requesting project requires it. In the case of the Orbit project, the answer is always the same :-)
Cheers,
Christian
On 2-Feb-09, at 8:40 AM, Chris Aniszczyk wrote: Yes, they should piggyback on the original ones. Any library that goes into Orbit should piggyback on a CQ that has that library going in a project. At least that's how things have been working for awhile.
Thanks!
On Mon, Feb 2, 2009 at 7:34 AM, Oliver Wolf <oliver.wolf@xxxxxxxxx> wrote: You will have to file CQs for each of those libraries when they get put into Orbit. Should the Orbit CQs piggyback on my original ones or should I file new CQs for Orbit and have my original CQs changed to piggyback on the Orbit ones? Cheers, Oliver _______________________________________________ orbit-dev mailing list orbit-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/orbit-dev
-- Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465 _______________________________________________ orbit-dev mailing list orbit-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/orbit-dev
-- Christian W. Damus Senior Software Developer, Zeligsoft Inc. Component Lead, Eclipse MDT OCL and EMF-QTV
|