From dev-return-48118-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Oct 25 02:18:02 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 D694118065D for ; Fri, 25 Oct 2019 04:18:01 +0200 (CEST) Received: (qmail 92824 invoked by uid 500); 25 Oct 2019 02:18:00 -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 92807 invoked by uid 99); 25 Oct 2019 02:18:00 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2019 02:18:00 +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 E17261A34C7 for ; Fri, 25 Oct 2019 02:17:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.101 X-Spam-Level: * X-Spam-Status: No, score=1.101 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_REPLY=1, HTML_MESSAGE=0.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URI_HEX=0.1] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-he-de.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id HoSWSbLCW-Gs for ; Fri, 25 Oct 2019 02:17:58 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2a00:1450:4864:20::143; helo=mail-lf1-x143.google.com; envelope-from=saikat.maitra@gmail.com; receiver= Received: from mail-lf1-x143.google.com (mail-lf1-x143.google.com [IPv6:2a00:1450:4864:20::143]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id DA8D77DDE1 for ; Fri, 25 Oct 2019 02:17:57 +0000 (UTC) Received: by mail-lf1-x143.google.com with SMTP id x4so357469lfn.8 for ; Thu, 24 Oct 2019 19:17:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=aQU8ofkPktkxhZ8Oiu8STv5euGASXIn6Xg9Hao20H6I=; b=YdUjJ/Lqa/VHLI4VdDTB9gz6L1oQw9TXGclJrUu4T55vjuJNdHgXWQsYJXfYjqIrRc XqFZWl5zFiOtqQQZB5csIc+DCsbx0Xp6a5D/UUPRWa+9MvS2Ffx/tdB8xdLJ1gL8wZWH ZdqQt82O+Z81BAoX/fyDf4ieVRepTiiPO8Aj7vQaxdbvAl9Zjd3jYY9Mvy9an6meZx1g YJ7T1OrUYMN4vVBoQ3LQWREHkenIrvmnreapfc0aNNoMn5SiSyllNmBviDZq7YGQOJ3r rhXWUFdgWfSMzpfs7btjvZ/IubuinfPbT61bP5HaZWBEbagYN35jFDUktU+YxaPkHWQ+ W0hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=aQU8ofkPktkxhZ8Oiu8STv5euGASXIn6Xg9Hao20H6I=; b=S5q0eQpsrXYpOV71QKHTfzMdrn3S/JkWkEd/598rSVJhiAwK072eGRgqTtYZugC/oR a/lExOXk5F1kPF9omtE/PY/P5jae+PcXgNmECWv9JiMoCGBfE0f5+roJVWcsbuONAsLI RZlpv3MDlbuQx4Bl8HZBXGGvSEwLn5HJbneaiSqHcXKty+NL04xdJwVQ2PXzRnPgXYia r1yLSRJPmXop4ghFiPv3MuwMXbR8gq1HC4ipJcz3eRWe7hHPstPWm7icGuITEA3Wcays 1h5XR5jxRswc7qU3y4VdwyEpnLrMkx5dH75GY/bXpdLY6KjnFY7uMDcngExKuPMdqfQQ o8MA== X-Gm-Message-State: APjAAAXXaLviGeEcEXpUdIuVY9O9FBIkx7GYu4WpZHKTybS3BcW7BX6M ojL7JeRJwZbWL/ofdKsDidHvwTXrcP6e/szmjNEqxkNK X-Google-Smtp-Source: APXvYqyovg3D+6TIjGApXonVufCVO6Yes0PaKoXTU/ysJGPKpSyQLX6Vrt2TU0yQaHxACGXzdosaXTtg/a1FTBKAtGw= X-Received: by 2002:a19:f813:: with SMTP id a19mr748550lff.33.1571969876560; Thu, 24 Oct 2019 19:17:56 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Saikat Maitra Date: Thu, 24 Oct 2019 21:17:45 -0500 Message-ID: Subject: Re: [DISCUSS] Proposal for Ignite Extensions as a separate Bahir module or Incubator project To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="000000000000170f0e0595b2c2ad" --000000000000170f0e0595b2c2ad Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Denis, Yes, I see it now as I think more about it, I like option - 0. I am thinking from a new member and a contributor perspective for Ignite project, I would very much like my PR and proposal to be accepted within Ignite community. Regards, Saikat On Thu, Oct 24, 2019 at 1:56 PM Denis Magda wrote: > 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 > contribution > > outside ASF could lead projects to split their communities. > > > > I believe, the Ignite community is more open and flexible in that regar= d. > > 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 = Maitra : > > > > > Hi, > > > > > > I looked into the way Apache Bahir manages their extensions for Spark > and > > > Flink and it looks like they are much independent in terms of managin= g > > > their releases. They also have separate git repos for apache bahir an= d > > > 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 Bahi= r > > > project and managing independent release cycle will benefit us as it > will > > > help foster cross community engagement and support. The purpose of > Bahir > > is > > > also to host such extensions as ours. > > > > > > I was reading this news article and it resonated similar ideas that w= e > > 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 Ignit= e > > > > extensions/modules but those will be governed by the Ignite communi= ty > > 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 li= ke > > 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 Apach= e > > > 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 a= nd > > > > > 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, A= lexey Zinoviev < > zaleslaw.sin@gmail.com > > >: > > > > > > > > > > > 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 > > > > > 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= Maitra < > saikat.maitra@gmail.com > > >: > > > > > >> > > > > > >>> Hi, > > > > > >>> > > > > > >>> I discussed with Apache Bahir community and they are interest= ed > > to > > > > have > > > > > >>> Apache Ignite extensions as part of Apache Bahir project. > > > > > >>> > > > > > >>> I have also requested for contributor access in Jira for Apac= he > > > Bahir > > > > > >>> project so that I can create issues and assign to myself. I c= an > > > help > > > > > with > > > > > >>> 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 > > > > > 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 w= e > > 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 her= e > > > > > >>> > > > > > > >>> > > > > > > > > > > > > > > > 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 > separate > > > > > >>> 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 Apac= he > > > > Ignite > > > > > >>> > Extensions: > > > > > >>> > > > > > > >>> > 1. Reach out to Apache Bahir community and propose to make > > Ignite > > > > > >>> > Extensions a separate module as part of Apache Bahir projec= t. > > > > > >>> > > > > > > >>> > 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 > > > > > >>> > > > > > > >>> > > > > > >> > > > > > > > > > > > > > > > --000000000000170f0e0595b2c2ad--