Re: Blueprint Spring

Ok, I'll put that on my todo list and will try to release it soon. If not, ping again. 2017-01-18 15:42 GMT+01:00 Anton Deripaska : > Hello everyone > > I have problem "Error when using Blueprint Spring with simple > configuration" but it already resoled: > https://issues.apache.org/jira/browse/

[jira] [Created] (ARIES-1665) Initial contribution of implementation of OSGi RFC-193

Raymond Augé created ARIES-1665: --- Summary: Initial contribution of implementation of OSGi RFC-193 Key: ARIES-1665 URL: https://issues.apache.org/jira/browse/ARIES-1665 Project: Aries Issue Type

ApacheCon CFP closing soon (11 February)

Hello, fellow Apache enthusiast. Thanks for your participation, and interest in, the projects of the Apache Software Foundation. I wanted to remind you that the Call For Papers (CFP) for ApacheCon North America, and Apache: Big Data North America, closes in less than a month. If you've been puttin

Re: Implementation of unreleased spec and community

> On 18 Jan 2017, at 12:36, Guillaume Nodet wrote: > > Fwiw, I think Christian was referring to the JAX-RS WHITEBOARD, not the > JAX-RS spec itself. > That one is an RFC from the OSGi Alliance... RFC-127 afaik. This is pretty much my point. Why raise an issue with the “Whiteboard” half of “JA

Re: Implementation of unreleased spec and community

Guillaume, you seem to be working from out of date information. All RFPs and RFCs are publicly available, including those that are still being developed. They are here: https://github.com/osgi/design/. This has been the case for at least four years now. Given this, I don’t see any impediment to

Re: Implementation of unreleased spec and community

Guillaume, All OSGi specifications in progress are publicly visible, so in what sense are Apache community members unable to be involved in the development of the RIs? Regards, Neil > On 18 Jan 2017, at 10:41, Guillaume Nodet wrote: > > I'm a bit concerned by some subprojects in our communiti

Blueprint Spring

Hello everyone I have problem "Error when using Blueprint Spring with simple configuration" but it already resoled: https://issues.apache.org/jira/browse/ARIES-1567 When will be releasedblueprint-spring-0.3.0 ? Looking for

Re: Implementation of unreleased spec and community

> I'm not talking about developing an implementation of a publicly released > specification. I have absolutely no problem with that of course. How is that different from developing an implementation for a publicly released DRAFT specification? In both cases you create an implementation for someth

Re: Implementation of unreleased spec and community

RFC-217 sorry https://github.com/osgi/design/tree/master/rfcs/rfc0217 2017-01-18 13:36 GMT+01:00 Guillaume Nodet : > Fwiw, I think Christian was referring to the JAX-RS WHITEBOARD, not the > JAX-RS spec itself. > That one is an RFC from the OSGi Alliance... RFC-127 afaik. > > 2017-01-18 13:

Re: Implementation of unreleased spec and community

Fwiw, I think Christian was referring to the JAX-RS WHITEBOARD, not the JAX-RS spec itself. That one is an RFC from the OSGi Alliance... RFC-127 afaik. 2017-01-18 13:34 GMT+01:00 Neil Bartlett : > Christian, your example of JAX-RS Whiteboard is fascinating, because > JAX-RS was designed by the E

Re: Implementation of unreleased spec and community

2017-01-18 11:46 GMT+01:00 Neil Bartlett : > Guillaume, > > All OSGi specifications in progress are publicly visible, so in what sense > are Apache community members unable to be involved in the development of > the RIs? > I'm not talking about developing an implementation of a publicly released

Re: Implementation of unreleased spec and community

Hi all And we should also mention that quite a number of active community members actually working on those things are members (or employees of members) of the OSGi alliance and as such open to feedback received from the communities on the evolution of the specifications. As such, I think it i

Re: Implementation of unreleased spec and community

Hi Guillaume, First of all, the OSGi Alliance is a very open standards development organization. Any organisation can join. RFPs and RFCs are developed in the open, specs are available for free and are free to be implemented by anyone. There is also an open feedback channel available where everyo

Implementation of unreleased spec and community

I'm a bit concerned by some subprojects in our communities. The ASF is supposed to be "community over code", so the very basic thing for a project is that people can get involved. However, I see more and more code developped as a reference implementation of a spec which is not publicly available,