Re: [VOTE] Release Apache Uniffle (Incubating) 0.6.1-rc3

[He Qi]

>From my side
+1

I have checked
* Download links, checksums and PGP signatures are valid
* LICENSE, NOTICE and DISCLAIMER-WIP files are correct
* No unlicensed compiled archives bundled in source archive.
* UT passed. I use the command `mvn package -Pspark3

On 2022/12/06 05:56:13 Kaijie Chen wrote:
> Hello Incubator Community,
> 
> This is a call for a vote to release Apache Uniffle (Incubating)
> version 0.6.1-rc3.
> 
> The Apache Uniffle community has voted on and approved a proposal to
> release Apache Uniffle (Incubating) version 0.6.1-rc3.
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Uniffle community vote thread:
> https://lists.apache.org/thread/sorpwljxl2nssowhloswo662jng5qwr7
> 
> Vote result thread:
> https://lists.apache.org/thread/4k9v3n6fvtmd3y37jhof2t6kb90qjg36
> 
> The release candidate:
> https://dist.apache.org/repos/dist/dev/incubator/uniffle/0.6.1-rc3/
> 
> Git tag for the release:
> https://github.com/apache/incubator-uniffle/tree/v0.6.1-rc3
> 
> Release notes:
> https://uniffle.apache.org/download/release-notes-0.6.1/
> 
> The artifacts signed with PGP key
> 3B8167D035D33A4C2D725FAA39A39E985C5EFBA4
> corresponding to c...@apache.org, that can be found in keys file:
> https://dist.apache.org/repos/dist/dev/incubator/uniffle/KEYS
> 
> The vote will be open for at least 72 hours or until the necessary
> number of votes are reached.
> 
> Please vote accordingly:
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> Thanks,
> Kaijie Chen
> On behalf of Apache Uniffle (Incubating) community
> 
> -
> 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

Re: [VOTE] Apache Tuweni graduation

[Willem Jiang]

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 as a blocker for graduation.
> There was enough consensus and testing to spin and publish 14 releases.
> There has been healthy conversation about this very topic among the mentors
> and contributors on the private list.
>
> The nature of this project is that the consumption of these libraries are
> going to get less traction while in incubation and a community may grow
> larger as a TLP as confidence is instilled by that status.
>
> The Tuweni community has demonstrated the ability to publish releases
> within that Apache Way and guidelines, has welcomed new contributors, etc.
> The long term success will require a larger active community but I don't
> think that needs to block graduation as the incubation goals have been met.
>
> My 2 cents.
>
> On Mon, Dec 5, 2022 at 7:41 PM Willem Jiang  wrote:
>
> > I agree with Gang Li. The Bus factor[1] of this project is relatively high.
> >
> > [1]https://en.wikipedia.org/wiki/Bus_factor
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Mon, Dec 5, 2022 at 11:06 PM li gang  wrote:
> > >
> > > I checked the contributions of the Tuweni project[1],the traffic of the
> > > mail list d...@tuweni.apache.org[2] and the KEYS[3].
> > >
> > > It looks like the project is mainly maintained by Antoine Toulme self,
> > > I have a concern this is not comply with the diversity.
> > >
> > > [1]https://github.com/apache/incubator-tuweni/graphs/contributors
> > > [2]https://lists.apache.org/list?d...@tuweni.apache.org
> > > [3]https://downloads.apache.org/incubator/tuweni/KEYS
> > >
> > > Antoine Toulme  于2022年12月5日周一 15:14写道：
> > >
> > > > Dear Apache Incubator Community and IPMC members,
> > > >
> > > > We discussed the graduation for Tuweni in the Apache Incubator
> > > > Community [4], where no issues were raised and positive replies were
> > > > received.
> > > > After having the graduation discussion in the Tuweni community [1], we
> > > > have passed the vote within Tuweni community [2] and the vote result
> > > > was published [3].
> > > >
> > > > I would like to start this voting thread to request graduating Apache
> > > > Tuweni(incubating) from Apache Incubator as a Top Level Project.
> > > >
> > > > Please provide your vote accordingly:
> > > > [ ] +1 Yes, I support Tuweni project to graduate from the Apache
> > Incubator.
> > > > [ ] +0 No opinion.
> > > > [ ] -1 No, the Tuweni project is not ready to graduate, because...
> > > >
> > > > Thank you for participating in the vote. This vote will stay open for
> > at
> > > > least 72 hours.
> > > >
> > > > Here is an overview of the Apache Tuweni(incubating) to help with the
> > > > vote.
> > > >
> > > > *Community*
> > > >
> > > > ● The PPMC is active, with PMC members voting for graduation along with
> > > > mentors.
> > > > ● 6 new committers were added, bringing the total number of committers
> > to
> > > > 14 from 12 different
> > > > organizations.
> > > > ● The number of contributors is now 25 and growing.
> > > > ● The dev@Tuweni mailing list currently has 33 subscribers [4].
> > > >
> > > > *Project*
> > > >
> > > > ● Apache Tuweni (incubating) is a set of libraries and other tools to
> > aid
> > > > development of blockchain and other  decentralized software in Java and
> > > > other JVM languages. It includes a low-level bytes library,
> > serialization
> > > > and deserialization codecs (e.g. RLP), various cryptography functions
> > and
> > > > primitives, and lots of other helpful utilities. Tuweni is developed
> > for
> > > > JDK 11 or higher.
> > > > ● Project maturity model and incubation status is detailed in [5]
> > > > ● Tuweni has been incubating [5] since 2019-02-25 for over 45
> > > > months.
> > > > ● Tuweni community released a total of 14 Apache releases [6].
> > > > ● 331 pull requests created closed [7].
> > > > ● 76 issues created, and 46 issues closed [8].
> > > > ● The release cadence is about 3 months.
> > > >
> > > > *Brand, License, and Copyright*
> > > >
> > > > ● We submitted an application for the brand [9] 

Re: [DISCUSS] Graduate Apache Sedona to a Top Level Project

[Martin Andersson]

+1 (non-binding)

Den mån 5 dec. 2022 kl 06:38 skrev Jinxuan Wu :

> +1
>
> Looking forward to Apache Sedona’s graduation!
> On Dec 4, 2022 at 7:05 PM -0700, Goson zhang ,
> wrote:
> > +1 (non-binding)
> >
> > Good luck!
> >
> > Looking forward to Santa sending a candy to make everyone happy:)
> >
> > Netanel Malka  于2022年12月4日周日 02:28写道：
> >
> > > +1 really great project :)
> > >
> > > On Sat, Dec 3, 2022, 20:27 George Percivall  >
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Apache Sedona’s graduation will be a great addition to the geospatial
> > > > capabilities of Apache TLPs
> > > >
> > > >
> > > > George Percivall
> > > > perciv...@apache.org
> > > >
> > > >
> > > >
> > > > > On Dec 3, 2022, at 3:07 AM, Bertil Chapuis 
> wrote:
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > Sedona is an awesome project!
> > > > >
> > > > > Best,
> > > > >
> > > > > Bertil
> > > > >
> > > > > > On 3 Dec 2022, at 01:06, PJ Fanning 
> wrote:
> > > > > >
> > > > > > +1 (binding) - Sedona project seems to be in good shape and the
> team
> > > > > > looks ready to become a TLP
> > > > > >
> > > > > > On Sat, 3 Dec 2022 at 00:21, Sunil Govindan 
> > > wrote:
> > > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > Thanks for shepherding this. All the best.
> > > > > > >
> > > > > > > Thanks
> > > > > > > Sunil
> > > > > > >
> > > > > > > On Fri, Dec 2, 2022 at 6:56 AM Calvin Kirs 
> wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > +1, I think it's time to graduate.
> > > > > > > >
> > > > > > > > On Fri, Dec 2, 2022 at 5:28 PM Jia Yu 
> wrote:
> > > > > > > > >
> > > > > > > > > Dear Apache Incubator Community (CCed Sedona dev),
> > > > > > > > >
> > > > > > > > > Apache Sedona has been incubating since 07-19-2020. For
> over 2
> > > > years, the
> > > > > > > > > Sedona community has made great progress and grown rapidly
> under
> > > the
> > > > > > > > > guidance of our mentors. We believe the Sedona project has
> met the
> > > > > > > > > conditions for graduation. We'd like to start the
> discussion and
> > > > collect
> > > > > > > > > feedback towards graduation. Please feel free to join the
> > > discussion.
> > > > > > > > >
> > > > > > > > > The discussion will remain open for at least 72 hours.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Jia
> > > > > > > > >
> > > > > > > > > ***
> > > > > > > > >
> > > > > > > > > The incubation status of Sedona can be found in [1]. The
> Apache
> > > > Sedona
> > > > > > > > > community has a discussion thread of graduating Sedona to
> a TLP
> > > [2],
> > > > > > > > passed
> > > > > > > > > the community vote [3]. The vote result was announced [4].
> The PPMC
> > > > also
> > > > > > > > > passed a vote [5] to nominate Jia as the chair of Sedona
> TLP, and
> > > the
> > > > > > > > > result was also announced [6]. We had a discussion about
> Sedona
> > > > > > > > graduation
> > > > > > > > > in the incubator this September [12] and all issues have
> been
> > > fixed.
> > > > > > > > >
> > > > > > > > > The summary on the state of the community is listed below
> and the
> > > > self
> > > > > > > > > assessment (Apache Project Maturity Model) is in [7].
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Sedona joined the Apache Incubator on July 19 2020. As of
> Dec 2
> > > 2022:
> > > > > > > > >
> > > > > > > > > ** Community **:
> > > > > > > > >
> > > > > > > > > * number of contributions (commits) since incubation: 394
> > > > > > > > > - Overall: 1083
> > > > > > > > > - 36% of the commits were added since incubation.
> > > > > > > > >
> > > > > > > > > * number of contributors (and growth since incubation): 51
> > > > > > > > > - Overall: 86
> > > > > > > > > - 59% of the contributors joined since incubation
> > > > > > > > >
> > > > > > > > > * email discussions since incubation: 1214 threads on
> > > > > > > > d...@sedona.apache.org
> > > > > > > > >
> > > > > > > > > * Number of monthly downloads: grow from 200K per month to
> 800K per
> > > > > > > > month.
> > > > > > > > >
> > > > > > > > > * Marked as critical project on PyPi as Sedona ranks among
> top 1%
> > > > most
> > > > > > > > > downloaded Python projects on PyPi.
> > > > > > > > >
> > > > > > > > > ** Project **
> > > > > > > > >
> > > > > > > > > * releases: 7
> > > > > > > > >
> > > > > > > > > * number of release managers: 3 (Jia Yu, Paweł Kociński,
> Kanchan
> > > > > > > > Chowdhury)
> > > > > > > > >
> > > > > > > > > * Apache Sedona website (sedona.apache.org) is compliant
> with ASF
> > > > > > > > > requirement [8]. The GitHub.com used in external resources
> are
> > > > compliant
> > > > > > > > > with ASF privacy requirement [9]
> > > > > > > > >
> > > > > > > > > ** Brands ,License, and Copyright **
> > > > > > > > >
> > > > > > > > > * We submitted an application for the brand [10] and it
> has been
> > > > > > > > > reviewed and approved.
> > > > > > > > >
> > > > > > > > > * Apache Sedona community maintains 

Re: [DISCUSS] KIE Proposal

[Jason Porter]

> On Dec 6, 2022, at 01:43, Christofer Dutz  wrote:
> 
> Hi Jason,
> 
> Well, those numbers are a bit better than the initial ones.
> Thing is: Mentors will not only have to help onboard people to Apache and 
> teach them how to do things, if they are doing their job correctly, they 
> should also really audit the releases being done and help get the codebase 
> into shape first.
> 
> Even with 12 sub-projects, work-wise that would put a load on the mentors, as 
> if they signed up for mentoring 12 projects.
> 
> So how about bringing in projects separately (where it makes sense)? There 
> each project could have their initial PPMC and committer lists and it would 
> spread out the load a bit. However I would expect staffing 12 projects with 
> enough work-willing mentors will still be challenging and I would assume not 
> all of them to find enough of them, but it could be one first step.
> 
> Or is there an advantage of considering all projects as one unity?
> 
> Chris
> 
> [snip]

That is part of a broader question. Some of those repos are things like 
examples for kogito, the website, etc. Things that are part of the projects 
themselves, but don’t have a life outside of the project to which they belong. 
I understand we’ll probably have to collapse the structures within Apache and 
have a single repo per project. What we’re really looking at as far as projects 
being donated:

Kogito
Drools
jBPM

Then there are the supporting repos for things like examples, docs, website, 
tooling, etc. Many of the people working on these projects work on all of them, 
so it would probably be the same group of people with very little deviation in 
the list of committers. Could they be different PPMCs, but they’d basically be 
the same group, just more work with the reports, setup, infra, etc.

Jason Porter
Software Engineer
He/Him/His

IBM

Re: [VOTE] Apache Tuweni graduation

[li gang]

Regarding graduation, the ASF official website made some introductions, and
also introduced how to build an open and diverse community.

First,whether graduation requires diversity?
Here is a quote from [1].
 > A major criterion for graduation is to have developed an open and
diverse meritocratic community.
Time has demonstrated that these kinds of communities are more robust and
productive than more closed ones.

Second, is the current community diverse?
Here is the introduction to diversity in [1].
> The project is considered to have a diverse community when it is not
highly dependent on any single contributor (there are at least 3 legally
independent committers and there is no single company or entity that is
vital to the success of the project).

Because I checked the [3],[4],[5] and It looks like the project is mainly
maintained by Antoine Toulme self,so I have the concern.
Of course, we can also provide more evidence that the community is diverse

Third, how community grows diverse?
We can read more on how to successfully build an open and diverse community
in the community guide[2].


[1]https://incubator.apache.org/guides/graduation.html
[2]https://incubator.apache.org/guides/community.html
[3]https://github.com/apache/incubator-tuweni/graphs/contributors
[4]https://lists.apache.org/list?d...@tuweni.apache.org
[5]https://downloads.apache.org/incubator/tuweni/KEYS

Antoine Toulme  于2022年12月6日周二 15:56写道：

> Here are the relevant messages Larry mentions:
> https://lists.apache.org/thread/rl93tocc2nt3b6lnwvqp3xbnxcvc5cwg
> https://lists.apache.org/thread/xrf3ft5b9jzbbtcwo2k8kqbk2fn69vyx
>
> It’s unclear to me how the incubator will further help with establishing
> diversity - during our discussion, Justin Mclean mentioned he thought it
> was a good idea to get out of incubation to drive further adoption and
> growth (https://lists.apache.org/thread/9ghzpyqjcw7j2zbfq5nrx0ckq2tx761f).
> > Hi,  Given teh length of time you have been in the Incubator, I would
> try to graduate, putting it off further, may mean it never happens.  Kind
> Regards, Justin
>
> I would be grateful for any advice to bring additional growth to the
> project. Do you see any avenue inside the incubator that we should engage
> with? Any specific items we could pursue, perhaps?
>
> Cheers,
>
> Antoine
>
>
>
> > On Dec 5, 2022, at 5:50 PM, larry mccay  wrote:
> >
> > I'm not so sure that I see this as a blocker for graduation.
> > There was enough consensus and testing to spin and publish 14 releases.
> > There has been healthy conversation about this very topic among the
> mentors
> > and contributors on the private list.
> >
> > The nature of this project is that the consumption of these libraries are
> > going to get less traction while in incubation and a community may grow
> > larger as a TLP as confidence is instilled by that status.
> >
> > The Tuweni community has demonstrated the ability to publish releases
> > within that Apache Way and guidelines, has welcomed new contributors,
> etc.
> > The long term success will require a larger active community but I don't
> > think that needs to block graduation as the incubation goals have been
> met.
> >
> > My 2 cents.
> >
> > On Mon, Dec 5, 2022 at 7:41 PM Willem Jiang 
> wrote:
> >
> >> I agree with Gang Li. The Bus factor[1] of this project is relatively
> high.
> >>
> >> [1]https://en.wikipedia.org/wiki/Bus_factor
> >>
> >> Willem Jiang
> >>
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >> On Mon, Dec 5, 2022 at 11:06 PM li gang  wrote:
> >>>
> >>> I checked the contributions of the Tuweni project[1],the traffic of the
> >>> mail list d...@tuweni.apache.org[2] and the KEYS[3].
> >>>
> >>> It looks like the project is mainly maintained by Antoine Toulme self,
> >>> I have a concern this is not comply with the diversity.
> >>>
> >>> [1]https://github.com/apache/incubator-tuweni/graphs/contributors
> >>> [2]https://lists.apache.org/list?d...@tuweni.apache.org
> >>> [3]https://downloads.apache.org/incubator/tuweni/KEYS
> >>>
> >>> Antoine Toulme  于2022年12月5日周一 15:14写道：
> >>>
>  Dear Apache Incubator Community and IPMC members,
> 
>  We discussed the graduation for Tuweni in the Apache Incubator
>  Community [4], where no issues were raised and positive replies were
>  received.
>  After having the graduation discussion in the Tuweni community [1], we
>  have passed the vote within Tuweni community [2] and the vote result
>  was published [3].
> 
>  I would like to start this voting thread to request graduating Apache
>  Tuweni(incubating) from Apache Incubator as a Top Level Project.
> 
>  Please provide your vote accordingly:
>  [ ] +1 Yes, I support Tuweni project to graduate from the Apache
> >> Incubator.
>  [ ] +0 No opinion.
>  [ ] -1 No, the Tuweni project is not ready to graduate, because...
> 
>  Thank you for participating in the vote. This vote will stay open for
> >> at
>  least 72 hours.

Re: [DISCUSS] KIE Proposal

[Christofer Dutz]

Hi Jason,

Well, those numbers are a bit better than the initial ones.
Thing is: Mentors will not only have to help onboard people to Apache and teach 
them how to do things, if they are doing their job correctly, they should also 
really audit the releases being done and help get the codebase into shape first.

Even with 12 sub-projects, work-wise that would put a load on the mentors, as 
if they signed up for mentoring 12 projects.

So how about bringing in projects separately (where it makes sense)? There each 
project could have their initial PPMC and committer lists and it would spread 
out the load a bit. However I would expect staffing 12 projects with enough 
work-willing mentors will still be challenging and I would assume not all of 
them to find enough of them, but it could be one first step.

Or is there an advantage of considering all projects as one unity?

Chris

From: Jason Porter 
Date: Monday, 5. December 2022 at 19:08
To: general@incubator.apache.org 
Subject: Re: [DISCUSS] KIE Proposal
On Dec 5, 2022, at 01:23, Christofer Dutz  wrote:

Hi all,

as you already mentioned PLC4X, I think in general supporting something to do 
logic-decisions based on industrial data-streams would be a nice addition.  I 
do also agree that adding 80 projects might be quite a big gulp for us to 
ingest.

How many people are we talking about being on the IPMC/committers? Mentoring a 
project with hundreds of people would probably require a fleet of mentors.

Hey Chris,

The size of the PPMC is a good question. Per the Incubator site 
[https://incubator.apache.org/guides/ppmc.html] it is typically made up of the 
initial committers and mentors. We have 51 people currently tagged for being 
initial committers and three people as mentors. Most have not done anything 
with Apache. That feels like a lot of people for an initial PPMC. We were 
initially thinking of something small around 7 people initially. Not sure how 
that plays in with the list of initial committers though, unless we par that 
down as well and bring people in during the incubation.

WRT the number of projects, we’re not looking at donating all of those. We’re 
still in discussion on the final list, but that list is considerably smaller. 
Discussions are leaning toward 12 or so.

Jason Porter
Software Engineer
He/Him/His

IBM

Chris

From: Willem Jiang mailto:willem.ji...@gmail.com>>
Date: Monday, 5. December 2022 at 04:15
To: general@incubator.apache.org 
mailto:general@incubator.apache.org>>
Subject: Re: [DISCUSS] KIE Proposal
We need to go through the IP clearance and help the project to do the
release that follows the Apache police.
It could be a nightmare for the incubator if we donate an "Umbrella Project."
Can we consider donating sub-projects such as kogito one by one?


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Dec 2, 2022 at 9:21 AM Niall Pemberton
 wrote:

Wow, 137 GitHub repositories!

OK, so 38 are archived and 19 are forks, but that still leaves 80! Do you
have a rough idea of how many of those would be part of the incubation?

Historically, Apache has been against "Umbrella Projects" - encouraging
them to break up and become individual Top Level Projects (TLP) in their
own right - the biggest example of that was Jakarta which used to be
anything java related - but there have been others where sub-projects which
have a life of their own have moved out to become TLPs.

To me this looks like it should be 4 or 5 projects - its not clear whether
kie is a product in its own right (with releasable artifcats) or just the
umbrella that the others are grouped under?
 * drools
 * jbpm
 * kogito
 * optaplanner
 * kie ???

Niall


On Thu, 1 Dec 2022 at 21:36, Jason Porter  wrote:

Abstract

KIE (Knowledge is Everything) is a community of solutions and supporting
tooling for knowledge engineering and process automation, focusing on
events, rules, and workflows.

Proposal<
https://cwiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal#proposal


KIE is a community dedicated to supporting knowledge engineering and
process automation, using standards from groups like OMG (BPMN, CMMN, DMN),
CNCF (Serverless Workflow, Cloud Events), and DMG (PMML, PFA). KIE is
comprised of leading open-source projects (like Drools and jBPM), which
provide modeling and code authoring tools in this space. The work has a
strong emphasis on being a first-class citizen for Kubernetes but will
continue to support embedded and other environments such as edge computing.
Drools and jBPM are well-known projects in their areas of rules and
workflow and they will be joined by another project, building on a shared
core with jBPM, for CNCF’s Serverless Workflow - this project is going
through a naming process at the time of this application. Kogito is the
foundation project for workflow which jBPM and CNCF’s Serverless Workflow
build on. Services and frameworks are provided to enable those projects in
a