From dev-return-9733-apmail-karaf-dev-archive=karaf.apache.org@karaf.apache.org Wed Nov 25 08:36:24 2015 Return-Path: X-Original-To: apmail-karaf-dev-archive@minotaur.apache.org Delivered-To: apmail-karaf-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 01E5118566 for ; Wed, 25 Nov 2015 08:36:24 +0000 (UTC) Received: (qmail 57559 invoked by uid 500); 25 Nov 2015 08:36:23 -0000 Delivered-To: apmail-karaf-dev-archive@karaf.apache.org Received: (qmail 57516 invoked by uid 500); 25 Nov 2015 08:36:23 -0000 Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list dev@karaf.apache.org Received: (qmail 57505 invoked by uid 99); 25 Nov 2015 08:36:23 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Nov 2015 08:36:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 2F6891A301F for ; Wed, 25 Nov 2015 08:36:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.001 X-Spam-Level: * X-Spam-Status: No, score=1.001 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id IR4Ukt_bli3x for ; Wed, 25 Nov 2015 08:36:08 +0000 (UTC) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 733E6428FF for ; Wed, 25 Nov 2015 08:36:08 +0000 (UTC) Received: from mfilter34-d.gandi.net (mfilter34-d.gandi.net [217.70.178.165]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id A06111720D5 for ; Wed, 25 Nov 2015 09:36:07 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter34-d.gandi.net Received: from relay4-d.mail.gandi.net ([IPv6:::ffff:217.70.183.196]) by mfilter34-d.gandi.net (mfilter34-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id EjSjWZ5P30VQ for ; Wed, 25 Nov 2015 09:36:06 +0100 (CET) X-Originating-IP: 82.238.224.4 Received: from [192.168.134.10] (bre91-1-82-238-224-4.fbx.proxad.net [82.238.224.4]) (Authenticated sender: jb@nanthrax.net) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id EEC5C1720BE for ; Wed, 25 Nov 2015 09:36:05 +0100 (CET) Subject: Re: [HEADS UP] Marketing and releases schedule To: dev@karaf.apache.org References: <56556CC3.1060903@nanthrax.net> <07E11E1D-F728-4909-869B-F4B646E3D297@jahia.com> From: =?UTF-8?Q?Jean-Baptiste_Onofr=c3=a9?= Message-ID: <565572F4.8020700@nanthrax.net> Date: Wed, 25 Nov 2015 09:36:04 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <07E11E1D-F728-4909-869B-F4B646E3D297@jahia.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Serge, thanks for this great feedback ;) We are definitely in line ;) Regards JB On 11/25/2015 09:31 AM, Serge Huber wrote: > Hello JB, > > I was actually thinking about this this morning too. The website seems more and more “critical” I believe to make Karaf appear as a modern “container” solution. It would actually be great to have a “roadmap” page that summarizes the ideas for the future of Karaf. I was thinking about doing this for the Unomi website too. In the roadmap of course Karaf-boot could be referenced and even the tentative code could be referenced, making it much more visible. > > For karaf-boot I think it would be great to move it to the Karaf repository asap, that way it will be more visible. Also I need to play with it to understand what you have done so far. > > On my way in to the office I was thinking that we should “leverage” existing technologies out there for Karaf boot. Much in the same way that projects like JHipster (https://jhipster.github.io) do it, it would be fantastic for example if JHipster offered a Karaf alternative to Spring-Boot. Also, maybe we could find a way to leverage Spring Boot by offering Karaf Features that embed most of the Spring libraries so that we could then say, instead of using Spring Boot and create yet-another-monolith, you could instead use Karaf Boot and the Spring features and easily create a custom distribution that provides any of the features listed here : https://github.com/spring-projects/spring-boot/tree/master/spring-boot-samples > > My thinking is that if this is done right we might even convince Pivotal to use Karaf instead of their own custom container, which would make sense for them too since they are basically (slowly) re-inventing Karaf for their needs. > > If we can streamline Karaf boot enough, it has (I believe) a huge potential. And I volunteer to do all the work to try to get Pivotal on board once we have something very smooth :) > > I’ll do my best to help out in my limited availability. > > cheers, > Serge… > >> On 25 nov. 2015, at 09:13, Achim Nierbeck wrote: >> >> Hi JB, >> >> looks good for me ... especially the move of karaf-boot to apache sounds ok >> for me ... >> it'll will get a broader visibility this way ;) >> >> regards, Achim >> >> 2015-11-25 9:09 GMT+01:00 Jean-Baptiste Onofré : >> >>> Hi all, >>> >>> I gonna work on "marketing" this afternoon (new website and documentation >>> improvements). I will update you later today with latest changes on my >>> server to discuss. I would like to move forward on this (both new website >>> and new documentation) during the week end. >>> >>> On the other hand, I propose the following release plan: >>> >>> - Karaf Cave 4.0.1 (beginning of next week): I fixed couple of issues and >>> add new features on a local branch (especially Cave is able to "gather" >>> multiple repository.xml in one, and create one repository.xml per artifact >>> if wanted) >>> - Karaf Cellar 4.0.1 (during the week end): I fixed couple of issues >>> (especially one related to Hazelcast configuration parsing with Saxon) and >>> added some new features. >>> - Karaf Decanter 1.0.2 (end of next week): several new features (ActiveMQ >>> logging plugin, Redis appender, ...) have been added >>> - Karaf Container 4.0.4 (if we use the new wording proposal ;)) (middle of >>> next week): several bug fixes and preparation for the karaf-4.0.x branch >>> >>> On the other hand, I plan to move forward on karaf-boot. About this, any >>> help would be more than appreciated ! As Achim said, I wonder if it makes >>> sense to keep it on my github or if I can already create a branch in Karaf >>> for that. Let me know. >>> >>> Thoughts ? >>> >>> Regards >>> JB >>> -- >>> Jean-Baptiste Onofré >>> jbonofre@apache.org >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com >>> >> >> >> >> -- >> >> Apache Member >> Apache Karaf Committer & PMC >> OPS4J Pax Web Committer & >> Project Lead >> blog >> Co-Author of Apache Karaf Cookbook >> >> Software Architect / Project Manager / Scrum Master > -- Jean-Baptiste Onofré jbonofre@apache.org http://blog.nanthrax.net Talend - http://www.talend.com