From dev-return-48115-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Oct 24 18:56:46 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 62BD018065D for ; Thu, 24 Oct 2019 20:56:46 +0200 (CEST) Received: (qmail 4985 invoked by uid 500); 24 Oct 2019 18:56:45 -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 4974 invoked by uid 99); 24 Oct 2019 18:56:45 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.42) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Oct 2019 18:56:45 +0000 Received: from mail-il1-f179.google.com (mail-il1-f179.google.com [209.85.166.179]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 4D8525A44 for ; Thu, 24 Oct 2019 18:56:45 +0000 (UTC) Received: by mail-il1-f179.google.com with SMTP id d83so14938550ilk.7 for ; Thu, 24 Oct 2019 11:56:45 -0700 (PDT) X-Gm-Message-State: APjAAAVWBfop2KqrH6S8cmszed5eRUGzlnKyTk/YtIkZ7nS1BhiDHmLD eBTHjEX3RH4+zNJIIFanx21Xoe/4yjWY6ZnwOQhtuQ== X-Google-Smtp-Source: APXvYqywnhgakYA+TxlGL8Cszq2ZlKgeOZBPDtm44IKMBMhQnfA38dBR1lYeW4XqnOtWQy03cuSfDBYR9rK5JQAXT6A= X-Received: by 2002:a92:4952:: with SMTP id w79mr48068922ila.70.1571943404775; Thu, 24 Oct 2019 11:56:44 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Denis Magda Date: Thu, 24 Oct 2019 11:56:15 -0700 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="0000000000003fdefa0595ac98f4" --0000000000003fdefa0595ac98f4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Exactly, Dmitry found the right word for the reason why option-0 might be the best one - to avoid the Ignite community *split*. All those who will be contributing to integrations and extensions need to be able to earn a status of an Ignite committer and PMC members. Otherwise, I'm not sure if Emmanouil and others to come will be fully involved in the Ignite community= . Saikat, Emmanouil, what do you think if to look from this perspective? - Denis On Thu, Oct 24, 2019 at 12:04 AM Dmitriy Pavlov wrote: > Hah, IMHO, it is a story of how pushing others to place their contributio= n > outside ASF could lead projects to split their communities. > > I believe, the Ignite community is more open and flexible in that regard. > So Option-0. is also OK from my perspective. > > =D1=87=D1=82, 24 =D0=BE=D0=BA=D1=82. 2019 =D0=B3. =D0=B2 04:01, Saikat Ma= itra : > > > Hi, > > > > I looked into the way Apache Bahir manages their extensions for Spark a= nd > > Flink and it looks like they are much independent in terms of managing > > their releases. They also have separate git repos for apache bahir and > > apache bahir-flink. > > > > Releases : > > https://bahir.apache.org/downloads/spark/ > > https://bahir.apache.org/downloads/flink/ > > > > Repos : > > https://github.com/apache/bahir > > https://github.com/apache/bahir-flink > > > > > > I am thinking if we are following the similar pattern we can create a > > separate git repo under the Org apache / ignite-extentions or apache / > > bahir-ignite. > > > > If most of our integrations are data streaming connectors that we are > most > > interested to migrate to separate repository then joining Apache Bahir > > project and managing independent release cycle will benefit us as it wi= ll > > help foster cross community engagement and support. The purpose of Bahi= r > is > > also to host such extensions as ours. > > > > I was reading this news article and it resonated similar ideas that we > have > > specific to managing release cycles > > https://thenewstack.io/apache-bahir-gives-spark-extensions-new-home/ > > > > Please review and share your feedback. > > > > Warm Regards, > > Saikat > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, Oct 23, 2019 at 4:29 PM Denis Magda wrote: > > > > > Folks, > > > > > > How about considering the option Dmitriy named as "0. placing > integration > > > in a separate module within space of Apache Ignite"? > > > > > > Nothing prevents us from following concepts of Bahir project in the > sense > > > that we'll be creating and managing separate repositories for Ignite > > > extensions/modules but those will be governed by the Ignite community > and > > > all the contributors to the extensions will be becoming Ignite > committers > > > and PMC members. The more I think about this approach the more I like > it. > > > Any thoughts? > > > > > > - > > > Denis > > > > > > > > > On Wed, Oct 23, 2019 at 12:42 PM Dmitriy Pavlov > > > wrote: > > > > > > > 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, Ale= xey Zinoviev >: > > > > > > > > > Also, dear Saikat Maitra, could you please describe how you see t= he > > > > > release cycles in Bahir Ignite Extensions and how it be related t= o > > > 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 Zi= noviev >: > > > > > > > > > >> 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 n= ot > > > only > > > > >> contributor but a few Committer permissions to merge In reposito= ry > > in > > > > other > > > > >> 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 M= aitra >: > > > > >> > > > > >>> 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 > > > > with > > > > >>> code reviews as well. > > > > >>> > > > > >>> Also my thoughts on releases specific to dependencies for Apach= e > > > Ignite > > > > >>> is > > > > >>> to do a fast follow up release for modules based on latest Apac= he > > > > Ignite > > > > >>> 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 > > > > to > > > > >>> move the following Apache Ignite Extensions > > > > >>> > > > > >>> > > > > >>> > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularizati= on#IEP-36:Modularization-IndependentIntegrations > > > > >>> > > > > >>> Regards, > > > > >>> Saikat > > > > >>> > > > > >>> > > > > >>> On Fri, Oct 18, 2019 at 9:44 PM Saikat Maitra < > > > saikat.maitra@gmail.com > > > > > > > > > >>> 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-Str= eamer-Implementation-td43944.html > > > > >>> > . > > > > >>> > > > > > >>> > The reason we wanted to move our Apache Ignite integration as > > > > separate > > > > >>> > Extensions is this will help us to manage and maintain separa= te > > > > >>> lifecycle > > > > >>> > for Apache Ignite integrations. > > > > >>> > > > > > >>> > All the integrations will continue to be part of ASF and we > will > > > > keep > > > > >>> > 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_foundation_= 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 > > > > >>> > > > > > >>> > > > > >> > > > > > > > > > > --0000000000003fdefa0595ac98f4--