Looking for a Champion: FuzzyLite
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.
[VOLUNTEER WANTED]Incubator Shepherds
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
SDAP 1.0.0-rc2
Incubator PMC members, Can I get some help inspecting a release candidate? SDAP has been in incubation for several years, has only one remaining active mentor (myself!) and has just produced a release candidate good enough for me to vote +1. In due course this RC will appear in a vote on this list, but could we do them a favor and shorten the cycle a bit? If you are an IPMC member and have some time to inspect an RC, can you please read their vote email [1], inspect the artifacts, and reply with your feedback/vote. Your feedback will help them get to a good release sooner. Julian [1] https://lists.apache.org/thread/6nmknw8n1flwsqp4n3cromnrck21xmh9 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Apache Tuweni graduation
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. December 2022 at 02:59 > To: general@incubator.apache.org > Subject: Re: [VOTE] Apache Tuweni graduation > It looks like we need a dedicated community leader[1] to build a > diverse community (just borrow a pattern from InnerSource Common[2]). > > " Communication takes up a significant percentage of a
Re: [VOTE] Apache Tuweni graduation
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 >>> 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. December 2022 at 02:59 To: general@incubator.apache.org Subject: Re: [VOTE] Apache Tuweni graduation It looks like we need a dedicated community leader[1] to build a diverse community (just borrow a pattern from InnerSource Common[2]). " Communication takes up a significant percentage of a community leader's daily work. At the same time, he or she will likely also have to spearhead the initial development, too. In the face of limited capacity, inexperienced leaders will tend to focus on development and neglect communication. The barrier for potential contributors to make their first contribution and to commit to the community will be much higher if the community leader is hard to reach or is slow to respond to feedback and questions for lack of time." [1] https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/main/patterns/2-structured/dedicated-community-leader.md#forces [2]https://innersourcecommons.org/ Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Dec 6, 2022 at 9:51 AM larry mccay wrote: > > I'm not so sure that I see this
