Guillaume Nodet wrote > >> There is no difference? Really? Claiming the current approach is not >> optimal from a community perspective is certainly not unreasonable, but >> saying that the community doesn't benefit at all from having draft >> implementations being worked on at Apache seems like a stretch. > > > Can you outline the benefits then ? Honestly, I don't see the difference > between such an implementation being developed at Apache and the same one > being developed under the same license at github. At github, I can also > fork, provide PR, raise issues, etc... > Why is github the alternative to Apache? If my work is not valued by the Felix community I have no incentive to do it at github. It would rather be company internal or maybe at the Eclipse foundation. > > > Shaping future evolution is definitely a privilege of OSGi Alliance members > and again, I have no problem with that part. The problem is not whether > OSGi members have more information or not, it's whether non OSGi members > have enough information or not to implement a spec. When the > implementation is used as a play ground for the spec design, that's > definitely not true. > I've written some of the implementations of the current RFCs and believe me the RFC document is all you need. And if not, there are the mentioned channels to ask for clarifications.
Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
