From dev-return-48088-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Oct 23 19:42:07 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id CADB4180608 for ; Wed, 23 Oct 2019 21:42:06 +0200 (CEST) Received: (qmail 80330 invoked by uid 500); 23 Oct 2019 19:42:06 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 80312 invoked by uid 99); 23 Oct 2019 19:42:05 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.42) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Oct 2019 19:42:05 +0000 Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 86A415A44 for ; Wed, 23 Oct 2019 19:42:05 +0000 (UTC) Received: by mail-wr1-f42.google.com with SMTP id q13so18415477wrs.12 for ; Wed, 23 Oct 2019 12:42:05 -0700 (PDT) X-Gm-Message-State: APjAAAUWPXdGwV7kdd0CVRA1LLiSMgaiBMmT2gd8sY4X8U48n+/EjH75 O661ipf3I82Ac02JgdVh/8/TompuM1xEPX7vcRI= X-Google-Smtp-Source: APXvYqzU1lJPqIsdXI8aVIOAbpScbu7HALHltozfjS+YOLU0XTuR17GHryJbTCg1EjVh/PVr3X/fp1p1GVn9VfnF1rw= X-Received: by 2002:adf:b1d2:: with SMTP id r18mr359280wra.138.1571859724664; Wed, 23 Oct 2019 12:42:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dmitriy Pavlov Date: Wed, 23 Oct 2019 22:41:53 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [DISCUSS] Proposal for Ignite Extensions as a separate Bahir module or Incubator project To: dev Content-Type: multipart/alternative; boundary="0000000000008685700595991cb4" --0000000000008685700595991cb4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Saikat, Alexey, Actually we have 3 ways to solve it. 0. placing integration in a separate module within space of Apache Ignite 1. Apache Bahir 2. Apache Incubator I'm not sure if option 2 is the best one since it is more about building a new community around Ignite Extensions, it may be tricky. But 0 and 1 seem to be perfectly OK. And I like option 1 most since it is very natural to move Ignite-Kafka, Ignite-Camel to a separate project specially intended for integration. So if we stay with option 1 I would be glad to help. Count on my support within the migration to Apache Bahir. Inter-project interaction and integration are usually welcomed in the ASF. Sincerely, Dmitriy Pavlov =D1=81=D1=80, 23 =D0=BE=D0=BA=D1=82. 2019 =D0=B3. =D0=B2 09:31, Alexey Zino= viev : > Also, dear Saikat Maitra, could you please describe how you see the > release cycles in Bahir Ignite Extensions and how it be related to Ignite > release, 2.9, 3.0 for example. > > Thank you for your energy > > =D1=81=D1=80, 23 =D0=BE=D0=BA=D1=82. 2019 =D0=B3., 8:10 Alexey Zinoviev <= zaleslaw.sin@gmail.com>: > >> Please, give me permissions too, I'd glad to help with this modules >> migration and support part of them in future, but also we need not only >> contributor but a few Committer permissions to merge In repository in ot= her >> side it could be very long proccess. >> >> Could you ask Bahir Community about that? >> >> =D1=81=D1=80, 23 =D0=BE=D0=BA=D1=82. 2019 =D0=B3., 2:31 Saikat Maitra : >> >>> Hi, >>> >>> I discussed with Apache Bahir community and they are interested to have >>> Apache Ignite extensions as part of Apache Bahir project. >>> >>> I have also requested for contributor access in Jira for Apache Bahir >>> project so that I can create issues and assign to myself. I can help wi= th >>> code reviews as well. >>> >>> Also my thoughts on releases specific to dependencies for Apache Ignite >>> is >>> to do a fast follow up release for modules based on latest Apache Ignit= e >>> stable release. >>> >>> Here is the email thread for reference >>> https://www.mail-archive.com/dev@bahir.apache.org/msg02703.html >>> >>> I wanted to connect and get feedback on the proposal and if we are ok t= o >>> move the following Apache Ignite Extensions >>> >>> >>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modulariza= tion#IEP-36:Modularization-IndependentIntegrations >>> >>> Regards, >>> Saikat >>> >>> >>> On Fri, Oct 18, 2019 at 9:44 PM Saikat Maitra >>> wrote: >>> >>> > Hello, >>> > >>> > We wanted to discuss on a proposal to move and support the Apache >>> Ignite >>> > integrations as separate Ignite Extensions as discussed here >>> > >>> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Pub-Sub-S= treamer-Implementation-td43944.html >>> > . >>> > >>> > The reason we wanted to move our Apache Ignite integration as separa= te >>> > Extensions is this will help us to manage and maintain separate >>> lifecycle >>> > for Apache Ignite integrations. >>> > >>> > All the integrations will continue to be part of ASF and we will kee= p >>> > supporting and developing in accordance with ASF vision and practices= . >>> > >>> > We are considering following two choices for moving to Apache Ignite >>> > Extensions: >>> > >>> > 1. Reach out to Apache Bahir community and propose to make Ignite >>> > Extensions a separate module as part of Apache Bahir project. >>> > >>> > https://bahir.apache.org/ >>> > >>> > >>> > >>> https://blogs.apache.org/foundation/entry/the_apache_software_foundatio= n_announces96 >>> > >>> > >>> > 2. Reach out to Apache Incubator community and request for a new >>> project >>> > for Ignite Extensions. >>> > >>> > Please review and share feedback on our proposal. >>> > >>> > Warm Regards, >>> > Saikat >>> > >>> >> --0000000000008685700595991cb4--