Re: [RESULT][VOTE] Apache Tuweni graduation
Thanks Chris, Mea culpa. You’re right and I’m wrong and we’ll look into fixing the release process so PPMC only are binding. I will work with the project on its community. Cheers, Antoine > On Dec 22, 2022, at 12:57 AM, Christofer Dutz > wrote: > > Sooo … assuming we let Tuweni graduate, > > If you could only release with binding votes from the incubator. > How would you be able to release without it? > > Because technically as a TLP there is nowhere, where you could get those > missing votes. > > And if a project can’t release because there are too little PMC members able > to vote, that’s the direct path to the Attic. > > So please invest some time and effort into growing and engaging your > community. > Trust them with making changes and decisions. > Promote your project publicly and promote that people are welcome to come and > contribute. > Offer them to be their mentor for their first contributions. > > That’s my advice and happy to chat if you want some help with that all. > (Help like in guidance, not help, like in doing the work) > > Chris > > From: Antoine Toulme > Date: Thursday, 22. December 2022 at 08:48 > To: general > Subject: Re: [RESULT][VOTE] Apache Tuweni graduation > > >> On Dec 21, 2022, at 12:55 AM, Christofer Dutz >> wrote: >> >> Hi all, >> >> I still think just because a resolution is added that it doesn’t mean the >> board will accept it. >> >> Having barely 3 +1 votes also seems an indicator that the rest of the IPMC >> doesn’t clearly believe Tuweni is ready for graduation. >> The incubator is for projects to learn how to do things the Apache way and >> to grow its community into a sustainable project. >> I see that the first part seems to be done, but the second part is >> completely missing. >> >> I also don’t agree that being in the incubator will keep anyone from >> contributing, I even think that most people know that incubating projects >> are usually the ones easiest to get involved in. >> So I would like to bring the counter-argument to the table, that growing the >> community might become harder, once Tuweni is a TLP. >> >> The problem I see is perfectly reflected by this: >> https://github.com/apache/incubator-tuweni/graphs/contributors >> >> Has anyone besides you – Antoine – ever done a release? >> Also did I have a look at your last release thread: >> There you had exactly 3 +1 votes, however one of them was from “Danno >> Ferrin” who seems to “only” be a Committer. >> A PPMC +1 vote would have been required here, so technically this release >> wasn’t ok. > Because this release didn’t have enough votes, we moved it to the general > incubator list where it was duly voted. > >> >> I think this project should focus on building the community, having others >> be the Release Manager for one or two releases and then to aim for >> graduation. >> >> Maybe I should make my opinion a bit more explicit by officially voting -1 >> >> So here goes: >> >> -1 binding >> >> Chris >> >> >> From: Antoine Toulme >> Date: Wednesday, 21. December 2022 at 07:02 >> To: general >> Subject: [RESULT][VOTE] Apache Tuweni graduation >> Folks, >> >> Thank you for your participation in the Apache Tuweni graduation vote. >> >> The results are as follows: >> +1: 3 Antoine Toulme (binding), Larry Mccay (binding), Dave Fisher (binding) >> +0: 0 >> -1: 0 >> >> Thanks all! We will proceed to the next step of voting for a PMC chair and >> drafting a resolution for the board. >> >> Cheers, >> >> Antoine >> >>> On Dec 20, 2022, at 8:45 AM, Antoine Toulme wrote: >>> >>> I’ve let the vote go on for a bit. I’d like to make sure we get a chance >>> for final votes and comments and I will close it by tonight PT time. >>> >>> Cheers, >>> >>> Antoine >>> On Dec 19, 2022, at 6:45 AM, Josh Fischer wrote: To build on what Dave is saying (from my experience at least) is projects will enter the incubator and they tend to focus on building new features on top of new features. Instead of focusing on how they can transfer that deep knowledge of the system to anyone who is willing to learn. Getting those people to feel comfortable stepping up can be a challenge. Making new comers (whoever they are) feel welcome to ask questions and contribute on mailing list discussion, prs, code contributions, etc is the most important part of building a self-sustaining community. I’ll get off my soapbox now. - Josh On Mon, Dec 19, 2022 at 2:40 AM Christofer Dutz wrote: > Sorry for asking, > > but Dave, could you please explain that reply … admittedly I didn’t > understand what you wanted to say > (Guess I would consider it advanced English and I simply didn’t understand > it). > > Chris > > From: Dave Fisher > Date: Monday, 12. December 2022 at 06:19 > To: general@incubator.apache.org > Subject:
[VOTE] Release Apache SDAP (incubating) 1.0.0-rc2
Hello everyone, This is a call for a vote to release Apache SDAP (incubating) version 1.0.0-rc2. The Apache SDAP community has voted to approve release of Apache SDAP (incubating) version 1.0.0-rc2. We now request the Incubator PMC review and vote on this release. SDAP community vote thread: https://lists.apache.org/thread/6nmknw8n1flwsqp4n3cromnrck21xmh9 Instructions for building docker images from source can be found here: https://incubator-sdap-nexus.readthedocs.io/en/latest/build.html Instructions for deploying locally to test can be found here: https://incubator-sdap-nexus.readthedocs.io/en/latest/quickstart.html The tags to be voted on are 1.0.0-rc2: - nexusproto: - URL: https://github.com/apache/incubator-sdap-nexusproto/tree/1.0.0-rc2 - Commit: f3c726e69997436dd9ee6f9a993d4c95ee490b6f - ingester: - URL: https://github.com/apache/incubator-sdap-ingester/tree/1.0.0-rc2 - Commit: 2c8a9d35320f11a5db2534802f43366ddaff2fea - nexus: - URL: https://github.com/apache/incubator-sdap-nexus/tree/1.0.0-rc2 - Commit: f60e98331ac29b57ca40322f8f96e98a5c69e553 The release files, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/sdap/apache-sdap-1.0.0-rc2/ For verification, the hashes of the .tar.gz artifacts we are voting on are as follows: apache-sdap-ingester-1.0.0-src.tar.gz: db380c3002351e65ec3581a3ff0cacbb7092f46292b0a656a78a919e1409738442e845731050a2160a556a7818f22b2ab4bb6da437200bc0a62419332de49ad7 apache-sdap-nexus-1.0.0-src.tar.gz: da34e9830cf5126bac498180d7cdd95bc2cfc13535c7b4355ba51de64e3589a385a969e0cf1a89fa77e436b30c99a48abffab4b4ef03b23982aa33c2e83e8dbd apache-sdap-nexusproto-1.0.0-src.tar.gz: 05dc8e96d9c49207750c1da13f630493e8d08f5e68733742c157ac6c85ede29aca25f3c94cd706acbbe21cee41ebc052a880b4d6ce859bf510bcc2d66d8f88b2 Release artifacts are signed with the following key: https://keyserver.ubuntu.com/pks/lookup?op=get=0x4e98c4a32026656e14e0b570fc20035a010e3b7b Please vote on releasing this package as Apache SDAP (incubating) 1.0.0. The vote is open for 72 hours or until at least 3 “+1” PMC votes are cast and passes if at least 3 +1 PMC votes are cast. [ ] +1 Release this package as Apache SDAP (incubating) 1.0.0 [ ] +0 No opinion [ ] -1 Do not release this package because ... Thank you, Riley - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Apache Tuweni graduation
Sooo … assuming we let Tuweni graduate, If you could only release with binding votes from the incubator. How would you be able to release without it? Because technically as a TLP there is nowhere, where you could get those missing votes. And if a project can’t release because there are too little PMC members able to vote, that’s the direct path to the Attic. So please invest some time and effort into growing and engaging your community. Trust them with making changes and decisions. Promote your project publicly and promote that people are welcome to come and contribute. Offer them to be their mentor for their first contributions. That’s my advice and happy to chat if you want some help with that all. (Help like in guidance, not help, like in doing the work) Chris From: Antoine Toulme Date: Thursday, 22. December 2022 at 08:48 To: general Subject: Re: [RESULT][VOTE] Apache Tuweni graduation > On Dec 21, 2022, at 12:55 AM, Christofer Dutz > wrote: > > Hi all, > > I still think just because a resolution is added that it doesn’t mean the > board will accept it. > > Having barely 3 +1 votes also seems an indicator that the rest of the IPMC > doesn’t clearly believe Tuweni is ready for graduation. > The incubator is for projects to learn how to do things the Apache way and to > grow its community into a sustainable project. > I see that the first part seems to be done, but the second part is completely > missing. > > I also don’t agree that being in the incubator will keep anyone from > contributing, I even think that most people know that incubating projects are > usually the ones easiest to get involved in. > So I would like to bring the counter-argument to the table, that growing the > community might become harder, once Tuweni is a TLP. > > The problem I see is perfectly reflected by this: > https://github.com/apache/incubator-tuweni/graphs/contributors > > Has anyone besides you – Antoine – ever done a release? > Also did I have a look at your last release thread: > There you had exactly 3 +1 votes, however one of them was from “Danno Ferrin” > who seems to “only” be a Committer. > A PPMC +1 vote would have been required here, so technically this release > wasn’t ok. Because this release didn’t have enough votes, we moved it to the general incubator list where it was duly voted. > > I think this project should focus on building the community, having others be > the Release Manager for one or two releases and then to aim for graduation. > > Maybe I should make my opinion a bit more explicit by officially voting -1 > > So here goes: > > -1 binding > > Chris > > > From: Antoine Toulme > Date: Wednesday, 21. December 2022 at 07:02 > To: general > Subject: [RESULT][VOTE] Apache Tuweni graduation > Folks, > > Thank you for your participation in the Apache Tuweni graduation vote. > > The results are as follows: > +1: 3 Antoine Toulme (binding), Larry Mccay (binding), Dave Fisher (binding) > +0: 0 > -1: 0 > > Thanks all! We will proceed to the next step of voting for a PMC chair and > drafting a resolution for the board. > > Cheers, > > Antoine > >> On Dec 20, 2022, at 8:45 AM, Antoine Toulme wrote: >> >> I’ve let the vote go on for a bit. I’d like to make sure we get a chance for >> final votes and comments and I will close it by tonight PT time. >> >> Cheers, >> >> Antoine >> >>> On Dec 19, 2022, at 6:45 AM, Josh Fischer wrote: >>> >>> To build on what Dave is saying (from my experience at least) is projects >>> will enter the incubator and they tend to focus on building new features on >>> top of new features. Instead of focusing on how they can transfer that deep >>> knowledge of the system to anyone who is willing to learn. >>> >>> Getting those people to feel comfortable stepping up can be a challenge. >>> Making new comers (whoever they are) feel welcome to ask questions and >>> contribute on mailing list discussion, prs, code contributions, etc is the >>> most important part of building a self-sustaining community. >>> >>> >>> I’ll get off my soapbox now. >>> >>> - Josh >>> >>> >>> >>> On Mon, Dec 19, 2022 at 2:40 AM Christofer Dutz >>> wrote: >>> Sorry for asking, but Dave, could you please explain that reply … admittedly I didn’t understand what you wanted to say (Guess I would consider it advanced English and I simply didn’t understand it). Chris From: Dave Fisher Date: Monday, 12. December 2022 at 06:19 To: general@incubator.apache.org Subject: Re: [VOTE] Apache Tuweni graduation Thanks. I think you are onto an idea of community that could be somehow explicitly part of the incubator’s curriculum. That’s a separate discussion. Best, Dave Sent from my iPhone > On Dec 11, 2022, at 7:17 PM, Willem Jiang wrote: > > I agree we don't need to hold the Tuweni graduation for the release checking. > But if we want to build a sustainable
Re: [RESULT][VOTE] Apache Tuweni graduation
HI, > Because this release didn’t have enough votes, we moved it to the general > incubator list where it was duly voted. Sorry, that’s not how it works, the PPMC needs to vote on it first, and then once that has passed, vote for it on the IPMC list. If you don’t get enough votes on the podling's list, that may indicate a community issue. Either you need to find more PPMC members or try and engage existing ones. Kind Regards, Justin
