Re: *****SPAM***** Re: State of the Project
Hey, Could we please try to stay on topic? Thanks, On Mon, 31 May 2021, 20:55 Zahoor, wrote: > hmmm... Ethereum has a popular client in golang and attracts many rookie > developers every day. > But still one of the most complex and nicely maintained software on Earth. > > On Mon, May 31, 2021 at 7:08 PM Marc wrote: > >> > >> > Better to rewrite/redesign Mesos with a more popular language (like >> > golang) to attract more developers. >> > Just a mind voice. >> > >> > ../Zahoor >> >> H, I would argue exactly the opposite. >> Going to these easier entry level languages attracts rookies coders and >> rookie thinking. I have seen some really weird design and errors in >> csi-ceph and influx. >> > > > -- > ./zahoor > > Web: http://zahoor.in > Twit: @jmohamedzahoor >
Re: *****SPAM***** Re: State of the Project
hmmm... Ethereum has a popular client in golang and attracts many rookie developers every day. But still one of the most complex and nicely maintained software on Earth. On Mon, May 31, 2021 at 7:08 PM Marc wrote: > > > > Better to rewrite/redesign Mesos with a more popular language (like > > golang) to attract more developers. > > Just a mind voice. > > > > ../Zahoor > > H, I would argue exactly the opposite. > Going to these easier entry level languages attracts rookies coders and > rookie thinking. I have seen some really weird design and errors in > csi-ceph and influx. > -- ./zahoor Web: http://zahoor.in Twit: @jmohamedzahoor
RE: *****SPAM***** Re: State of the Project
> > Better to rewrite/redesign Mesos with a more popular language (like > golang) to attract more developers. > Just a mind voice. > > ../Zahoor H, I would argue exactly the opposite. Going to these easier entry level languages attracts rookies coders and rookie thinking. I have seen some really weird design and errors in csi-ceph and influx.
Re: State of the Project
> > Yes I think it's important to mention, in response to Javi's point, > that one doesn't need to be an hard-core C++ dev to contribute. Exactly! To be honest I did not have much C++ programming experience when I started to contribute to Mesos. But when I read Mesos code, I felt it's easy to understand and has very good design. Although Mesos is running in multi-thread mode, you actually do not need to take care of the locking/race condition in most cases (thanks to the actor mode with libprocess). So I'd encourage everyone to read Mesos code and let us know which area you'd like to contribute to :) Regards, Qian Zhang On Mon, May 31, 2021 at 3:08 AM Charles-François Natali wrote: > Le dim. 30 mai 2021 à 16:09, Qian Zhang a écrit : > > [...] So given the > > active committers and contributors that we have in the community, I do > not > > think we can do anything big in the short term, instead we should do > small > > things to gradually activate the community. Here are what in my mind: > > 1. Review and merge the outstanding PRs. > > 2. Review the tickets in JIRA and select some high priority ones to work > on. > > 3. Add at least one new committer. > > Yes I think it's important to mention, in response to Javi's point, > that one doesn't need to be an hard-core C++ dev to contribute. > The code base is actually very clean and easy to read, the main > problem is the use of libprocess/actor model which takes some getting > used to, especially for people who're more used to a reactor, green > thread, etc models. The libprocess doc [1] gives a good overview. The > stout doc [2] is also worth a read although nothing surprising about > its design. > > But in any case I think there's a lot of valuable work which doesn't > require any C++, for example as Qian mentions going through the huge > backlog of JIRA issues. > I know it doesn't sound like the most exciting thing but it would > actually help a lot to do some triage, try to reproduce bugs, close > stale tickets, respond to user questions etc. > > I remember seeing a few other people answering Qian's call for > contributors a couple months ago [3], it'd be great if they could > reach out if they're still interested - if not it's fine, I know we're > all busy with our lives :). > > Cheers, > > Charles > > > [1] https://github.com/apache/mesos/tree/master/3rdparty/libprocess > [2] https://github.com/apache/mesos/tree/master/3rdparty/stout > [3] > https://mail-archives.apache.org/mod_mbox/mesos-dev/202103.mbox/%3CCABY6VOb%3DT8VxehVaS1YBrC5_odEwKhZzj3R4o3b-ykCytDw3JA%40mail.gmail.com%3E > > > > > > Please let me know for any comments / suggestions, thanks! > > > > > > Regards, > > Qian Zhang > > > > > > On Sun, May 30, 2021 at 7:59 PM Zahoor wrote: > > > > > Hi > > > > > > Better to rewrite/redesign Mesos with a more popular language (like > > > golang) to attract more developers. > > > Just a mind voice. > > > > > > ../Zahoor > > > > > > > > > On Sun, May 30, 2021 at 4:08 PM Javi Roman > > > wrote: > > > > > >> Totally agree that the main problem with this project is trying to > > >> increase the developer community. > > >> > > >> From my point of view, attracting new developers to a project of this > > >> complexity is difficult (C++ low level developers, creating Java and > Python > > >> bindings is not easy). However, if we try to broaden the objectives > of the > > >> project we may be able to attract other developers (not only C++ > > >> developers) who can help. > > >> > > >> One idea I have always had is to incorporate the concept and > technology > > >> of D2IQ DC/OS [1], in this way we would continue the abandoned work > of D2IQ > > >> by extending Apache Mesos to a more user-friendly technology and > broaden > > >> the base of developers with interest in (ReactJS, Go, Scala, > databases). > > >> > > >> I would be interested in contributing in this line, being able to > apply > > >> my knowledge in other areas, beyond C++ (which unfortunately I am not > > >> proficient in). > > >> > > >> [1] https://github.com/dcos > > >> -- > > >> Javi Roman > > >> > > >> Twitter: @javiromanrh > > >> GitHub: github.com/javiroman > > >> Linkedin: es.linkedin.com/in/javiroman > > >> Big Data Blog: dataintensive.info > > >> > > >> > > >> On Sat, May 29, 2021 at 12:47 PM Charles-François Natali < > > >> cf.nat...@gmail.com> wrote: > > >> > > >>> Hi Renan, > > >>> > > >>> > Renaming the topic because apparently we need to have this > discussion > > >>> again. > > >>> > > >>> Thanks for bringing this up again, because it is indeed still a > problem. > > >>> > > >>> > Therefore, the PMC *must* add members or the project *will* > fizzle out > > >>> > and die. > > >>> > > > >>> > I'd also be curious to see if we even have enough PMC members to > form a > > >>> > quorum at the moment as I only see Andrei Sekretenko reviewing pull > > >>> > requests on Github and the new chair Qian Zhang on emails. The > project > > >>> > needs three PMC members for the project to
Re: State of the Project
Le dim. 30 mai 2021 à 16:09, Qian Zhang a écrit : > [...] So given the > active committers and contributors that we have in the community, I do not > think we can do anything big in the short term, instead we should do small > things to gradually activate the community. Here are what in my mind: > 1. Review and merge the outstanding PRs. > 2. Review the tickets in JIRA and select some high priority ones to work on. > 3. Add at least one new committer. Yes I think it's important to mention, in response to Javi's point, that one doesn't need to be an hard-core C++ dev to contribute. The code base is actually very clean and easy to read, the main problem is the use of libprocess/actor model which takes some getting used to, especially for people who're more used to a reactor, green thread, etc models. The libprocess doc [1] gives a good overview. The stout doc [2] is also worth a read although nothing surprising about its design. But in any case I think there's a lot of valuable work which doesn't require any C++, for example as Qian mentions going through the huge backlog of JIRA issues. I know it doesn't sound like the most exciting thing but it would actually help a lot to do some triage, try to reproduce bugs, close stale tickets, respond to user questions etc. I remember seeing a few other people answering Qian's call for contributors a couple months ago [3], it'd be great if they could reach out if they're still interested - if not it's fine, I know we're all busy with our lives :). Cheers, Charles [1] https://github.com/apache/mesos/tree/master/3rdparty/libprocess [2] https://github.com/apache/mesos/tree/master/3rdparty/stout [3] https://mail-archives.apache.org/mod_mbox/mesos-dev/202103.mbox/%3CCABY6VOb%3DT8VxehVaS1YBrC5_odEwKhZzj3R4o3b-ykCytDw3JA%40mail.gmail.com%3E > > Please let me know for any comments / suggestions, thanks! > > > Regards, > Qian Zhang > > > On Sun, May 30, 2021 at 7:59 PM Zahoor wrote: > > > Hi > > > > Better to rewrite/redesign Mesos with a more popular language (like > > golang) to attract more developers. > > Just a mind voice. > > > > ../Zahoor > > > > > > On Sun, May 30, 2021 at 4:08 PM Javi Roman > > wrote: > > > >> Totally agree that the main problem with this project is trying to > >> increase the developer community. > >> > >> From my point of view, attracting new developers to a project of this > >> complexity is difficult (C++ low level developers, creating Java and Python > >> bindings is not easy). However, if we try to broaden the objectives of the > >> project we may be able to attract other developers (not only C++ > >> developers) who can help. > >> > >> One idea I have always had is to incorporate the concept and technology > >> of D2IQ DC/OS [1], in this way we would continue the abandoned work of D2IQ > >> by extending Apache Mesos to a more user-friendly technology and broaden > >> the base of developers with interest in (ReactJS, Go, Scala, databases). > >> > >> I would be interested in contributing in this line, being able to apply > >> my knowledge in other areas, beyond C++ (which unfortunately I am not > >> proficient in). > >> > >> [1] https://github.com/dcos > >> -- > >> Javi Roman > >> > >> Twitter: @javiromanrh > >> GitHub: github.com/javiroman > >> Linkedin: es.linkedin.com/in/javiroman > >> Big Data Blog: dataintensive.info > >> > >> > >> On Sat, May 29, 2021 at 12:47 PM Charles-François Natali < > >> cf.nat...@gmail.com> wrote: > >> > >>> Hi Renan, > >>> > >>> > Renaming the topic because apparently we need to have this discussion > >>> again. > >>> > >>> Thanks for bringing this up again, because it is indeed still a problem. > >>> > >>> > Therefore, the PMC *must* add members or the project *will* fizzle out > >>> > and die. > >>> > > >>> > I'd also be curious to see if we even have enough PMC members to form a > >>> > quorum at the moment as I only see Andrei Sekretenko reviewing pull > >>> > requests on Github and the new chair Qian Zhang on emails. The project > >>> > needs three PMC members for the project to be considered in a good > >>> state > >>> > according to the Apache guidelines [0]. > >>> > > >>> > >>> I must say I'm also a bit confused. > >>> The new project chair was elected exactly a month ago [1]. > >>> Since then, the only thing I have seen - there might be more going on > >>> being the scenes - is a single thread calling for input on new > >>> technical direction [2], which as several people mentioned before is > >>> not the most important issue the project is facing right now. > >>> As far as I can tell, nothing as been done by the PMC/project chair to > >>> address the more fundamental issue of the health of the community. > >>> Now, Andrei has been doing a great job at reviewing MRs, but as > >>> mentioned before he only has so much time available, and the project > >>> can't have only one active committer. > >>> So it would be good to hear from the project chair what they are > >>> planning to do, if
Re: State of the Project
Sorry for the late response, I was just back from a business trip and started reviewing the PRs. I think the current state is, from the PMC side, Andrei S and I can do the reviews (and maybe Andrei B and Ben Mahler as well?), and Charles and Andreas are doing code contributions (thank you!). So given the active committers and contributors that we have in the community, I do not think we can do anything big in the short term, instead we should do small things to gradually activate the community. Here are what in my mind: 1. Review and merge the outstanding PRs. 2. Review the tickets in JIRA and select some high priority ones to work on. 3. Add at least one new committer. Please let me know for any comments / suggestions, thanks! Regards, Qian Zhang On Sun, May 30, 2021 at 7:59 PM Zahoor wrote: > Hi > > Better to rewrite/redesign Mesos with a more popular language (like > golang) to attract more developers. > Just a mind voice. > > ../Zahoor > > > On Sun, May 30, 2021 at 4:08 PM Javi Roman > wrote: > >> Totally agree that the main problem with this project is trying to >> increase the developer community. >> >> From my point of view, attracting new developers to a project of this >> complexity is difficult (C++ low level developers, creating Java and Python >> bindings is not easy). However, if we try to broaden the objectives of the >> project we may be able to attract other developers (not only C++ >> developers) who can help. >> >> One idea I have always had is to incorporate the concept and technology >> of D2IQ DC/OS [1], in this way we would continue the abandoned work of D2IQ >> by extending Apache Mesos to a more user-friendly technology and broaden >> the base of developers with interest in (ReactJS, Go, Scala, databases). >> >> I would be interested in contributing in this line, being able to apply >> my knowledge in other areas, beyond C++ (which unfortunately I am not >> proficient in). >> >> [1] https://github.com/dcos >> -- >> Javi Roman >> >> Twitter: @javiromanrh >> GitHub: github.com/javiroman >> Linkedin: es.linkedin.com/in/javiroman >> Big Data Blog: dataintensive.info >> >> >> On Sat, May 29, 2021 at 12:47 PM Charles-François Natali < >> cf.nat...@gmail.com> wrote: >> >>> Hi Renan, >>> >>> > Renaming the topic because apparently we need to have this discussion >>> again. >>> >>> Thanks for bringing this up again, because it is indeed still a problem. >>> >>> > Therefore, the PMC *must* add members or the project *will* fizzle out >>> > and die. >>> > >>> > I'd also be curious to see if we even have enough PMC members to form a >>> > quorum at the moment as I only see Andrei Sekretenko reviewing pull >>> > requests on Github and the new chair Qian Zhang on emails. The project >>> > needs three PMC members for the project to be considered in a good >>> state >>> > according to the Apache guidelines [0]. >>> > >>> >>> I must say I'm also a bit confused. >>> The new project chair was elected exactly a month ago [1]. >>> Since then, the only thing I have seen - there might be more going on >>> being the scenes - is a single thread calling for input on new >>> technical direction [2], which as several people mentioned before is >>> not the most important issue the project is facing right now. >>> As far as I can tell, nothing as been done by the PMC/project chair to >>> address the more fundamental issue of the health of the community. >>> Now, Andrei has been doing a great job at reviewing MRs, but as >>> mentioned before he only has so much time available, and the project >>> can't have only one active committer. >>> So it would be good to hear from the project chair what they are >>> planning to do, if anything, to address this situation. >>> From some private conversations I know that they have been busy with >>> other obligations in the past month so maybe it's only a bad timing >>> and just a transient state, however I don't think it's viable to >>> continue if even the project chair doesn't have any time to dedicate >>> to the project - not even replying to this thread. >>> >>> > At this point I suggest the PMC does a roll call and get Apche board >>> > members involved so that they can be aware of the situation. >>> >>> I'm not familiar with the ASF but yes it does sounds like a possible >>> course of action? >>> >>> Cheers, >>> >>> Charles >>> >>> >>> >>> [1] >>> https://mail-archives.apache.org/mod_mbox/mesos-dev/202104.mbox/%3CCAE0xwObaHPiSFM3KrY1SL--E864L48o_LF2E7PP2%3DUu3rk99gQ%40mail.gmail.com%3E >>> [2] >>> https://mail-archives.apache.org/mod_mbox/mesos-dev/202105.mbox/%3CCABY6VOaOxSp%2BeMJm_jSTdY%3DD5Qp%3DT%2B89Cvaxqw7GLbFYr1qzew%40mail.gmail.com%3E >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> > >>> > -Renan >>> > >>> > [0]https://www.apache.org/dev/pmc.html >>> > >>> > On 5/24/21 10:21 AM, Charles-François Natali wrote: >>> > > Hey, >>> > > >>> > > Le lun. 24 mai 2021 à 14:12, Qian Zhang a >>> écrit : >>> > >>> several fixing bugs which basically make Mesos unusable on
Re: State of the Project
Hi Better to rewrite/redesign Mesos with a more popular language (like golang) to attract more developers. Just a mind voice. ../Zahoor On Sun, May 30, 2021 at 4:08 PM Javi Roman wrote: > Totally agree that the main problem with this project is trying to > increase the developer community. > > From my point of view, attracting new developers to a project of this > complexity is difficult (C++ low level developers, creating Java and Python > bindings is not easy). However, if we try to broaden the objectives of the > project we may be able to attract other developers (not only C++ > developers) who can help. > > One idea I have always had is to incorporate the concept and technology of > D2IQ DC/OS [1], in this way we would continue the abandoned work of D2IQ by > extending Apache Mesos to a more user-friendly technology and broaden the > base of developers with interest in (ReactJS, Go, Scala, databases). > > I would be interested in contributing in this line, being able to apply my > knowledge in other areas, beyond C++ (which unfortunately I am not > proficient in). > > [1] https://github.com/dcos > -- > Javi Roman > > Twitter: @javiromanrh > GitHub: github.com/javiroman > Linkedin: es.linkedin.com/in/javiroman > Big Data Blog: dataintensive.info > > > On Sat, May 29, 2021 at 12:47 PM Charles-François Natali < > cf.nat...@gmail.com> wrote: > >> Hi Renan, >> >> > Renaming the topic because apparently we need to have this discussion >> again. >> >> Thanks for bringing this up again, because it is indeed still a problem. >> >> > Therefore, the PMC *must* add members or the project *will* fizzle out >> > and die. >> > >> > I'd also be curious to see if we even have enough PMC members to form a >> > quorum at the moment as I only see Andrei Sekretenko reviewing pull >> > requests on Github and the new chair Qian Zhang on emails. The project >> > needs three PMC members for the project to be considered in a good state >> > according to the Apache guidelines [0]. >> > >> >> I must say I'm also a bit confused. >> The new project chair was elected exactly a month ago [1]. >> Since then, the only thing I have seen - there might be more going on >> being the scenes - is a single thread calling for input on new >> technical direction [2], which as several people mentioned before is >> not the most important issue the project is facing right now. >> As far as I can tell, nothing as been done by the PMC/project chair to >> address the more fundamental issue of the health of the community. >> Now, Andrei has been doing a great job at reviewing MRs, but as >> mentioned before he only has so much time available, and the project >> can't have only one active committer. >> So it would be good to hear from the project chair what they are >> planning to do, if anything, to address this situation. >> From some private conversations I know that they have been busy with >> other obligations in the past month so maybe it's only a bad timing >> and just a transient state, however I don't think it's viable to >> continue if even the project chair doesn't have any time to dedicate >> to the project - not even replying to this thread. >> >> > At this point I suggest the PMC does a roll call and get Apche board >> > members involved so that they can be aware of the situation. >> >> I'm not familiar with the ASF but yes it does sounds like a possible >> course of action? >> >> Cheers, >> >> Charles >> >> >> >> [1] >> https://mail-archives.apache.org/mod_mbox/mesos-dev/202104.mbox/%3CCAE0xwObaHPiSFM3KrY1SL--E864L48o_LF2E7PP2%3DUu3rk99gQ%40mail.gmail.com%3E >> [2] >> https://mail-archives.apache.org/mod_mbox/mesos-dev/202105.mbox/%3CCABY6VOaOxSp%2BeMJm_jSTdY%3DD5Qp%3DT%2B89Cvaxqw7GLbFYr1qzew%40mail.gmail.com%3E >> >> >> >> >> >> >> >> >> >> > >> > -Renan >> > >> > [0]https://www.apache.org/dev/pmc.html >> > >> > On 5/24/21 10:21 AM, Charles-François Natali wrote: >> > > Hey, >> > > >> > > Le lun. 24 mai 2021 à 14:12, Qian Zhang a >> écrit : >> > >>> several fixing bugs which basically make Mesos unusable on a recent >> Linux >> > >> distro >> > >> Can you please elaborate a bit on this? Do you mean Mesos not >> working on a >> > >> recent Linux distro? If so, I think we can start to fix the issues >> and >> > >> maybe do a patch release for that. >> > > Yes, there are several issues on recent Linux distributions, e.g. >> > > Debian Bullseye: >> > > - https://github.com/apache/mesos/pull/387: compilaiton error, >> > > although it's only in master not in the last release >> > > - https://github.com/apache/mesos/pull/388: problem with the freezer >> > > cgroup based task killer which causes over a dozen test to fail and >> > > can leave the freezer frozen, tasks in uninterruptible state etc >> > > - https://github.com/apache/mesos/pull/384: problem parsing >> > > ld.so.cache which also breaks a lot of things >> > > >> > > You were tagged in some of this MRs, I tagged you in all of them, it'd >> > > be great if you could have a
Re: State of the Project
Totally agree that the main problem with this project is trying to increase the developer community. >From my point of view, attracting new developers to a project of this complexity is difficult (C++ low level developers, creating Java and Python bindings is not easy). However, if we try to broaden the objectives of the project we may be able to attract other developers (not only C++ developers) who can help. One idea I have always had is to incorporate the concept and technology of D2IQ DC/OS [1], in this way we would continue the abandoned work of D2IQ by extending Apache Mesos to a more user-friendly technology and broaden the base of developers with interest in (ReactJS, Go, Scala, databases). I would be interested in contributing in this line, being able to apply my knowledge in other areas, beyond C++ (which unfortunately I am not proficient in). [1] https://github.com/dcos -- Javi Roman Twitter: @javiromanrh GitHub: github.com/javiroman Linkedin: es.linkedin.com/in/javiroman Big Data Blog: dataintensive.info On Sat, May 29, 2021 at 12:47 PM Charles-François Natali < cf.nat...@gmail.com> wrote: > Hi Renan, > > > Renaming the topic because apparently we need to have this discussion > again. > > Thanks for bringing this up again, because it is indeed still a problem. > > > Therefore, the PMC *must* add members or the project *will* fizzle out > > and die. > > > > I'd also be curious to see if we even have enough PMC members to form a > > quorum at the moment as I only see Andrei Sekretenko reviewing pull > > requests on Github and the new chair Qian Zhang on emails. The project > > needs three PMC members for the project to be considered in a good state > > according to the Apache guidelines [0]. > > > > I must say I'm also a bit confused. > The new project chair was elected exactly a month ago [1]. > Since then, the only thing I have seen - there might be more going on > being the scenes - is a single thread calling for input on new > technical direction [2], which as several people mentioned before is > not the most important issue the project is facing right now. > As far as I can tell, nothing as been done by the PMC/project chair to > address the more fundamental issue of the health of the community. > Now, Andrei has been doing a great job at reviewing MRs, but as > mentioned before he only has so much time available, and the project > can't have only one active committer. > So it would be good to hear from the project chair what they are > planning to do, if anything, to address this situation. > From some private conversations I know that they have been busy with > other obligations in the past month so maybe it's only a bad timing > and just a transient state, however I don't think it's viable to > continue if even the project chair doesn't have any time to dedicate > to the project - not even replying to this thread. > > > At this point I suggest the PMC does a roll call and get Apche board > > members involved so that they can be aware of the situation. > > I'm not familiar with the ASF but yes it does sounds like a possible > course of action? > > Cheers, > > Charles > > > > [1] > https://mail-archives.apache.org/mod_mbox/mesos-dev/202104.mbox/%3CCAE0xwObaHPiSFM3KrY1SL--E864L48o_LF2E7PP2%3DUu3rk99gQ%40mail.gmail.com%3E > [2] > https://mail-archives.apache.org/mod_mbox/mesos-dev/202105.mbox/%3CCABY6VOaOxSp%2BeMJm_jSTdY%3DD5Qp%3DT%2B89Cvaxqw7GLbFYr1qzew%40mail.gmail.com%3E > > > > > > > > > > > > > -Renan > > > > [0]https://www.apache.org/dev/pmc.html > > > > On 5/24/21 10:21 AM, Charles-François Natali wrote: > > > Hey, > > > > > > Le lun. 24 mai 2021 à 14:12, Qian Zhang a écrit > : > > >>> several fixing bugs which basically make Mesos unusable on a recent > Linux > > >> distro > > >> Can you please elaborate a bit on this? Do you mean Mesos not working > on a > > >> recent Linux distro? If so, I think we can start to fix the issues and > > >> maybe do a patch release for that. > > > Yes, there are several issues on recent Linux distributions, e.g. > > > Debian Bullseye: > > > - https://github.com/apache/mesos/pull/387: compilaiton error, > > > although it's only in master not in the last release > > > - https://github.com/apache/mesos/pull/388: problem with the freezer > > > cgroup based task killer which causes over a dozen test to fail and > > > can leave the freezer frozen, tasks in uninterruptible state etc > > > - https://github.com/apache/mesos/pull/384: problem parsing > > > ld.so.cache which also breaks a lot of things > > > > > > You were tagged in some of this MRs, I tagged you in all of them, it'd > > > be great if you could have a look :). > > > > > > Cheers, > > > > > >> > > >> Regards, > > >> Qian Zhang > > >> > > >> > > >> On Fri, May 21, 2021 at 2:57 AM Charles-François Natali < > cf.nat...@gmail.com> > > >> wrote: > > >> > > >>> Hey, > > >>> > > >>> Sorry for being a killjoy and repeating myself, but as mentioned in > > >>> the past, I don't think that
Re: State of the Project
Hi Renan, > Renaming the topic because apparently we need to have this discussion again. Thanks for bringing this up again, because it is indeed still a problem. > Therefore, the PMC *must* add members or the project *will* fizzle out > and die. > > I'd also be curious to see if we even have enough PMC members to form a > quorum at the moment as I only see Andrei Sekretenko reviewing pull > requests on Github and the new chair Qian Zhang on emails. The project > needs three PMC members for the project to be considered in a good state > according to the Apache guidelines [0]. > I must say I'm also a bit confused. The new project chair was elected exactly a month ago [1]. Since then, the only thing I have seen - there might be more going on being the scenes - is a single thread calling for input on new technical direction [2], which as several people mentioned before is not the most important issue the project is facing right now. As far as I can tell, nothing as been done by the PMC/project chair to address the more fundamental issue of the health of the community. Now, Andrei has been doing a great job at reviewing MRs, but as mentioned before he only has so much time available, and the project can't have only one active committer. So it would be good to hear from the project chair what they are planning to do, if anything, to address this situation. >From some private conversations I know that they have been busy with other obligations in the past month so maybe it's only a bad timing and just a transient state, however I don't think it's viable to continue if even the project chair doesn't have any time to dedicate to the project - not even replying to this thread. > At this point I suggest the PMC does a roll call and get Apche board > members involved so that they can be aware of the situation. I'm not familiar with the ASF but yes it does sounds like a possible course of action? Cheers, Charles [1] https://mail-archives.apache.org/mod_mbox/mesos-dev/202104.mbox/%3CCAE0xwObaHPiSFM3KrY1SL--E864L48o_LF2E7PP2%3DUu3rk99gQ%40mail.gmail.com%3E [2] https://mail-archives.apache.org/mod_mbox/mesos-dev/202105.mbox/%3CCABY6VOaOxSp%2BeMJm_jSTdY%3DD5Qp%3DT%2B89Cvaxqw7GLbFYr1qzew%40mail.gmail.com%3E > > -Renan > > [0]https://www.apache.org/dev/pmc.html > > On 5/24/21 10:21 AM, Charles-François Natali wrote: > > Hey, > > > > Le lun. 24 mai 2021 à 14:12, Qian Zhang a écrit : > >>> several fixing bugs which basically make Mesos unusable on a recent Linux > >> distro > >> Can you please elaborate a bit on this? Do you mean Mesos not working on a > >> recent Linux distro? If so, I think we can start to fix the issues and > >> maybe do a patch release for that. > > Yes, there are several issues on recent Linux distributions, e.g. > > Debian Bullseye: > > - https://github.com/apache/mesos/pull/387: compilaiton error, > > although it's only in master not in the last release > > - https://github.com/apache/mesos/pull/388: problem with the freezer > > cgroup based task killer which causes over a dozen test to fail and > > can leave the freezer frozen, tasks in uninterruptible state etc > > - https://github.com/apache/mesos/pull/384: problem parsing > > ld.so.cache which also breaks a lot of things > > > > You were tagged in some of this MRs, I tagged you in all of them, it'd > > be great if you could have a look :). > > > > Cheers, > > > >> > >> Regards, > >> Qian Zhang > >> > >> > >> On Fri, May 21, 2021 at 2:57 AM Charles-François Natali > >> > >> wrote: > >> > >>> Hey, > >>> > >>> Sorry for being a killjoy and repeating myself, but as mentioned in > >>> the past, I don't think that technical direction is the most important > >>> problem right now - community is. > >>> Coming up with medium/long-term technical roadmap doesn't do much if > >>> there are no contributors to implement them, and users to use them. > >>> > >>> The following issues which have been brought up are still not resolved: > >>> - very few committers willing to review and merge MRs - currently only > >>> Andrei Sekretenko is doing that, and I'm sure he's busy with his day > >>> job so only has that much bandwidth > >>> - very few people contribute MRs and triage/address JIRA issues - > >>> AFAICT it's pretty much Andreas and me > >>> > >>> So I think the first thing to do would be to address those problems. > >>> Some suggestions which come to mind: > >>> - to the remaining committers who'd still like to salvage the project, > >>> please take some time to review and merge MRs - > >>> https://github.com/apache/mesos/pulls has a few open, several fixing > >>> bugs which basically make Mesos unusable on a recent Linux distro > >>> - to the various users who've said they were interested in keeping the > >>> project alive: start contributing. It doesn't have to be anything big, > >>> just get familiar with the code base: > >>>* start going through JIRA and triage bugs, closing invalid/stale > >>> ones, tackling small issues > >>>
