Hi Rich, Thanks for chiming in and providing your perspective.
Charles already did a great job summarizing some of the current sentiments in the community above. I wanted to add a couple more points based on my discussions with folks in the community and PMC. Yes, there are some folks who are still interested in making some (minor) contributions but for that they just need a single repo to collaborate on. ASF has been a great home and steward for the Mesos project, but at this stage in its lifecycle, Mesos project could actually benefit from an ultra lightweight process and collaboration model. A public GitHub repo with requisite permissions for collaborators would serve these purposes well compared to the ASF process (PMC, voting, board reports etc). As an aside, would the ASF Board have any issue with the community forking the project and collaborating at https://github.com/mesos/mesos ? Thanks, Vinod On Tue, Apr 6, 2021 at 9:01 PM Samuel Marks <sam...@offscale.io> wrote: > Who runs this one? https://github.com/mesos > > Samuel Marks > Charity <https://sydneyscientific.org> | consultancy <https://offscale.io> > | open-source <https://github.com/offscale> | LinkedIn > <https://linkedin.com/in/samuelmarks> > > > On Wed, Apr 7, 2021 at 11:42 AM Charles-François Natali < > cf.nat...@gmail.com> > wrote: > > > Hi Rich, > > > > FWIW, I'm one of those people who said they were interested, and I > > still voted to move it to the attic (even though my vote is non > > binding as I'm not a committer). > > > > Initially I also thought that we could try to revive it within the > > ASF, but it quickly became clear that *none* of the current committers > > is willing to go down that route, i.e. put in the effort needed to > > onboard new committers. And without that, there's just no way forward. > > Various people voiced other concerns as well, such as viability of the > > project when other alternatives like Kubernetes exist, lack of clear > > technical direction for the future, etc. > > While they're relevant questions, I think currently they don't really > > make sense since the current Mesos community is basically dead. > > Finally, I think that the project should be moved to the Attic de > > facto because AFAICT the Apache rules require at least 3 *active* > > committers, and that's definitely not the case. > > > > However I still do believe in the project for the reasons I outlined > > in some of the previous threads, and I'm still interested in > > contributing: I just think that the current structure of the project > > is not suited for that anymore. And to be honest, I just want to move > > on, I'm tired of those endless discussions - it's been almost 2 months > > since the first thread stared, and nothing happened. > > > > It's a shame that we won't be able to continue using > > https://github.com/apache/mesos though, as it creates a much higher > > barrier to continuing the project. > > > > However if that's really not possible, then I guess that leaves no > > other option: once the vote has passed, I guess I'll start a final > > thread to gather people who'd be interested to create a new project > > forked off master on github, so we can start from scratch with our own > > repository, bug tracker etc. I hope those people who said they're > > actually interested will be willing to take an active part. > > > > Cheers, > > > > Charles > > > > > > > > > > > > Le mer. 7 avr. 2021 à 02:50, Rich Bowen <rbo...@apache.org> a écrit : > > > > > > I hope y'all can forgive me for sticking my nose in, as a concerned > > member. Color me confused by this vote. > > > > > > A month ago, on this same list - > > > https://lists.apache.org/thread.html/r307db648e201182fcf39b0de63ba224b94965501e20e6cbcecc085e4%40%3Cdev.mesos.apache.org%3E > > - Qian asked who was still interested in keeping the project going. SIX > > people responded that, given the chance, they'd step up and keep it > going. > > > > > > Around that same time - > > > https://lists.apache.org/thread.html/raed89cc5ab78531c48f56aa1989e1e7eb05f89a6941e38e9bc8803ff%40%3Cdev.mesos.apache.org%3E > > - Vinod observed that the too-high barrier to granting committer rights > has > > been a major factor in the slowdown of the project. > > > > > > And yet, y'all are voting to attic the project. > > > > > > So, again, it's not my project, and I don't have a vote here, but the > > reason the Board asks projects to have these attic conversations on the > Dev > > list is *specifically* so that interested people can say, hey, don't > attic > > it, we'll take it from here. Which six people, plus Qian, have done. > > > > > > Maybe it's time to lower the barrier to entry, and let these willing > > people take the project forward, do so. The Board can work out the picky > > little details of re-forming the PMC, if that's a difficulty. > > > > > > > > >
