We're using mesos 1.11 straight out of the box on ubuntu 18.04 at touchplan.io running our own bespoke framework. Would like to get it to ubuntu 22.04. We have limited resources to commit to mesos development, but it's not totally out of the question.
-Dan ________________________________ From: Benjamin Mahler <bmah...@apache.org> Sent: Monday, March 20, 2023 2:55 PM To: user@mesos.apache.org <user@mesos.apache.org> Cc: mesos <d...@mesos.apache.org>; priv...@mesos.apache.org <priv...@mesos.apache.org> Subject: Re: Next steps for Mesos Also if you are still a user of mesos, please chime in. Qian, it might be worth having a more explicit email asking users to chime in as this email was tailored more for contributors. Twitter is still using mesos heavily, we upgraded from a branch based off of 1.2.x to 1.9.x in 2021, but haven't upgraded to 1.11.x yet. We do have a lot of patches carried on our branch that have not been upstreamed. I would like to upstream them to avoid relying on many custom patches and to get closer to HEAD, but it will take time and quite a bit of work, and it's not a priority at the moment. On the contribution side, at this point if I were to continue contributing, it would be on a volunteer basis, and I can't guarantee having enough time to do so. On Fri, Mar 17, 2023 at 9:57 PM Qian Zhang <zhq527...@gmail.com<mailto:zhq527...@gmail.com>> wrote: Hi all, I'd like to restart the discussion around the future of the Mesos project. As you may already be aware, the Mesos community has been inactive for the last few years, there were only 3 contributors last year, that's obviously not enough to keep the project moving forward. I think we need at least 3 active committers/PMC members and some active contributors to keep the project alive, or we may have to move it to attic<https://attic.apache.org/>. Call for action: If you are the current committer/PMC member and still have the capacity to maintain the project, or if you are willing to actively contribute to the project as a contributor, please reply to this email, thanks! Regards, Qian Zhang
