Re: Next steps for Mesos

Hi Alexander, Thanks for your mail and happy to know you are also using Mesos. So my question is, is there an option to lift the requirement of 3 active > contributors for the specific case of Mesos and postpone the decision > on moving this project to the attic? I think we may not be able to

Re: Next steps for Mesos

Hi Alexander, It seams not so easy (almost impossible) to maintain Mesos with a small group of peoples under Apache. Thats why I decide to create a fork of Mesos (https://github.com/m3scluster/clusterd). Have a look into the changelog. Maybe some changes are interesting for you. You (and of

Re: Next steps for Mesos

Hello. Except M3S, do we have K8S distro as Mesos frameworks? On Fri, Nov 10, 2023, 13:32 Alexander Sibiryakov wrote: > Hi Qian and others, > > We're also Mesos user, having 4-5 clusters of Mesos, running 1.4.1. > Some of them are powering our Scrapy Cloud product using 3K CPUs, > around 6-10K

RE: Next steps for Mesos

Hi Qian and others, We're also Mesos user, having 4-5 clusters of Mesos, running 1.4.1. Some of them are powering our Scrapy Cloud product using 3K CPUs, around 6-10K jobs executing in parallel, and several hundreds starting per second. I think the situation with Mesos is that its purpose have

Re: Next steps for Mesos

> > Qian, it might be worth having a more explicit email asking users to chime > in as this email was tailored more for contributors. Yes, we can have such email, but I think it does not affect whether we should move Mesos to attic or not, since the most important factor is whether we have

RE: Next steps for Mesos

Hello everyone, At Institutional Shareholder Services we just rolled out additional Mesos clusters in two of our data-centers. Those are based on Mesos 1.11.0 running on Debian 11 (using cgroups v1). Obviously I personally would like to see the community grow again, and also more than happy

Re: Next steps for Mesos

From: Benjamin Mahler Sent: Monday, March 20, 2023 2:55 PM To: user@mesos.apache.org Cc: mesos ; 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

Re: Next steps for Mesos

Hi, as you know Qian, I'm still on board.  Andreas On 18.03.23 02:57, Qian Zhang 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

Re: Re: Next steps for Mesos

...@mesos.apache.org Subject: [BULK]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

RE: Next steps for Mesos

@mesos.apache.org Cc : mesos ; priv...@mesos.apache.org Objet : 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

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

Next steps for Mesos

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

Re: Next Steps

> > > How many man hours where spend on mesos in 2020, 2019 and 2018? > > Roughly 5-6 ppl (in 2020),10-11 (in 2019), 16-18 (in 2018)

RE: Next Steps

> > Most existing PMC members who have chimed in so far seemed to be in > favor of moving the project to Attic. The exception is Qian (who is > willing to step up to be the new PMC chair, thanks Qian!). The main > argument for this seems to be that it'll be hard to re-activate the > project at

Re: Next Steps

tionned before, > happy to contribute. > But yeah, need a plan of action :p > > > >> > >> Br, > >> > >> Thomas > >> > >> - > >> > >> From: Grégoire Seux > >> Sent: Friday, 26 February 2021

Re: Next Steps

- From: Grégoire Seux Sent: Friday, 26 February 2021 11:12 To: priv...@mesos.apache.org ; dev ; user Subject: Re: Next Steps Hello all, here at Criteo, we heavily use Mesos and plan to do so for a foreseeable future alongside other alternatives. I am ok to become committer and help

Re: Next Steps

t; d...@mesos.apache.org>; user > *Subject:* Re: Next Steps > > Hello all, > > here at Criteo, we heavily use Mesos and plan to do so for a foreseeable > future alongside other alternatives. > I am ok to become committer and help the project if you are looking for > c

Re: Next Steps

: Friday, 26 February 2021 11:12 To: priv...@mesos.apache.org ; dev ; user Subject: Re: Next Steps Hello all, here at Criteo, we heavily use Mesos and plan to do so for a foreseeable future alongside other alternatives. I am ok to become committer and help the project if you are looking

Re: Next Steps

Hello all, here at Criteo, we heavily use Mesos and plan to do so for a foreseeable future alongside other alternatives. I am ok to become committer and help the project if you are looking for contributors. It seems finding committers will be doable but finding a PMC chair will be difficult.

Re: Next Steps

I'm thinking we can create a document in the http://mesos.apache.org/documentation/latest/design-docs/ section (Drive document) as a central point for discussing the roadmap and future of a new Mesos era. A lot of interesting things we can do, I have IMHO interesting ideas regarding Mesos and

Re: Next Steps

Good to see some interest in helping with project maintenance. Qian can you start a new email about figuring out the roadmap for the project? Thanks, Vinod > On Feb 18, 2021, at 11:18 AM, Charles-François Natali > wrote: > > Speaking as someone who contributed a few patches and would like

RE: Next Steps

- Sent: 18 February 2021 21:09 To: user@mesos.apache.org Subject: Re: Next Steps Some perspective from someone who went through something similar with Apache Aurora: It's not as simple as electing new committers. It takes time to develop the trust needed to add new members to the PMC, and that's

Re: Next Steps

Hello old friends. Long time no hear. +1 (binding) Haven't written that in a while... I also think moving it to the attic (as far as Apache is concerned) makes a lot of sense. It can have a life of its own on github (without the overhead of Apache PMC, requirements for voting, etc.) Kevin Am

Re: Next Steps

+1 to what Renan (and Benjamin) suggested.

Re: Next Steps

Some perspective from someone who went through something similar with Apache Aurora: It's not as simple as electing new committers. It takes time to develop the trust needed to add new members to the PMC, and that's the most important aspect of keeping the project going under Apache (my

Re: Next Steps

I think we can elect new committers. Currently we have 49 but most of them have left the project long ago. https://projects.apache.org/committee.html?mesos czw., 18 lut 2021 o 18:18 Charles-François Natali napisał(a): > Speaking as someone who contributed a few patches and would like to get >

Re: Next Steps

Speaking as someone who contributed a few patches and would like to get more involved, I find it a bit difficult to get MRs reviewed and merged. I think it's probably because the current committers have other priorities now that D2iQ focus has shifted, which is understandable but makes it harder

Re: Next Steps

Hi Vinod, I am still interested in the project. As other folks said, we need to have a direction for the project. I think there are still a lot of Mesos users/customers in the mail list, can you please send another mail to collect their requirements / pain points on Mesos, and then we can try to

Re: Next Steps

IIUC, Attic is not intended for projects which still have active users and thus might be in need of fixing bugs. Key items about moving project to Attic: > It is not intended to: > - Rebuild community > - Make bugfixes > - Make releases >Projects whose PMC are unable to muster 3 votes for a

Re: Next Steps

Thanks Tomek, that's what I suspected. It would therefore make it much more difficult for anyone to carry on since it would effectively have to be a fork, etc. I think it'd be a bit of a shame, but I understand Benjamin's point. I hope it can be avoided. Cheers, On Thu, 18 Feb 2021, 11:02

Re: Next Steps

Moving to attic is making project read only https://attic.apache.org/ https://attic.apache.org/projects/aurora.html czw., 18 lut 2021, 11:56 użytkownik Charles-François Natali < cf.nat...@gmail.com> napisał: > I'm not familiar with the attic but would it still allow to actually > develop, make

Re: Next Steps

I'm not familiar with the attic but would it still allow to actually develop, make commits to the repository etc? On Thu, 18 Feb 2021, 08:27 Benjamin Bannier, wrote: > Hi Vinod, > > > I would like to start a discussion around the future of the Mesos > project. > > > > As you are probably

Re: Next Steps

Hi Vinod, > I would like to start a discussion around the future of the Mesos project. > > As you are probably aware, the number of active committers and contributors > to the project have declined significantly over time. As of today, there's > no active development of any features or a public

Re: Next Steps

Hi, We're using Mesos at work, and are very happy with it. I'd be interested in becoming a committer. I could probably get some other colleagues interested as well but from a diversification point of view it'd probably be better if more individuals/organisations got involved. Happy to discuss

Re: Next Steps

On 2021-02-18 09:08 AM, Samuel Marks wrote: Mesos is great… conceptually. In practice it requires a lot of work to setup and keep running. What my team tried to contribute was a replacement for some of the big moving parts—namely Apache ZooKeeper—with a choice between etcd, Consul, and

Next Steps

Hi folks, I would like to start a discussion around the future of the Mesos project. As you are probably aware, the number of active committers and contributors to the project have declined significantly over time. As of today, there's no active development of any features or a public release