Hi,
FYI:
I asked Barb Cochrane the same questions and
she answered me as follows:
Hi Sebastian,
Before creating such dependencies on optional third party software,
your PMC will have to consult the Guidelines
for Third Party Dependencies for each piece of third party software that
SMILA is proposing to be downloaded from another site.
Then, for each piece of third party software that PMC approves the
use of under those guidelines, SMILA will have to enter a CQ and clearly
identify whether the third party software in question is a “workswith” or an
“exempt pre-req”. If PMC votes +1, then
a)
those that PMC has identified as
“workswith” are approved as optional components under the guidelines; and
b)
those that PMC has identified as
“exempt pre-req” require EMO approval as well, and only after EMO are these
components approved as optional components under the guidelines.
I hope this helps!
Cheers,
Barb
From: smila-dev-bounces@xxxxxxxxxxx
[mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of August Georg Schmidt
Sent: Wednesday, October 08, 2008 3:14 PM
To: Smila project developer mailing list
Subject: [smila-dev] SMILA check-in at Eclipse
Hallo Jochen, Hi Jeff,
we would like to prepare our check-in at
Eclipse. Since not all components are yet accepted at IP process we would like
to find out whether its possible for us to create a partitial version at
eclipse that is not compilable.
We currently see two ways for providing
such a version.
1.
Create a Tutorial for a build
including an external download site for manual components for download
2.
Create a ANT script that will
do a complete compile including such an download.
Would such options be possible? Are there
specific restrictions that we have to keep in mind (e.g. IP process
requirements)?
Kind Regards,
Georg