2017-01-18 14:29 GMT+01:00 Richard S. Hall <he...@ungoverned.org>: > On 1/18/17 08:22 , Guillaume Nodet wrote: > >> 2017-01-18 13:53 GMT+01:00 Carsten Ziegeler <cziege...@apache.org>: >> >> Whoever is doing the RI >>> does it somewhere else and might do a code contribution or not. >>> >> >> Yes, that definitely would avoid the problem. >> And I don't think it changes anything from the contributor point of view : >> the reason is that it's not really developed openly, as I explained, so >> there's definitely no difference with donating the code once the spec has >> been released. >> > > 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... > > > >> Not sure >>> if that is the preferable way. We might end up with not having an >>> implementation at Apache at all. >>> >>> The ASF does not care if there is one, multiple or no implementation at >> Apache at all afaik. However, it cares about the way the community work >> and that it operates as a meritocracy, which definitely rules out the fact >> not all members have access to the same information. >> > > This seems like splitting hairs to me. Even with a complete spec, Apache > members who are also OSGi members will have access to people, processes, > and information than non-OSGi Alliance members will not, giving them an > advantage to implementing and shaping future evolution. There is no way to > level the playing field between the two. Which would be true of any > standards body where you have to be a member to participate. 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. > > > -> richard > > > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: gno...@redhat.com Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
