Just so you are aware, it is completely feasible to fork the project to continue work on it outside of Apache, if you decide on retirement. We generally don't even pursue naming issues for former podlings, since we would have not done anything to claim the TM.
Maybe it is possible to build up the project outside of apache with just a couple of committers and roll your own releases. Build up a strong enough community and come back (if it makes sense). John On 2017-11-06 14:56, Santosh Marella <mare...@gmail.com> wrote: > Agree with Darin and Mohit. I think the project is still very relevant, but > there is no one actively working on it - I myself couldn't put time on it > as the problem space my employer operates in is very different from > Myriad's. If Mohit is willing to drive the future features and Darin is > ready to back him up, I honestly think this deserves another shot. We have > already seen other folks expressing interest to offer support (in terms of > code reviews, vetting releases etc). > > Thanks, > Santosh. > > On Mon, Nov 6, 2017 at 11:45 AM, Darin Johnson <dbjohnson1...@gmail.com> > wrote: > > > I certainly think the project is relevant but I'm concerned if it belongs > > in Apache. When I was active it was difficult to get people to review pull > > requests and when releasing v0.2.0 it was hard to even get people to vote > > for a release. If only a few people are going to work on it, maybe it's > > easier to develop outside the incubator until there's something stable? > > > > I'd be interested in potentially working on it again provided there's at > > least two other people actively working on it. > > > > Darin > > > > On Mon, Nov 6, 2017 at 1:13 PM, mohit soni <mohitsoni1...@gmail.com> > > wrote: > > > > > The project's core idea of dynamic creation and management of YARN > > clusters > > > without creating static partitions is still relevant. This project and > > it's > > > community were one of the first movers in the still developing space of > > > stateful containerized distributed systems. > > > > > > I believe the project is currently lagging behind the fast paced > > > development of Apache Mesos ecosystem project and is currently not > > designed > > > to take advantage of the fast growing Kubernetes (Apache License 2.0) > > > ecosystem. > > > > > > I also believe the project is not just about the code which gets old once > > > it's written, unless tendered and cared for regularly, it's also about > > the > > > community, and the mindshare. > > > > > > Here are the things that we can do to bring life to the project again: > > > 1. Refactor the project codebase to take advantage of the advances in the > > > Apache Mesos Ecosystem, which from my direct experience, will simplify > > the > > > project codebase a lot, making it easier once again to maintain it, while > > > making it more relevant to the Apache Mesos community again. > > > 2. Extend the project to take advantage of Kubernetes project's and > > enable > > > dynamic creation and management of YARN clusters on Kubernetes. > > Kubernetes > > > project now has great support for building stateful containerized > > > applications. Refactoring work in Step #1 will lay the groundwork that > > will > > > make it easier to extend the project for the Kubernetes ecosystem. > > > > > > I'm happy to take a lead to drive both above initiatives, and can post a > > > detailed plan and design for accomplishing above in coming months. I am > > > also happy to take a lead on submitting monthly incubator reports. > > > > > > I truly believe that we should give the project one more chance to > > > recuperate and thrive. > > > > > > Best > > > Mohit > > > > > > > > > On Mon, Nov 6, 2017 at 5:06 AM, John D. Ament <johndam...@apache.org> > > > wrote: > > > > > > > Just to be clear, this is a discussion thread. Not a vote thread. > > While > > > > I believe many people vote +1 because they feel its clear why, when you > > > > vote against the idea you should explain why. > > > > > > > > So please, treat this more like a discussion rather than a vote and > > > > explain why. > > > > > > > > On 2017-11-05 13:50, mohit soni <mohitsoni1...@gmail.com> wrote: > > > > > -1 vote to not retire the project (committer, PMC) > > > > > > > > > > I believe the project is still relevant. > > > > > > > > > > On Sun, Nov 5, 2017 at 8:48 AM, Niels Basjes <ni...@basjes.nl> > > wrote: > > > > > > > > > > > +1 vote to retire (non-committer) > > > > > > > > > > > > On Sun, Nov 5, 2017 at 3:16 PM, Brandon Gulla < > > > gulla.bran...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > +1 vote to retire (non-committer) > > > > > > > > > > > > > > On Sun, Nov 5, 2017 at 9:03 AM, John D. Ament < > > > johndam...@apache.org > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > All, > > > > > > > > > > > > > > > > Based on the current state of Myriad and prior discussions I'd > > > > like to > > > > > > > > start the discussions around retiring the project. > > > > > > > > > > > > > > > > John > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Brandon > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best regards / Met vriendelijke groeten, > > > > > > > > > > > > Niels Basjes > > > > > > > > > > > > > > > > > > > > >
