You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Thomas Diesler <th...@jboss.com> on 2010/01/19 14:40:01 UTC
Aries Blueprint spec compliance
Hi Folks,
I'm considering to ship Aries Blueprint with JBoss OSGi.
Could you perhaps give me a rough idea what level of spec compliance
(i.e. TCK pass rate) is reached by this implementation?
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Re: Aries Blueprint spec compliance
Posted by Jeremy Hughes <hu...@apache.org>.
Yeah, it would be nice to be able to say in our release that (e.g.)
Aries Blueprint is spec compliant.
Jeremy
On 26 February 2010 14:16, Alasdair Nottingham <no...@apache.org> wrote:
> Kevan,
>
> Have you made any progress on what can be done here?
>
> Thanks
> Alasdair
>
> On 19 January 2010 15:31, Kevan Miller <ke...@gmail.com> wrote:
>>
>> On Jan 19, 2010, at 8:40 AM, Thomas Diesler wrote:
>>
>>> Hi Folks,
>>>
>>> I'm considering to ship Aries Blueprint with JBoss OSGi.
>>> Could you perhaps give me a rough idea what level of spec compliance (i.e. TCK pass rate) is reached by this implementation?
>>
>> Hi Thomas,
>> Sounds great.
>>
>> As a project, we have not run the Compliance Tests (more later). So, as a project, I don't think we can claim compliance. Individuals/organizations have run Blueprint against the CT, would leave it up to them on what statements they can or cannot make about compliance.
>>
>> Will note that the Aries community has not yet performed a release. So, the current codebase has not yet been through an official review by the ASF. Hopefully, the community will be working on that in the near future.
>>
>> With regard to CT -- It's my understanding ASF now has access to the OSGi Compliance Tests. I'm confirming the process for obtaining the CT. An Aries committer will be able to obtain the CT after submitting an NDA to the ASF -- http://www.apache.org/jcp/ApacheNDA.pdf. The OSGi CT needs to be kept private -- it should not redistributed outside of the ASF.
>>
>> I'll keep the group informed...
>>
>> --kevan
>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
Re: Aries Blueprint spec compliance
Posted by Joe Bohn <jo...@gmail.com>.
That is my take as well.
Joe
David Jencks wrote:
> What works in my mind...
>
> if you want to discuss compliance on apache lists or run the ct for the
> benefit of the apache project you should file the apache NDA.
>
> If you want to discuss compliance with your employer on whatever code
> your employers license with osgi may let you work with, that has nothing
> to do with apache.
>
> IANAL etc etc
>
> david jencks
>
> On Mar 1, 2010, at 11:02 AM, Alasdair Nottingham wrote:
>
>> I'm not sure this fully addresses Jeremy's question though. I think he
>> is asking if people who have access to the CT via their employer need
>> to have the additional NDA filed to discuss CT related issues. Since
>> they can validly obtain the CT directly from the alliance.
>>
>> Alasdair
>>
>> On 1 Mar 2010, at 18:18, Lin Sun <li...@gmail.com> wrote:
>>
>>> I agree, that sounds reasonable. We can then start discussing on the
>>> list how we want to run the osgi CT with our aries jar and hopefully
>>> people can execute one command to get all test results.
>>>
>>> P.S. I think it is called Compliance Test (CT) instead of TCK.
>>>
>>> Lin
>>>
>>> On Mon, Mar 1, 2010 at 5:54 AM, Guillaume Nodet <gn...@gmail.com>
>>> wrote:
>>>> What about following the route other projects have already used ? i.e.
>>>> create a private mailing list opened to all aries committers with a
>>>> filed NDA and discuss any TCK related issues there ? A restricited
>>>> svn area could be set up as well to hold TCK material or custom
>>>> configs, scripts, etc...
>>>>
>>>> On Mon, Mar 1, 2010 at 11:47, Jeremy Hughes <hu...@apache.org> wrote:
>>>>> I know there are many people on this list whose employer is a member
>>>>> of the OSGi Alliance and hence they have access to OSGi member
>>>>> materials. Myself included. There are others that aren't so this is
>>>>> great step forward. I have some questions though:
>>>>>
>>>>> Do the results of running OSGi Compliance Tests count as confidential
>>>>> or non-confidential? For example, stack traces and other diagnostic
>>>>> information produced as the output to failing tests. Consider someone
>>>>> who signs this NDA and configures a test machine with the appropriate
>>>>> access controls to run the OSGi CTs for each hudson build. Can the
>>>>> results be made publicly available? Can even a public yes/no be made
>>>>> as to whether the CTs pass? This phrase in the NDA is the closest I
>>>>> could find to this:
>>>>>
>>>>> "My subsequent use of the general knowledge, skills and experience
>>>>> that I gain as a result of working with the information will not
>>>>> constitute a breach of these obligations."
>>>>>
>>>>> but IANAL and this may just be about not limiting the individual's
>>>>> subsequent pursuits.
>>>>>
>>>>> Also, where does this leave people who already have access to the
>>>>> confidential material through another route (employer for example). I
>>>>> wouldn't have thought they need to sign this NDA as they are not
>>>>> receiving this information from the OSGi Alliance via the ASF. Then,
>>>>> it is down to that person's individual or employer relationship with
>>>>> the OSGi Alliance as to whether they are permitted to run tests
>>>>> against Apache Aries and subsequently publish results. I hope there is
>>>>> a mechanism (SVN revision number for example) of identifying the level
>>>>> of the CTs that are run.
>>>>>
>>>>> At this point, it seems this is a discussion better had on a legal
>>>>> list ... legal@ or jcp@
>>>>>
>>>>> Thanks,
>>>>> Jeremy
>>>>>
>>>>> On 26 February 2010 19:58, Kevan Miller <ke...@gmail.com>
>>>>> wrote:
>>>>>>
>>>>>> On Feb 26, 2010, at 9:16 AM, Alasdair Nottingham wrote:
>>>>>>
>>>>>>> Kevan,
>>>>>>>
>>>>>>> Have you made any progress on what can be done here?
>>>>>>
>>>>>> This process may change, but for now you can submit the Apache NDA
>>>>>> -- http://apache.org/jcp/ApacheNDA.pdf
>>>>>>
>>>>>> Fax to US +1-919-573-9199 or email a pdf scanned version to
>>>>>> secretary@
>>>>>>
>>>>>> Then send an email to jcp@ Something like:
>>>>>>
>>>>>> Subject: OSGI CT access
>>>>>>
>>>>>> I'm a committer on the Apache Aries project and would like access
>>>>>> to the OSGi CT. I've submitted an NDA.
>>>>>>
>>>>>> --kevan
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Guillaume Nodet
>>>> ------------------------
>>>> Blog: http://gnodet.blogspot.com/
>>>> ------------------------
>>>> Open Source SOA
>>>> http://fusesource.com
>>>>
>
>
--
Joe
Re: Aries Blueprint spec compliance
Posted by Lin Sun <li...@gmail.com>.
Yes I kinda interpret it the same way :)
Lin
On Mon, Mar 1, 2010 at 2:13 PM, David Jencks <da...@yahoo.com> wrote:
> What works in my mind...
>
> if you want to discuss compliance on apache lists or run the ct for the
> benefit of the apache project you should file the apache NDA.
>
> If you want to discuss compliance with your employer on whatever code your
> employers license with osgi may let you work with, that has nothing to do
> with apache.
>
> IANAL etc etc
>
> david jencks
>
> On Mar 1, 2010, at 11:02 AM, Alasdair Nottingham wrote:
>
>> I'm not sure this fully addresses Jeremy's question though. I think he is
>> asking if people who have access to the CT via their employer need to have
>> the additional NDA filed to discuss CT related issues. Since they can
>> validly obtain the CT directly from the alliance.
>>
>> Alasdair
>>
>> On 1 Mar 2010, at 18:18, Lin Sun <li...@gmail.com> wrote:
>>
>>> I agree, that sounds reasonable. We can then start discussing on the
>>> list how we want to run the osgi CT with our aries jar and hopefully
>>> people can execute one command to get all test results.
>>>
>>> P.S. I think it is called Compliance Test (CT) instead of TCK.
>>>
>>> Lin
>>>
>>> On Mon, Mar 1, 2010 at 5:54 AM, Guillaume Nodet <gn...@gmail.com> wrote:
>>>>
>>>> What about following the route other projects have already used ? i.e.
>>>> create a private mailing list opened to all aries committers with a
>>>> filed NDA and discuss any TCK related issues there ? A restricited
>>>> svn area could be set up as well to hold TCK material or custom
>>>> configs, scripts, etc...
>>>>
>>>> On Mon, Mar 1, 2010 at 11:47, Jeremy Hughes <hu...@apache.org> wrote:
>>>>>
>>>>> I know there are many people on this list whose employer is a member
>>>>> of the OSGi Alliance and hence they have access to OSGi member
>>>>> materials. Myself included. There are others that aren't so this is
>>>>> great step forward. I have some questions though:
>>>>>
>>>>> Do the results of running OSGi Compliance Tests count as confidential
>>>>> or non-confidential? For example, stack traces and other diagnostic
>>>>> information produced as the output to failing tests. Consider someone
>>>>> who signs this NDA and configures a test machine with the appropriate
>>>>> access controls to run the OSGi CTs for each hudson build. Can the
>>>>> results be made publicly available? Can even a public yes/no be made
>>>>> as to whether the CTs pass? This phrase in the NDA is the closest I
>>>>> could find to this:
>>>>>
>>>>> "My subsequent use of the general knowledge, skills and experience
>>>>> that I gain as a result of working with the information will not
>>>>> constitute a breach of these obligations."
>>>>>
>>>>> but IANAL and this may just be about not limiting the individual's
>>>>> subsequent pursuits.
>>>>>
>>>>> Also, where does this leave people who already have access to the
>>>>> confidential material through another route (employer for example). I
>>>>> wouldn't have thought they need to sign this NDA as they are not
>>>>> receiving this information from the OSGi Alliance via the ASF. Then,
>>>>> it is down to that person's individual or employer relationship with
>>>>> the OSGi Alliance as to whether they are permitted to run tests
>>>>> against Apache Aries and subsequently publish results. I hope there is
>>>>> a mechanism (SVN revision number for example) of identifying the level
>>>>> of the CTs that are run.
>>>>>
>>>>> At this point, it seems this is a discussion better had on a legal
>>>>> list ... legal@ or jcp@
>>>>>
>>>>> Thanks,
>>>>> Jeremy
>>>>>
>>>>> On 26 February 2010 19:58, Kevan Miller <ke...@gmail.com> wrote:
>>>>>>
>>>>>> On Feb 26, 2010, at 9:16 AM, Alasdair Nottingham wrote:
>>>>>>
>>>>>>> Kevan,
>>>>>>>
>>>>>>> Have you made any progress on what can be done here?
>>>>>>
>>>>>> This process may change, but for now you can submit the Apache NDA --
>>>>>> http://apache.org/jcp/ApacheNDA.pdf
>>>>>>
>>>>>> Fax to US +1-919-573-9199 or email a pdf scanned version to secretary@
>>>>>>
>>>>>> Then send an email to jcp@ Something like:
>>>>>>
>>>>>> Subject: OSGI CT access
>>>>>>
>>>>>> I'm a committer on the Apache Aries project and would like access to
>>>>>> the OSGi CT. I've submitted an NDA.
>>>>>>
>>>>>> --kevan
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Cheers,
>>>> Guillaume Nodet
>>>> ------------------------
>>>> Blog: http://gnodet.blogspot.com/
>>>> ------------------------
>>>> Open Source SOA
>>>> http://fusesource.com
>>>>
>
>
Re: Aries Blueprint spec compliance
Posted by David Jencks <da...@yahoo.com>.
What works in my mind...
if you want to discuss compliance on apache lists or run the ct for
the benefit of the apache project you should file the apache NDA.
If you want to discuss compliance with your employer on whatever code
your employers license with osgi may let you work with, that has
nothing to do with apache.
IANAL etc etc
david jencks
On Mar 1, 2010, at 11:02 AM, Alasdair Nottingham wrote:
> I'm not sure this fully addresses Jeremy's question though. I think
> he is asking if people who have access to the CT via their employer
> need to have the additional NDA filed to discuss CT related issues.
> Since they can validly obtain the CT directly from the alliance.
>
> Alasdair
>
> On 1 Mar 2010, at 18:18, Lin Sun <li...@gmail.com> wrote:
>
>> I agree, that sounds reasonable. We can then start discussing on the
>> list how we want to run the osgi CT with our aries jar and hopefully
>> people can execute one command to get all test results.
>>
>> P.S. I think it is called Compliance Test (CT) instead of TCK.
>>
>> Lin
>>
>> On Mon, Mar 1, 2010 at 5:54 AM, Guillaume Nodet <gn...@gmail.com>
>> wrote:
>>> What about following the route other projects have already used ?
>>> i.e.
>>> create a private mailing list opened to all aries committers with a
>>> filed NDA and discuss any TCK related issues there ? A restricited
>>> svn area could be set up as well to hold TCK material or custom
>>> configs, scripts, etc...
>>>
>>> On Mon, Mar 1, 2010 at 11:47, Jeremy Hughes <hu...@apache.org>
>>> wrote:
>>>> I know there are many people on this list whose employer is a
>>>> member
>>>> of the OSGi Alliance and hence they have access to OSGi member
>>>> materials. Myself included. There are others that aren't so this is
>>>> great step forward. I have some questions though:
>>>>
>>>> Do the results of running OSGi Compliance Tests count as
>>>> confidential
>>>> or non-confidential? For example, stack traces and other diagnostic
>>>> information produced as the output to failing tests. Consider
>>>> someone
>>>> who signs this NDA and configures a test machine with the
>>>> appropriate
>>>> access controls to run the OSGi CTs for each hudson build. Can the
>>>> results be made publicly available? Can even a public yes/no be
>>>> made
>>>> as to whether the CTs pass? This phrase in the NDA is the closest I
>>>> could find to this:
>>>>
>>>> "My subsequent use of the general knowledge, skills and experience
>>>> that I gain as a result of working with the information will not
>>>> constitute a breach of these obligations."
>>>>
>>>> but IANAL and this may just be about not limiting the individual's
>>>> subsequent pursuits.
>>>>
>>>> Also, where does this leave people who already have access to the
>>>> confidential material through another route (employer for
>>>> example). I
>>>> wouldn't have thought they need to sign this NDA as they are not
>>>> receiving this information from the OSGi Alliance via the ASF.
>>>> Then,
>>>> it is down to that person's individual or employer relationship
>>>> with
>>>> the OSGi Alliance as to whether they are permitted to run tests
>>>> against Apache Aries and subsequently publish results. I hope
>>>> there is
>>>> a mechanism (SVN revision number for example) of identifying the
>>>> level
>>>> of the CTs that are run.
>>>>
>>>> At this point, it seems this is a discussion better had on a legal
>>>> list ... legal@ or jcp@
>>>>
>>>> Thanks,
>>>> Jeremy
>>>>
>>>> On 26 February 2010 19:58, Kevan Miller <ke...@gmail.com>
>>>> wrote:
>>>>>
>>>>> On Feb 26, 2010, at 9:16 AM, Alasdair Nottingham wrote:
>>>>>
>>>>>> Kevan,
>>>>>>
>>>>>> Have you made any progress on what can be done here?
>>>>>
>>>>> This process may change, but for now you can submit the Apache
>>>>> NDA -- http://apache.org/jcp/ApacheNDA.pdf
>>>>>
>>>>> Fax to US +1-919-573-9199 or email a pdf scanned version to
>>>>> secretary@
>>>>>
>>>>> Then send an email to jcp@ Something like:
>>>>>
>>>>> Subject: OSGI CT access
>>>>>
>>>>> I'm a committer on the Apache Aries project and would like
>>>>> access to the OSGi CT. I've submitted an NDA.
>>>>>
>>>>> --kevan
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Guillaume Nodet
>>> ------------------------
>>> Blog: http://gnodet.blogspot.com/
>>> ------------------------
>>> Open Source SOA
>>> http://fusesource.com
>>>
Re: Aries Blueprint spec compliance
Posted by Alasdair Nottingham <no...@apache.org>.
I'm not sure this fully addresses Jeremy's question though. I think he
is asking if people who have access to the CT via their employer need
to have the additional NDA filed to discuss CT related issues. Since
they can validly obtain the CT directly from the alliance.
Alasdair
On 1 Mar 2010, at 18:18, Lin Sun <li...@gmail.com> wrote:
> I agree, that sounds reasonable. We can then start discussing on the
> list how we want to run the osgi CT with our aries jar and hopefully
> people can execute one command to get all test results.
>
> P.S. I think it is called Compliance Test (CT) instead of TCK.
>
> Lin
>
> On Mon, Mar 1, 2010 at 5:54 AM, Guillaume Nodet <gn...@gmail.com>
> wrote:
>> What about following the route other projects have already used ?
>> i.e.
>> create a private mailing list opened to all aries committers with a
>> filed NDA and discuss any TCK related issues there ? A restricited
>> svn area could be set up as well to hold TCK material or custom
>> configs, scripts, etc...
>>
>> On Mon, Mar 1, 2010 at 11:47, Jeremy Hughes <hu...@apache.org>
>> wrote:
>>> I know there are many people on this list whose employer is a member
>>> of the OSGi Alliance and hence they have access to OSGi member
>>> materials. Myself included. There are others that aren't so this is
>>> great step forward. I have some questions though:
>>>
>>> Do the results of running OSGi Compliance Tests count as
>>> confidential
>>> or non-confidential? For example, stack traces and other diagnostic
>>> information produced as the output to failing tests. Consider
>>> someone
>>> who signs this NDA and configures a test machine with the
>>> appropriate
>>> access controls to run the OSGi CTs for each hudson build. Can the
>>> results be made publicly available? Can even a public yes/no be made
>>> as to whether the CTs pass? This phrase in the NDA is the closest I
>>> could find to this:
>>>
>>> "My subsequent use of the general knowledge, skills and experience
>>> that I gain as a result of working with the information will not
>>> constitute a breach of these obligations."
>>>
>>> but IANAL and this may just be about not limiting the individual's
>>> subsequent pursuits.
>>>
>>> Also, where does this leave people who already have access to the
>>> confidential material through another route (employer for
>>> example). I
>>> wouldn't have thought they need to sign this NDA as they are not
>>> receiving this information from the OSGi Alliance via the ASF. Then,
>>> it is down to that person's individual or employer relationship with
>>> the OSGi Alliance as to whether they are permitted to run tests
>>> against Apache Aries and subsequently publish results. I hope
>>> there is
>>> a mechanism (SVN revision number for example) of identifying the
>>> level
>>> of the CTs that are run.
>>>
>>> At this point, it seems this is a discussion better had on a legal
>>> list ... legal@ or jcp@
>>>
>>> Thanks,
>>> Jeremy
>>>
>>> On 26 February 2010 19:58, Kevan Miller <ke...@gmail.com>
>>> wrote:
>>>>
>>>> On Feb 26, 2010, at 9:16 AM, Alasdair Nottingham wrote:
>>>>
>>>>> Kevan,
>>>>>
>>>>> Have you made any progress on what can be done here?
>>>>
>>>> This process may change, but for now you can submit the Apache
>>>> NDA -- http://apache.org/jcp/ApacheNDA.pdf
>>>>
>>>> Fax to US +1-919-573-9199 or email a pdf scanned version to
>>>> secretary@
>>>>
>>>> Then send an email to jcp@ Something like:
>>>>
>>>> Subject: OSGI CT access
>>>>
>>>> I'm a committer on the Apache Aries project and would like
>>>> access to the OSGi CT. I've submitted an NDA.
>>>>
>>>> --kevan
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
Re: Aries Blueprint spec compliance
Posted by Lin Sun <li...@gmail.com>.
I agree, that sounds reasonable. We can then start discussing on the
list how we want to run the osgi CT with our aries jar and hopefully
people can execute one command to get all test results.
P.S. I think it is called Compliance Test (CT) instead of TCK.
Lin
On Mon, Mar 1, 2010 at 5:54 AM, Guillaume Nodet <gn...@gmail.com> wrote:
> What about following the route other projects have already used ? i.e.
> create a private mailing list opened to all aries committers with a
> filed NDA and discuss any TCK related issues there ? A restricited
> svn area could be set up as well to hold TCK material or custom
> configs, scripts, etc...
>
> On Mon, Mar 1, 2010 at 11:47, Jeremy Hughes <hu...@apache.org> wrote:
>> I know there are many people on this list whose employer is a member
>> of the OSGi Alliance and hence they have access to OSGi member
>> materials. Myself included. There are others that aren't so this is
>> great step forward. I have some questions though:
>>
>> Do the results of running OSGi Compliance Tests count as confidential
>> or non-confidential? For example, stack traces and other diagnostic
>> information produced as the output to failing tests. Consider someone
>> who signs this NDA and configures a test machine with the appropriate
>> access controls to run the OSGi CTs for each hudson build. Can the
>> results be made publicly available? Can even a public yes/no be made
>> as to whether the CTs pass? This phrase in the NDA is the closest I
>> could find to this:
>>
>> "My subsequent use of the general knowledge, skills and experience
>> that I gain as a result of working with the information will not
>> constitute a breach of these obligations."
>>
>> but IANAL and this may just be about not limiting the individual's
>> subsequent pursuits.
>>
>> Also, where does this leave people who already have access to the
>> confidential material through another route (employer for example). I
>> wouldn't have thought they need to sign this NDA as they are not
>> receiving this information from the OSGi Alliance via the ASF. Then,
>> it is down to that person's individual or employer relationship with
>> the OSGi Alliance as to whether they are permitted to run tests
>> against Apache Aries and subsequently publish results. I hope there is
>> a mechanism (SVN revision number for example) of identifying the level
>> of the CTs that are run.
>>
>> At this point, it seems this is a discussion better had on a legal
>> list ... legal@ or jcp@
>>
>> Thanks,
>> Jeremy
>>
>> On 26 February 2010 19:58, Kevan Miller <ke...@gmail.com> wrote:
>>>
>>> On Feb 26, 2010, at 9:16 AM, Alasdair Nottingham wrote:
>>>
>>>> Kevan,
>>>>
>>>> Have you made any progress on what can be done here?
>>>
>>> This process may change, but for now you can submit the Apache NDA -- http://apache.org/jcp/ApacheNDA.pdf
>>>
>>> Fax to US +1-919-573-9199 or email a pdf scanned version to secretary@
>>>
>>> Then send an email to jcp@ Something like:
>>>
>>> Subject: OSGI CT access
>>>
>>> I'm a committer on the Apache Aries project and would like access to the OSGi CT. I've submitted an NDA.
>>>
>>> --kevan
>>>
>>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: Aries Blueprint spec compliance
Posted by Guillaume Nodet <gn...@gmail.com>.
What about following the route other projects have already used ? i.e.
create a private mailing list opened to all aries committers with a
filed NDA and discuss any TCK related issues there ? A restricited
svn area could be set up as well to hold TCK material or custom
configs, scripts, etc...
On Mon, Mar 1, 2010 at 11:47, Jeremy Hughes <hu...@apache.org> wrote:
> I know there are many people on this list whose employer is a member
> of the OSGi Alliance and hence they have access to OSGi member
> materials. Myself included. There are others that aren't so this is
> great step forward. I have some questions though:
>
> Do the results of running OSGi Compliance Tests count as confidential
> or non-confidential? For example, stack traces and other diagnostic
> information produced as the output to failing tests. Consider someone
> who signs this NDA and configures a test machine with the appropriate
> access controls to run the OSGi CTs for each hudson build. Can the
> results be made publicly available? Can even a public yes/no be made
> as to whether the CTs pass? This phrase in the NDA is the closest I
> could find to this:
>
> "My subsequent use of the general knowledge, skills and experience
> that I gain as a result of working with the information will not
> constitute a breach of these obligations."
>
> but IANAL and this may just be about not limiting the individual's
> subsequent pursuits.
>
> Also, where does this leave people who already have access to the
> confidential material through another route (employer for example). I
> wouldn't have thought they need to sign this NDA as they are not
> receiving this information from the OSGi Alliance via the ASF. Then,
> it is down to that person's individual or employer relationship with
> the OSGi Alliance as to whether they are permitted to run tests
> against Apache Aries and subsequently publish results. I hope there is
> a mechanism (SVN revision number for example) of identifying the level
> of the CTs that are run.
>
> At this point, it seems this is a discussion better had on a legal
> list ... legal@ or jcp@
>
> Thanks,
> Jeremy
>
> On 26 February 2010 19:58, Kevan Miller <ke...@gmail.com> wrote:
>>
>> On Feb 26, 2010, at 9:16 AM, Alasdair Nottingham wrote:
>>
>>> Kevan,
>>>
>>> Have you made any progress on what can be done here?
>>
>> This process may change, but for now you can submit the Apache NDA -- http://apache.org/jcp/ApacheNDA.pdf
>>
>> Fax to US +1-919-573-9199 or email a pdf scanned version to secretary@
>>
>> Then send an email to jcp@ Something like:
>>
>> Subject: OSGI CT access
>>
>> I'm a committer on the Apache Aries project and would like access to the OSGi CT. I've submitted an NDA.
>>
>> --kevan
>>
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Aries Blueprint spec compliance
Posted by Jeremy Hughes <hu...@apache.org>.
I know there are many people on this list whose employer is a member
of the OSGi Alliance and hence they have access to OSGi member
materials. Myself included. There are others that aren't so this is
great step forward. I have some questions though:
Do the results of running OSGi Compliance Tests count as confidential
or non-confidential? For example, stack traces and other diagnostic
information produced as the output to failing tests. Consider someone
who signs this NDA and configures a test machine with the appropriate
access controls to run the OSGi CTs for each hudson build. Can the
results be made publicly available? Can even a public yes/no be made
as to whether the CTs pass? This phrase in the NDA is the closest I
could find to this:
"My subsequent use of the general knowledge, skills and experience
that I gain as a result of working with the information will not
constitute a breach of these obligations."
but IANAL and this may just be about not limiting the individual's
subsequent pursuits.
Also, where does this leave people who already have access to the
confidential material through another route (employer for example). I
wouldn't have thought they need to sign this NDA as they are not
receiving this information from the OSGi Alliance via the ASF. Then,
it is down to that person's individual or employer relationship with
the OSGi Alliance as to whether they are permitted to run tests
against Apache Aries and subsequently publish results. I hope there is
a mechanism (SVN revision number for example) of identifying the level
of the CTs that are run.
At this point, it seems this is a discussion better had on a legal
list ... legal@ or jcp@
Thanks,
Jeremy
On 26 February 2010 19:58, Kevan Miller <ke...@gmail.com> wrote:
>
> On Feb 26, 2010, at 9:16 AM, Alasdair Nottingham wrote:
>
>> Kevan,
>>
>> Have you made any progress on what can be done here?
>
> This process may change, but for now you can submit the Apache NDA -- http://apache.org/jcp/ApacheNDA.pdf
>
> Fax to US +1-919-573-9199 or email a pdf scanned version to secretary@
>
> Then send an email to jcp@ Something like:
>
> Subject: OSGI CT access
>
> I'm a committer on the Apache Aries project and would like access to the OSGi CT. I've submitted an NDA.
>
> --kevan
>
>
Re: Aries Blueprint spec compliance
Posted by Kevan Miller <ke...@gmail.com>.
On Feb 26, 2010, at 9:16 AM, Alasdair Nottingham wrote:
> Kevan,
>
> Have you made any progress on what can be done here?
This process may change, but for now you can submit the Apache NDA -- http://apache.org/jcp/ApacheNDA.pdf
Fax to US +1-919-573-9199 or email a pdf scanned version to secretary@
Then send an email to jcp@ Something like:
Subject: OSGI CT access
I'm a committer on the Apache Aries project and would like access to the OSGi CT. I've submitted an NDA.
--kevan
Re: Aries Blueprint spec compliance
Posted by Alasdair Nottingham <no...@apache.org>.
Kevan,
Have you made any progress on what can be done here?
Thanks
Alasdair
On 19 January 2010 15:31, Kevan Miller <ke...@gmail.com> wrote:
>
> On Jan 19, 2010, at 8:40 AM, Thomas Diesler wrote:
>
>> Hi Folks,
>>
>> I'm considering to ship Aries Blueprint with JBoss OSGi.
>> Could you perhaps give me a rough idea what level of spec compliance (i.e. TCK pass rate) is reached by this implementation?
>
> Hi Thomas,
> Sounds great.
>
> As a project, we have not run the Compliance Tests (more later). So, as a project, I don't think we can claim compliance. Individuals/organizations have run Blueprint against the CT, would leave it up to them on what statements they can or cannot make about compliance.
>
> Will note that the Aries community has not yet performed a release. So, the current codebase has not yet been through an official review by the ASF. Hopefully, the community will be working on that in the near future.
>
> With regard to CT -- It's my understanding ASF now has access to the OSGi Compliance Tests. I'm confirming the process for obtaining the CT. An Aries committer will be able to obtain the CT after submitting an NDA to the ASF -- http://www.apache.org/jcp/ApacheNDA.pdf. The OSGi CT needs to be kept private -- it should not redistributed outside of the ASF.
>
> I'll keep the group informed...
>
> --kevan
--
Alasdair Nottingham
not@apache.org
Re: Aries Blueprint spec compliance
Posted by Kevan Miller <ke...@gmail.com>.
On Jan 19, 2010, at 8:40 AM, Thomas Diesler wrote:
> Hi Folks,
>
> I'm considering to ship Aries Blueprint with JBoss OSGi.
> Could you perhaps give me a rough idea what level of spec compliance (i.e. TCK pass rate) is reached by this implementation?
Hi Thomas,
Sounds great.
As a project, we have not run the Compliance Tests (more later). So, as a project, I don't think we can claim compliance. Individuals/organizations have run Blueprint against the CT, would leave it up to them on what statements they can or cannot make about compliance.
Will note that the Aries community has not yet performed a release. So, the current codebase has not yet been through an official review by the ASF. Hopefully, the community will be working on that in the near future.
With regard to CT -- It's my understanding ASF now has access to the OSGi Compliance Tests. I'm confirming the process for obtaining the CT. An Aries committer will be able to obtain the CT after submitting an NDA to the ASF -- http://www.apache.org/jcp/ApacheNDA.pdf. The OSGi CT needs to be kept private -- it should not redistributed outside of the ASF.
I'll keep the group informed...
--kevan