I don't want to add more noise with a simple reply that says I agree but this time I think it is worth: I agree with this approach proposed by Gert :-) also I think that discussion on "how to act" should move to dev@ mailing list.
Then, I was curiously trying to rebuild the history of Karaf. Before I had an overall idea but not certainty. And well, I think we all shall give more focus to the fact that Karaf comes from the ServiceMix Kernel: http://web.archive.org/web/20120102122544/http://servicemix.apache.org/kernel This is not just something about pride, it is more about credibility of the solution of Karaf. Remember when I say that ServiceMix has a "(debatable) marketing value"? Well, if we outline Karaf comes from ServiceMix's Kernel, this value get transferred to Karaf too. Also, it is a Shame that nowhere on the home page of Karaf is a quote to its origin. Saying that "most of the work that used to be at SerivceMix is now happening at Karaf and Camel instead" can be discouraging if we don't have clear view of the history. Claus surely has this clear view, but me and many other developers may not, and I can misunderstand what he means. This nice link summarize the history of Karaf: http://icodebythesea.blogspot.it/2011/01/brief-history-of-apache-karaf.html Regards, Cristiano > Personally, I'd think the best place to start would be with the > ServiceMix 5 codebase - that already removes the NMR/JBI bits, so we > have a good starting point there. I'd be inclined to remove the extra > Camel stuff we have there at the moment and focus on the core > assembly, the examples and the new pax-exam-karaf based integration > tests first. That way, it's easy for people to get involved and we > have a nice attainable goal in getting a first non-JBI/NMR assembly > out without the burden of any extra code. > > Once we agree on the approach, I would try to get some of the tasks > registered in JIRA so people interested in contributing have some > place to go and look for things they can help out with. > > I'd also like to invite everyone who expressed an interest in > contributing to join the dev@ mailing list as well (cfr. > http://servicemix.apache.org/community/mailing-lists.html for more > info). As we start working on this, that's where you can get in touch > and follow up on what's happening with the JIRA issues. > > > Regards, > > Gert > Regards, > > Gert Vanthienen > > > On Tue, Feb 11, 2014 at 3:22 PM, Johan Edstrom <[email protected]> wrote: > > Where do we want to start? > > Gert and I spoke about this quite a long time ago, what really is needed > is a new parent Pom - then removal of NMR/Jbi as direct deps, maybe those > two could be better solved with embedded and hidden older jars. > > > > Sent from my pressure cooker. > > > >> On Feb 11, 2014, at 9:11, Krzysztof Sobkowiak < > [email protected]> wrote: > >> > >> I'm ready to contribute to ServiceMix (and Karaf too) but the next 4 > weeks I have still limited time capacities (due to the trainings I'm > preparing for my company) > >> > >> regards > >> Krzysztof > >> > >>> On 11.02.2014 14:46, Achim Nierbeck wrote: > >>> I wonder when and why that happened .... > >>> ... but this is a good point for all those people that > >>> raised their voices the last 4 days to show their pride of > >>> the project and get into it ;) > >>> > >>> regards, Achim > >> > >> -- > >> Krzysztof Sobkowiak > >> > >> JEE & OSS Architect | Technical Architect @ Capgemini > >> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center < > http://www.pl.capgemini-sdm.com/> | Wroclaw > >> e-mail: [email protected] <mailto:[email protected]> | > Twitter: @KSobkowiak >
