[RESULT][VOTE] Release Apache Sedona 1.3.1-incubating-rc1
Dear all, The vote closes now as 72hr have passed. The vote PASSES with +1 (binding): Felix, Sunil, Li Gang No -1 votes The vote thread (Permalink from https://lists.apache.org/list.html): https://lists.apache.org/thread/v8r6xlx5tlkot1x9cvptc9j55o2x64zv I will publish the release and make an announcement once it is done. Thanks, Jia
Re: [VOTE] Release Apache Sedona 1.3.1-incubating-rc1
Dear all, Thank you all for your help. We have collected enough votes. Now the voting is closed. Regards, Jia On Tue, Dec 20, 2022 at 7:30 AM li gang wrote: > +1 (binding) > I checked > - Files have the word incubating in their name. > - Signatures and hashes are fine > - DISCLAIMER,LICENSE and NOTICE files exist. > - LICENSE and NOTICE looks good. > > Jia Yu 于2022年12月17日周六 17:00写道： > > > Hi all, > > > > This is a call for vote on Apache Sedona 1.3.1-incubating-rc1. Due to two > > critical bugs [1] and [2] , the users who use 1.3.0 have trouble running > > Sedona on Java 8 or Scala 2.12. We have to make this new release in a > short > > period of time. > > > > Thanks, > > Jia > > > > Sedona Community vote thread (Permalink from > > https://lists.apache.org/list.html): > > https://lists.apache.org/thread/wj0bsgyy48f9dw8n896tc0rt22dy7ww7 > > > > Sedona community vote result thread (Permalink from > > https://lists.apache.org/list.html): > > https://lists.apache.org/thread/4l8yl3bd7yqbxzgmzc2odnxgsgs33vjc > > > > Release notes: > > > > > https://github.com/apache/incubator-sedona/blob/sedona-1.3.1-incubating-rc1/docs/setup/release-notes.md > > > > Build instructions: > > > > > https://github.com/apache/incubator-sedona/blob/sedona-1.3.1-incubating-rc1/docs/setup/compile.md > > > > GitHub tag: > > > > > https://github.com/apache/incubator-sedona/releases/tag/sedona-1.3.1-incubating-rc1 > > > > GPG public key to verify the Release: > > https://downloads.apache.org/incubator/sedona/KEYS > > > > Source code and binaries: > > > > > https://dist.apache.org/repos/dist/dev/incubator/sedona/1.3.1-incubating-rc1/ > > > > The vote will be open for at least 72 hours or until at least 3 "+1" PMC > > votes are cast > > > > Please vote accordingly: > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > Checklist for reference: > > > > [ ] Download links are valid. > > > > [ ] Checksums and PGP signatures are valid. > > > > [ ] DISCLAIMER is included. > > > > [ ] Source code artifacts have correct names matching the current > release. > > > > [ ] LICENSE is there > > > > [ ] No unexpected binary files > > > > For a detailed checklist please refer to: > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > > > [1] https://issues.apache.org/jira/browse/SEDONA-210 > > [2] https://issues.apache.org/jira/browse/SEDONA-211 > > > > > -- > > > -- > Best Regards > > DolphinScheduler PMC > Gang Li 李岗 > > lgcar...@apache.org >
[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 Open Source project, we still need to pay lots of attention to community building. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem > On Sun, Dec 11, 2022 at 9:24 AM Antoine Toulme >>> wrote: > > Hello folks, > > Apache Tuweni had a much smaller community when it started its >>> incubation at Apache. The path of this project has been impacted by the >>> domain it applies to and the pandemic certainly hasn't helped. Still it has >>> managed to create enough momentum to make regular releases and check off >>> all incubation checks. > Community building is definitely still on the menu - right now and >>> later as well. We will continue building and including folks. We have >>> onboarded successfully multiple committers and have received contributions. >>> I expect this trend to continue and mature. > > The question is whether the best place for us to continue growing is >>> the incubator. The incubator adds additional checks on our releases and >>> slows down our cycles, which has historically driven folks to fork and move >>> away from the project. > > The incubator doesn't offer opportunities for community building, from >>> what I know. We will need to continue to build our image and presence to >>> attract contributors on our own. > > The project mentors have been nothing short of fantastic. They have >>> been helpful in maturing the project. In my opinion, we are using their >>> precious time when they should be engaged in helping other projects of the >>> incubator. > > With this, I want to thank the incubator. We had a great experience >>> building with you all. I personally believe we should free the incubator's >>> time and attention to concentrate on other projects. I also believe the >>> project is mature enough to function outside of the incubator. > > I vote +1 to graduate Tuweni from the incubator. > > Thanks, > > Antoine > >>> On Dec 7, 2022, at 3:37 PM, larry mccay wrote: >> >> We have also recently seen long term incubating projects with >>> considerable >> adoption falter. >> I consider the fact that they did not graduate early enough a >>> contributing >> factor here. >> >> Nothing wrong with incubation but staying in the incubator and >>> encountering >> attrition is different from TLP >> with some churn with new folks coming into an official TLP project >>> while >> others can fall off in a healthy way. >> >> Again, having the community test and release 14 separate releases >> demonstrates contributors in the community >> even if they aren't all materially contributing code. >> >> >> >> On Wed, Dec 7, 2022 at 3:45 AM Christofer Dutz < >>>
Re: Looking for a Champion: FuzzyLite
Hi PJ, Thanks for your email. Only a few people have contributed, and not constantly. I have been the main driver of the engineering efforts. I am thinking of Apache as a way to start a community and keep the development on the projects more active. Juan. On Wed, 21 Dec 2022 at 01:06, PJ Fanning wrote: > Resending and including OP, just in case. > > -- Forwarded message - > From: PJ Fanning > Date: Tue, 20 Dec 2022 at 13:02 > Subject: Re: Looking for a Champion: FuzzyLite > To: > > > Thanks Juan for your interest in contributing this work to the ASF. > > I have a question about whether there are any other people who have > contributed to FuzzyLite and if they would be interested in continuing > to contribute as part of a FuzzyLite PMC? > > One of the most important aspects of an ASF project is building a > community. > > On Tue, 20 Dec 2022 at 08:29, Juan Rada-Vilela wrote: > > > > Hi, > > > > I have created over the past years three projects: fuzzylite (C++), > > jfuzzylite (Java), and pyfuzzylite (Python), which are well designed and > > engineered libraries for fuzzy logic controllers, a field within > Artificial > > Intelligence. Their repositories are in github.com/fuzzylite, and the > home > > page is fuzzylite.com > > > > I am considering having them for incubation at Apache, so I am looking > for > > a Champion to first find if there is interest in the ASF, and maybe > start > > with one? > > > > Kind regards, > > > > Juan. >
Re: [VOTE] Apache Tuweni graduation
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 Open Source project, we still >>> need to pay lots of attention to community building. >>> >>> >>> Willem Jiang >>> >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>> On Sun, Dec 11, 2022 at 9:24 AM Antoine Toulme >> wrote: Hello folks, Apache Tuweni had a much smaller community when it started its >> incubation at Apache. The path of this project has been impacted by the >> domain it applies to and the pandemic certainly hasn't helped. Still it has >> managed to create enough momentum to make regular releases and check off >> all incubation checks. Community building is definitely still on the menu - right now and >> later as well. We will continue building and including folks. We have >> onboarded successfully multiple committers and have received contributions. >> I expect this trend to continue and mature. The question is whether the best place for us to continue growing is >> the incubator. The incubator adds additional checks on our releases and >> slows down our cycles, which has historically driven folks to fork and move >> away from the project. The incubator doesn't offer opportunities for community building, from >> what I know. We will need to continue to build our image and presence to >> attract contributors on our own. The project mentors have been nothing short of fantastic. They have >> been helpful in maturing the project. In my opinion, we are using their >> precious time when they should be engaged in helping other projects of the >> incubator. With this, I want to thank the incubator. We had a great experience >> building with you all. I personally believe we should free the incubator's >> time and attention to concentrate on other projects. I also believe the >> project is mature enough to function outside of the incubator. I vote +1 to graduate Tuweni from the incubator. Thanks, Antoine >> On Dec 7, 2022, at 3:37 PM, larry mccay wrote: > > We have also recently seen long term incubating projects with >> considerable > adoption falter. > I consider the fact that they did not graduate early enough a >> contributing > factor here. > > Nothing wrong with incubation but staying in the incubator and >> encountering > attrition is different from TLP > with some churn with new folks coming into an official TLP project >> while > others can fall off in a healthy way. > > Again, having the community test and release 14 separate releases > demonstrates contributors in the community > even if they aren't all materially contributing code. > > > > On Wed, Dec 7, 2022 at 3:45 AM Christofer Dutz < >> christofer.d...@c-ware.de> > wrote: > >> Hi all, >> >> And in the last few months the ASF has sadly seen enough cases, in >> which >> even big projects suffered from the lack of diversity. >> So, I would also consider this to be a blocker. >> >> Community building isn’t something that happens or comes for free. >> It’s actually hard work, but it needs to be done. >> >> Just my opinion on this topic. >> >> Chris >> >> From: Willem Jiang >> Date: Wednesday, 7.
Re: [VOTE] Release Apache Sedona 1.3.1-incubating-rc1
+1 (binding) I checked - Files have the word incubating in their name. - Signatures and hashes are fine - DISCLAIMER,LICENSE and NOTICE files exist. - LICENSE and NOTICE looks good. Jia Yu 于2022年12月17日周六 17:00写道： > Hi all, > > This is a call for vote on Apache Sedona 1.3.1-incubating-rc1. Due to two > critical bugs [1] and [2] , the users who use 1.3.0 have trouble running > Sedona on Java 8 or Scala 2.12. We have to make this new release in a short > period of time. > > Thanks, > Jia > > Sedona Community vote thread (Permalink from > https://lists.apache.org/list.html): > https://lists.apache.org/thread/wj0bsgyy48f9dw8n896tc0rt22dy7ww7 > > Sedona community vote result thread (Permalink from > https://lists.apache.org/list.html): > https://lists.apache.org/thread/4l8yl3bd7yqbxzgmzc2odnxgsgs33vjc > > Release notes: > > https://github.com/apache/incubator-sedona/blob/sedona-1.3.1-incubating-rc1/docs/setup/release-notes.md > > Build instructions: > > https://github.com/apache/incubator-sedona/blob/sedona-1.3.1-incubating-rc1/docs/setup/compile.md > > GitHub tag: > > https://github.com/apache/incubator-sedona/releases/tag/sedona-1.3.1-incubating-rc1 > > GPG public key to verify the Release: > https://downloads.apache.org/incubator/sedona/KEYS > > Source code and binaries: > > https://dist.apache.org/repos/dist/dev/incubator/sedona/1.3.1-incubating-rc1/ > > The vote will be open for at least 72 hours or until at least 3 "+1" PMC > votes are cast > > Please vote accordingly: > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > Checklist for reference: > > [ ] Download links are valid. > > [ ] Checksums and PGP signatures are valid. > > [ ] DISCLAIMER is included. > > [ ] Source code artifacts have correct names matching the current release. > > [ ] LICENSE is there > > [ ] No unexpected binary files > > For a detailed checklist please refer to: > > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist > > [1] https://issues.apache.org/jira/browse/SEDONA-210 > [2] https://issues.apache.org/jira/browse/SEDONA-211 > -- -- Best Regards DolphinScheduler PMC Gang Li 李岗 lgcar...@apache.org
Re: [VOLUNTEER WANTED]Incubator Shepherds
Hi Calvin, I can get involved if you are looking for volunteers. I have reasonable availability for the foreseeable future. Regards, PJ On Tue, 20 Dec 2022 at 03:45, Calvin Kirs wrote: > > Hi, > > Shepherd[1] participation has been low for the past two years (maybe > longer), so I thought of trying to see if any other IPMC members would > be willing to take on this role. > > if possible, we could allocate them according to everyone's free periods. > so, if you are interested in this, please leave your name and time cycle > > [1]https://cwiki.apache.org/confluence/display/INCUBATOR/IncubatorShepherds > > -- > Best wishes！ > CalvinKirs > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Fwd: Looking for a Champion: FuzzyLite
Resending and including OP, just in case. -- Forwarded message - From: PJ Fanning Date: Tue, 20 Dec 2022 at 13:02 Subject: Re: Looking for a Champion: FuzzyLite To: Thanks Juan for your interest in contributing this work to the ASF. I have a question about whether there are any other people who have contributed to FuzzyLite and if they would be interested in continuing to contribute as part of a FuzzyLite PMC? One of the most important aspects of an ASF project is building a community. On Tue, 20 Dec 2022 at 08:29, Juan Rada-Vilela wrote: > > Hi, > > I have created over the past years three projects: fuzzylite (C++), > jfuzzylite (Java), and pyfuzzylite (Python), which are well designed and > engineered libraries for fuzzy logic controllers, a field within Artificial > Intelligence. Their repositories are in github.com/fuzzylite, and the home > page is fuzzylite.com > > I am considering having them for incubation at Apache, so I am looking for > a Champion to first find if there is interest in the ASF, and maybe start > with one? > > Kind regards, > > Juan. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Looking for a Champion: FuzzyLite
Thanks Juan for your interest in contributing this work to the ASF. I have a question about whether there are any other people who have contributed to FuzzyLite and if they would be interested in continuing to contribute as part of a FuzzyLite PMC? One of the most important aspects of an ASF project is building a community. On Tue, 20 Dec 2022 at 08:29, Juan Rada-Vilela wrote: > > Hi, > > I have created over the past years three projects: fuzzylite (C++), > jfuzzylite (Java), and pyfuzzylite (Python), which are well designed and > engineered libraries for fuzzy logic controllers, a field within Artificial > Intelligence. Their repositories are in github.com/fuzzylite, and the home > page is fuzzylite.com > > I am considering having them for incubation at Apache, so I am looking for > a Champion to first find if there is interest in the ASF, and maybe start > with one? > > Kind regards, > > Juan. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
