RE: [orbit-dev] On the need for CQs

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

Hey Martin, 

I did not get the "after the fact"
nature of your question.  I would not rush to do these retro CQs right
now.  There is an open question with the Foundation legal team to
better understand what we should do here.

More later

Jeff

"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

01/07/2008 06:56 AM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	"Orbit Developer discussion" <orbit-dev@xxxxxxxxxxx>
cc
Subject	RE: [orbit-dev] On the need for CQs

Hi Jeff,
 
thanks for your explanations.
You say:
   "We
can then enter a "reuse" CQ for Orbit.  These CQs
can/should..."
since that does not explicitly
answer my question,
let me ask once again:
 
Do you want us to create
an Orbit-related "reuse" CQ 
for every existing lib in Orbit
after the fact, even if a 
Using-Project-related CQ already
exists?
 
Do you want us to file
an Orbit-related bugzilla entry
for existing libs in Orbit after
the fact?
 
Thanks,
--
Martin Oberhuber, Senior
Member of Technical Staff, Wind
River
Target Management Project Lead,
DSDP PMC Member
http://www.eclipse.org/dsdp/tm

---

From: orbit-dev-bounces@xxxxxxxxxxx
[mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer
Sent: Friday, January 04, 2008 3:57 PM
To: Orbit Developer discussion
Subject: RE: [orbit-dev] On the need for CQs


The rule according to the IP policy is: 
        Every project that wants to reship code from
a third party must have and approved CQ. 

What this means to us is that some project that wants to use a lib must
enter an initiating CQ.  ANY and ALL projects that want to use that
same lib MUST also enter a CQ.  The subsequent CQs are very light/fastbut
are needed none the less.  Since the Orbit mandate is to manage/host
bundlings of libs approved for use in other projects, I suggest that the
initiating CQ be entered on behalf of the project first using the lib.
 We can then enter a "reuse" CQ for Orbit.  These CQs
can/should be entered at the same time and the bundling can/should actually
happen in Orbit directly.  The exception is where someone is incubating
and trying to use the parallel ip provisions.  Orbit is not incubating
and therefor cannot host libs which are in parallel IP (i.e., have not
completed a full IP review). 

I hope that is clearer.  Let me know if more information is needed.

Jeff _______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev