felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Nodet <gno...@apache.org>
Subject Re: Implementation of unreleased spec and community
Date Wed, 18 Jan 2017 13:31:07 GMT
2017-01-18 11:59 GMT+01:00 David Bosschaert <david.bosschaert@gmail.com>:

> 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 everyone can post
> feedback, described at https://github.com/osgi/design
> OSGi works very hard in defining specs that are portable and can be
> implemented without the need to pay for any licenses or anything of that
> sort.
> History has shown that spec implementations are really quite portable.
> Implementation bundles can be mixed from different sources and everything
> just works as long as you use the specced APIs.
> Every new spec that is being worked on in OSGi needs, besides the RFP/RFC
> and spec chapter, a Reference Implementation and a Conformance Testsuite.
> Over the past 10 years or so, Reference Implementations have primarily been
> implemented in open source. This has the benefit that everyone can see what
> the implementation is going to be and also it allows everyone to provide
> feedback and participate in the implementation.

That's very fine.  Fwiw, I really don't think this is advertised anywhere.
I mean, I'm quite sure there's no way you can know where the RI is being
developed by looking at the public documents from the OSGi Alliance.  So
while the goal is interesting, I doubt a lot of non members know where the
RI is being developed.

> Apache committers have free
> access to the relevant CTs as well.
> I think this is all goodness. Or would you rather see that Reference
> Implementations are implemented in private?

Definitely not.  Though, for myself, if the RI is LGPL, I won't use it, so
it does not matter to me.  However, a ASL2 / BSD licensed RI is very
interesting for users.  But that has nothing to do with *where* this RI is
developed.  You can perfectly develop an ASL2 RI at github.
If you want to do it at Apache, you need to follow its rules.

> Best regards,
> David
> On 18 January 2017 at 10:41, Guillaume Nodet <gnodet@apache.org> wrote:
> > 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, because it's still being
> > developed at the OSGi Alliance.  I find that very disturbing because
> > there's no way the community can get involved unless they are OSGi
> Alliance
> > members, and that's clearly not acceptable imho.
> >
> > Thoughts ?
> > Guillaume Nodet
> >

Guillaume Nodet
Red Hat, Open Source Integration

Email: gnodet@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message