It seems the consensus for the code is to move it to https://svn.apache.org/repos/asf/felix/trunk/karaf So i'll go ahead and move the servicemix kernel trunk there asap.
We still need to settle the problems of: * package name: org.apache.karaf vs org.apache.felix.karaf * jira issue tracker: use FELIX or create a new KARAF one * web site: use FELIX or create a new KARAF one The package renaming to org.apache.karaf has raised a number of concerns, mostly (correct me if i'm wrong) about the fact whether this would be frowned upong by the ASF or not. Given the number of subprojects that do that since a long time, I think the answer is no. Now we need to decide if we want to do this or not. For the issue tracker and web site, I think this is somewhat related to the package renaming issue above, though the problem is a bit different. I'm really opened here, but if we choose to rename the packages to org.apache.karaf, it think it would make more sense to have dedicated JIRA and confluence spaces. On Fri, Apr 24, 2009 at 09:26, Guillaume Nodet <gno...@gmail.com> wrote: > I'd like to start moving the ServiceMix Kernel code into Felix now. > Given the size of the code base, I think it would be better to just > move the tree into its own top level svn structure. > I'd like to run the following command: > > svn cp https://svn.apache.org/repos/asf/servicemix/smx4/kernel > https://svn.apache.org/repos/asf/felix/karaf > > Any objections in doing that ? > > Next steps will include creating a JIRA project and moving all the > issues into it (with a KARAF id), then the confluence space. > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
