I agree with option 0 now, we could start from that option, and later migrate to the Bahir Community, if it is required.
чт, 24 окт. 2019 г., 9:04 Dmitriy Pavlov <dpav...@apache.org>: > 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 regard. > So Option-0. is also OK from my perspective. > > чт, 24 окт. 2019 г. в 04:01, Saikat Maitra <saikat.mai...@gmail.com>: > > > 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 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 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 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 <dma...@apache.org> 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 <dpav...@apache.org> > > > 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 > > > > > > > > ср, 23 окт. 2019 г. в 09:31, Alexey Zinoviev <zaleslaw....@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 > > > > > > > > > > ср, 23 окт. 2019 г., 8:10 Alexey Zinoviev <zaleslaw....@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? > > > > >> > > > > >> ср, 23 окт. 2019 г., 2:31 Saikat Maitra <saikat.mai...@gmail.com > >: > > > > >> > > > > >>> 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 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 we > are > > ok > > > > to > > > > >>> move the following Apache Ignite Extensions > > > > >>> > > > > >>> > > > > >>> > > > > > > > > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization#IEP-36:Modularization-IndependentIntegrations > > > > >>> > > > > >>> Regards, > > > > >>> Saikat > > > > >>> > > > > >>> > > > > >>> On Fri, Oct 18, 2019 at 9:44 PM Saikat Maitra < > > > saikat.mai...@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-Streamer-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 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 > > > > >>> > > > > > >>> > > > > >> > > > > > > > > > >
