[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orbit-dev] Addind/Updating Libaries in Orbit
|
Hi, David,
Sorry to have given out bad advice. I had thought that we started out
with this process, and that following discussions with the
Foundation's legal team, it was decided to take the other tack. I
agree that it seems desirable to track the origin of Eclipse's initial
requirement for 3rd-party libs this way, and searching through the
mail archive, I don't find anything that supports my wonky memory.
Perhaps we should add a step 0 to the "Adding Bundles to Orbit" page
in the Wiki, and a note about this in the FAQ? If we're all agreed, I
can draft something.
Thanks,
Christian
On 10-Nov-08, at 12:49 PM, David M Williams wrote:
You should submit first the CQs for contribution to Orbit, then
(once
those are approved) the piggy-back (PB) CQs for re-use of these
bundles in your project.
Turns our that I can't submit Orbit CQs. Thus, I started submitting
CQs
for my project first.
Don't mean to start a controversy, but actually, I believe that's the
better procedure anyway. I'm not sure anyone polices it, so the other
approach might have worked, but we are supposed to only put things in
Orbit that are used by other Eclipse Projects ... hence, its better
that
the original requesting Project gets the original CQ approved first,
then
all others (including Orbit) can piggy back off that one. This way,
there's at least one PMC somewhere that reviews it and with their
approval state "... yes, this is worth expending resource and money on
for our project ...".
_______________________________________________
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
E-mail: cdamus@xxxxxxxxxxxxx
