Yup. The Galileo elements must share these 3rd party libs through
Orbit.
It would be fine if projects were proactive about putting things in
Orbit. As you say, it seems inevitable that they will have to be there.
Another option is to work it such that projects were somehow "forced"
to start out with their libs in Orbit. It ought not be more work for
them and it avoids this whole issue. Not sure that I would seriously
propose that at this point.
Jeff
Oliver Wolf wrote:
But does it mean that because of our CQs
we’re essentially forcing everyone else to consume things from Orbit
that they’ve already received an approval for?
Oliver
Am 03.02.09 13:27 schrieb "Jeff McAffer" unter
<jeff@xxxxxxxxxxxxxxxxx>:
I would have suggested #2 but either ways
seems fine. An interesting topic is whether, in this example, the
SMILA team has to file an additional CQ to nor use the stuff that gets
put in Orbit... Will have to talk about this with the IP team.
Jeff
Oliver Wolf wrote:
Question regarding third party libraries for
Galileo Hi *@PMC,
I’ve filed a bunch of CQs for third party libraries that rt.swordfish
will require directly or indirectly for the Galileo release.
Some of them are piggybacking on existing CQs filed by other projects
that have been approved previously. Consequently, PMC approval for my
CQs was not granted because of the Galileo requirement that all
libraries shared between projects must be consumed from Orbit (which
makes perfect sense). I’ve already asked to be nominated as a committer
on Orbit and the election is underway. So far, so good.
What’s puzzling me, though, is how to correctly proceed from here.
Let’s take CQ3015 as a random example. It’s a CQ for xmlschema-1.4.2
which piggybacks on CQ2756 originally filed by rt.smila. As far as I
understand, there are two potential routes to go down:
- Get PMC approval for CQ3015 and have it
approved as reuse by the IP team, then file an ATO (add to orbit CQ)
that piggybacks on CQ3015, get approval and commit to Orbit.
- File an ATO that piggybacks on CQ2756, get
approval, commit to Orbit. Change CQ3015 to piggyback on the ATO and
get approval to consume from Orbit.
-
What is the correct/common/best way to proceed? And what happens in the
(hopefully theoretical) case that rt.smila doesn’t agree to consume
from Orbit?
Cheers,
Oliver
--
Wir bieten Trainings zu SOA:
Jetzt online auf unserer Homepage informieren und schnell buchen!
Oliver Wolf
Tel.: +49 228-182 19059
Fax: +49 228-182 19093
Mobil: +49 160 98931313
oliver.wolf@xxxxxxxxxx
SOPERA GmbH - Open Source SOA
Subscription Services, Support & Maintenance, Training,
Technical SOA Consulting & Customized Development
www.sopera.com
SOPERA GmbH · Geschäftsführer: Dr. Ricco Deutscher, Harald Weimer,
Peter Spiegel
Standort Bonn: Sträßchensweg 10 · 53113 Bonn · Handelsregister: Bonn
HRB 15336
Standort München: Hohenlindnerstraße 11b · 85622 München
Vertraulichkeitshinweis: Diese Nachricht und jeder übermittelte Anhang
beinhaltet vertrauliche Informationen und ist nur für die Personen oder
das Unternehmen bestimmt, an welche sie tatsächlich gerichtet ist.
Sollten Sie nicht der Bestimmungsempfänger sein, weisen wir Sie darauf
hin, dass die Verbreitung, das (auch teilweise) Kopieren sowie der
Gebrauch der empfangenen E-Mail und der darin enthaltenen Informationen
gesetzlich verboten ist und gegebenenfalls Schadensersatzpflichten
auslösen kann. Sollten Sie diese Nachricht aufgrund eines
Übermittlungsfehlers erhalten haben, bitten wir Sie, den Sender
unverzüglich hiervon in Kenntnis zu setzen.
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
|