Re: Next steps for Mesos

[Stephen Salinas]

HubSpot is still also using mesos and I know we have at least 3 other
companies still using the open source version of our Singularity scheduler.
We are up to the 1.11.x release at this point. However, I don't know that
any of that crowd has been or will be active contributors.

-Stephen Salinas

On Mon, Mar 27, 2023 at 5:03 AM Qian Zhang  wrote:

> >
> > 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 enough active committers. Quoted from
> https://attic.apache.org/
> 
>
> When should a project move to the Attic?
>
> Projects whose PMC are unable to muster 3 votes for a release, who have no
> active committers or are unable to fulfill their reporting duties to the
> board are all good candidates for the Attic.
>
> I am happy to see there are still some companies using Mesos now, but in
> this mail thread, so far there are just several contributors interested in
> contributing to Mesos and only one committer Benjamin Mahler (no guaranteed
> time), I think that's not enough to keep this project going, so we may have
> to move Mesos to attic.
>
>
> Regards,
> Qian Zhang
>
>
> On Tue, Mar 21, 2023 at 2:56 AM Benjamin Mahler 
> wrote:
>
> > 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  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
> > >  
> >.
> > >
> > > 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
> > >
> >
>

Re: Next steps for Mesos

[Qian Zhang]

>
> 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 enough active committers. Quoted from
https://attic.apache.org/:

When should a project move to the Attic?

Projects whose PMC are unable to muster 3 votes for a release, who have no
active committers or are unable to fulfill their reporting duties to the
board are all good candidates for the Attic.

I am happy to see there are still some companies using Mesos now, but in
this mail thread, so far there are just several contributors interested in
contributing to Mesos and only one committer Benjamin Mahler (no guaranteed
time), I think that's not enough to keep this project going, so we may have
to move Mesos to attic.


Regards,
Qian Zhang


On Tue, Mar 21, 2023 at 2:56 AM Benjamin Mahler  wrote:

> 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  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
> > .
> >
> > 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
> >
>

Re: Re: Next steps for Mesos

[Thomas Langé]

Hello,

Criteo is still an active user of Mesos, running it worldwide for most of its 
production workloads.

We currently run a fork of Mesos 1.9.x (with some patches that were not 
upstreamed but not that much), and we don't plan to upgrade to the latest 
version for now.

We will continue to propose patches regularly upstream when possible, but can't 
really commit on actively contributing on particular needs in Mesos ecosystem.

Regards,

Thomas Langé

From: Benjamin Mahler 
Sent: Monday, 20 March 2023 19:55
To: u...@mesos.apache.org 
Cc: mesos ; priv...@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 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 
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://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fattic.apache.org%2F&data=05%7C01%7Ct.lange%40criteo.com%7C6e782bd9b402421896d608db2974e0de%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C638149354183246959%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2QLjvfO3KRuvcwcZCEnFFwWGLaBz%2BIY7Yi2K%2Bw1Lm5A%3D&reserved=0>.

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

Re: Next steps for Mesos

[Benjamin Mahler]

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  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
> .
>
> 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
>

Re: Next steps for Mesos

[Andreas Peters]

Hi,

as you know, 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 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
.

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



--
AVENTER UG (haftungsbeschraenkt)
Köllner Chaussee 144
25337 Kölln-Reisiek

Phone: (+49)4121 - 235582 0
E-Mail: a...@aventer.biz
Internet: https://www.aventer.biz
Git: https://www.github.com/AVENTER-UG

Geschäftsführer/CEO: Andreas Peters
Unternehmenssitz/City: Kölln-Reisiek
Handelsregister beim Amtsgericht/Legal Court: Itzehoe
Handelsregister-Nummer/Company Registration Number: HRB 9995 PI


OpenPGP_0x6A83F12541CFCCF9.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Re: Next steps for Mesos

[Han Li]

Hi,
I'm very interested in maintaining Mesos and don't want such an excellent
project to end.
I have participated in the development of a resource scheduling system used
Mesos in a big data platform  (AlibabaCloud Dataphin) before.
And now I have quit my job and am preparing to go to graduate school now,
so I have much free time.
But I'm not particularly familiar with C++, so I would appreciate some help
from the community.

Qian Zhang  于2023年3月18日周六 09:57写道：

> 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
> .
>
> 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
>