possible interest in forming a community fork of akka

[PJ Fanning]

Hi everyone,

Apologies if this is not the right mailing list. If it is not, please
let me know and I'll switch the thread to the right list.

Lighbend [1], the company that maintains the popular open source
framework, Akka [2], recently announced they are moving Akka to a
non-OSS commercial license [3].

There is interest in the OSS community in forking Akka under a new
name and maintaining it as an ASF project [4].

It is early days yet but there is some discussion online [5].

Reading the incubator cookbook, a new podling would need to have
champions and mentors from within the Incubator PMC [6].

I would like to put my name forward for such a role, as an existing
ASF member [7].

If anyone else in the Incubator PMC would like to get involved, that
would be great.

Regards,
PJ

[1] https://www.lightbend.com/
[2] https://akka.io/
[3] https://www.lightbend.com/akka/license-faq
[4] https://github.com/mdedetrich/akka-apache-project
[5] https://github.com/mdedetrich/akka-apache-project/discussions/9
[6] 
https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
[7] https://whimsy.apache.org/roster/committer/fanningpj

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: possible interest in forming a community fork of akka

[PJ Fanning]

Thanks Ralph for looking at this.

It is early days but a number of people have expressed an interest in
joining the new community.

https://github.com/mdedetrich/akka-apache-project/discussions/3

There are some former Lightbend employees and some very active
contributors. Most of the people appear to have contributed to akka or
to related projects.

So far, it looks like quite a diverse group with no company or
interest group having too great a say.

There are other discussions, including ones about goals and release
plans at https://github.com/mdedetrich/akka-apache-project/discussions

On Mon, 26 Sept 2022 at 23:25, Ralph Goers  wrote:
>
> Before going too far with this I would be interested to know:
> 1. Who the initial committers/PMC members would be.
> 2. How much familiarity the proposed people already have with the code base.
> 3. How diverse the community is from an employment point of view.
>
> In other words, I would be concerned if this is pushed by just 3 or 4 people,
> none of which have ever spent much time in the code, and who all work for
> the same employer.
>
> Ralph
>
> > On Sep 26, 2022, at 11:11 AM, PJ Fanning  wrote:
> >
> > Hi everyone,
> >
> > Apologies if this is not the right mailing list. If it is not, please
> > let me know and I'll switch the thread to the right list.
> >
> > Lighbend [1], the company that maintains the popular open source
> > framework, Akka [2], recently announced they are moving Akka to a
> > non-OSS commercial license [3].
> >
> > There is interest in the OSS community in forking Akka under a new
> > name and maintaining it as an ASF project [4].
> >
> > It is early days yet but there is some discussion online [5].
> >
> > Reading the incubator cookbook, a new podling would need to have
> > champions and mentors from within the Incubator PMC [6].
> >
> > I would like to put my name forward for such a role, as an existing
> > ASF member [7].
> >
> > If anyone else in the Incubator PMC would like to get involved, that
> > would be great.
> >
> > Regards,
> > PJ
> >
> > [1] https://www.lightbend.com/
> > [2] https://akka.io/
> > [3] https://www.lightbend.com/akka/license-faq
> > [4] https://github.com/mdedetrich/akka-apache-project
> > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9
> > [6] 
> > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
> > [7] https://whimsy.apache.org/roster/committer/fanningpj
> >
> > -
> > 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
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: possible interest in forming a community fork of akka

[PJ Fanning]

Thanks Willem for taking the time to look into this.

The license change means the fork project will not be able to cherry
pick future fixes from Lightbend - at least not readily.

On a case by case basis, we could request that the PR submitter also
contribute them to the fork project.

In some cases, the critical fix might be submitted to the fork first
and it may be easier for the Lightbend team to cherry pick those cases
than it is for the fork team to do the opposite.

The real hope would be that the fork can attract a strong enough
community that any security issues can be fixed in house.

The core of Akka is quite stable at this point so hopefully critical
bugs should be rare. It's possible that some of the less used non-core
code might be more susceptible to having issues.

Links for recent security issues in Akka:
* https://doc.akka.io/docs/akka/current/security/index.html
* https://doc.akka.io/docs/akka-http/current/security.html


On Tue, 27 Sept 2022 at 02:30, Willem Jiang  wrote:
>
> After going through the FAQ of the Akka license,   it looks like we
> cannot backport the BSL codes to the Apache License branch.
>
> > If there is a newer version of the software under BSL, can I backport any 
> > of the code to an older, Open Source, version of Akka?
>
> > No. In this circumstance, you would either violate Lightbend’s copyright by 
> > re-releasing the code under Open Source, or you would violate the earlier 
> > Akka version’s Apache license by introducing incompatible BSL code (i.e., 
> > code subject to a use limitation not allowed by the Open Source Apache 2.0 
> > license).
>
> It will cause us a lot of effort to maintain the code, even if we just
> want to backport some critical bug fixes.
>
> [1]https://www.lightbend.com/akka/license-faq
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Sep 27, 2022 at 6:25 AM Ralph Goers  
> wrote:
> >
> > Before going too far with this I would be interested to know:
> > 1. Who the initial committers/PMC members would be.
> > 2. How much familiarity the proposed people already have with the code base.
> > 3. How diverse the community is from an employment point of view.
> >
> > In other words, I would be concerned if this is pushed by just 3 or 4 
> > people,
> > none of which have ever spent much time in the code, and who all work for
> > the same employer.
> >
> > Ralph
> >
> > > On Sep 26, 2022, at 11:11 AM, PJ Fanning  wrote:
> > >
> > > Hi everyone,
> > >
> > > Apologies if this is not the right mailing list. If it is not, please
> > > let me know and I'll switch the thread to the right list.
> > >
> > > Lighbend [1], the company that maintains the popular open source
> > > framework, Akka [2], recently announced they are moving Akka to a
> > > non-OSS commercial license [3].
> > >
> > > There is interest in the OSS community in forking Akka under a new
> > > name and maintaining it as an ASF project [4].
> > >
> > > It is early days yet but there is some discussion online [5].
> > >
> > > Reading the incubator cookbook, a new podling would need to have
> > > champions and mentors from within the Incubator PMC [6].
> > >
> > > I would like to put my name forward for such a role, as an existing
> > > ASF member [7].
> > >
> > > If anyone else in the Incubator PMC would like to get involved, that
> > > would be great.
> > >
> > > Regards,
> > > PJ
> > >
> > > [1] https://www.lightbend.com/
> > > [2] https://akka.io/
> > > [3] https://www.lightbend.com/akka/license-faq
> > > [4] https://github.com/mdedetrich/akka-apache-project
> > > [5] https://github.com/mdedetrich/akka-apache-project/discussions/9
> > > [6] 
> > > https://incubator.apache.org/cookbook/#does_our_project_fit_the_apache_incubator
> > > [7] https://whimsy.apache.org/roster/committer/fanningpj
> > >
> > > -
> > > 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
> >
>
> -
> 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: [DISCUSS] Incubating Proposal for Pekko

[PJ Fanning]

Thanks Tison,
Would you be in a position to do the notice email for Charles and me
(to the board mailing list)?

Regards,
PJ



On Thu, 29 Sept 2022 at 18:26, tison  wrote:
>
> Hi Claude,
>
> Thanks for starting this discussion! +1 to this proposal.
>
> It answers my previous questions on
> https://lists.apache.org/thread/hdknoyvr9c0d4j70xqw6t2t7gnbzc7nq a new
> name + a clear goal.
>
> I'm interested to act as a mentor to help with this podling's growth.
>
> w.r.t the membership, I notice that Claude Warren and PJ Fanning are listed
> on both initial committers and mentors, while other mentors don't. Perhaps
> you should check what's the intention here.
>
> Also, Claude Warren (you) and PJ Fanning are Apache members who can become
> IPMC members with a notice, but it still needs to go through the
> process[1][2].
>
> Best,
> tison.
>
> [1]
> https://incubator.apache.org/guides/roles_and_responsibilities.html#incubator_project_management_committee_ipmc
> [2] https://lists.apache.org/thread/t6k3mg97pyshzoxzjg4c62n166l3crcw
>
>
>
> Jean-Baptiste Onofré  于2022年9月29日周四 23:36写道：
>
> > Hi Claude
> >
> > Very interesting. I would be more than happy to mentor this podling (if
> > accepted of course).
> >
> > I will take a deeper look on the proposal wiki page.
> >
> > Thanks !
> >
> > Regards
> > JB
> >
> > Le jeu. 29 sept. 2022 à 16:57, Claude Warren, Jr
> >  a écrit :
> >
> > > Greetings,
> > >
> > > I would like to propose Pekko [1]  as a new Apache Incubator project.
> > >
> > > Pekko is a toolkit that brings the actor model (popularised by Erlang) to
> > > the JVM, providing the basis for building both locally and distributed
> > > concurrency. On top of this Pekko provides a rich set of libraries built
> > on
> > > top of Actors to solve modern problems, including:
> > >
> > >
> > >- Streams: Fully bi-directional backpressured streams following the
> > >Reactive manifesto
> > >- HTTP: A fully streamed HTTP client/server built on top of streams
> > that
> > >also provides expected tools (such as connection pooling) necessary
> > for
> > >highly available web services
> > >- connectors: A rich set of connectors for various databases,
> > messaging,
> > >persistent services built on top of streams
> > >- grpc: A gRPC server/client
> > >- projection: Provides abstractions necessary for CQRS pattern such as
> > >envelope, necessary for systems such as Kafka.
> > >
> > >
> > >
> > > Controversially Pekko is a fork of the Akka project just prior to its
> > > licence changed from Apache 2 to Business Source License 1.1.
> > >
> > > I look forward to your feedback and discussions,
> > >
> > > Thank you,
> > > Claude Warren
> > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal
> > >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Incubating Proposal for Pekko

[PJ Fanning]

Thanks Chesnay for clarifying the Flink team's position on this.
Since many companies and OSS projects are in a similar position, does
the Flink team have any documentation on the alternatives to Akka that
you're looking at?

Feel free to ignore the suggestion but the volunteers for the Pekko
include a number of major Akka contributors but would the Flink team
consider helping to get Pekko up and running? It may be that there is
less effort involved in getting Pekko released than rewriting a large
part of Flink.

Regards,
PJ

On Wed, 5 Oct 2022 at 15:45, Chesnay Schepler  wrote:
>
> Hello,
>
> since Flink is mentioned several times in the proposal I feel the need to 
> point out that we're actively looking into outright replacing Akka.
>
> We need something that is guaranteed to work once the 2.6.x support provided 
> by Lightbend ends next year, and with Akka being used in the very core of 
> Flink this transition has to start early.
> We can't really take a gamble on this fork still being active/useful in a 
> year.
>
> My current expectation is that we'd only use Pekko as an emergency 
> replacement for older releases when the Lightbend support ends and a critical 
> issue was found (which is quite unlikely to be honest).
>
> On 2022/09/29 14:57:56 "Claude Warren, Jr" wrote:
> > Greetings,
> >
> > I would like to propose Pekko [1]  as a new Apache Incubator project.
> >
> > Pekko is a toolkit that brings the actor model (popularised by Erlang) to
> > the JVM, providing the basis for building both locally and distributed
> > concurrency. On top of this Pekko provides a rich set of libraries built on
> > top of Actors to solve modern problems, including:
> >
> >
> >- Streams: Fully bi-directional backpressured streams following the
> >Reactive manifesto
> >- HTTP: A fully streamed HTTP client/server built on top of streams that
> >also provides expected tools (such as connection pooling) necessary for
> >highly available web services
> >- connectors: A rich set of connectors for various databases, messaging,
> >persistent services built on top of streams
> >- grpc: A gRPC server/client
> >- projection: Provides abstractions necessary for CQRS pattern such as
> >envelope, necessary for systems such as Kafka.
> >
> >
> >
> > Controversially Pekko is a fork of the Akka project just prior to its
> > licence changed from Apache 2 to Business Source License 1.1.
> >
> > I look forward to your feedback and discussions,
> >
> > Thank you,
> > Claude Warren
> > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal
> >
>
> -
> 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

package names (pekko related)

[PJ Fanning]

Hi everyone,

I'm creating a new thread to avoid filling the Pekko thread with emails that 
are only partially related to the proposal.

The current Akka code uses packages that start with 'akka.' and a lot of the 
people involved with Pekko seem to prefer to keep the use 'pekko.' instead of 
'org.apache.pekko.' when we rename the Akka packages.

Kafka and Netbeans are examples of Apache projects that don't use 'org.apache' 
prefix in their package names.

Is 'pekko.' a viable option or is there a strong preference within the ASF and 
the Incubator PMC for 'org.apache.pekko.'?

Regards,
PJ

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Pekko into the Apache Incubator

[PJ Fanning]

h we would like, we
> > believe that it will continue to grow as we move forward.
> >
> > *Core Developers:*
> >
> > The individuals on the committer list are ones who have a history of
> > contributing to the Akka project before the licence change as well as
> > individuals that participated in community discussion on various Akka
> > forums (i.e. Lightbend forums). In addition the individuals have a history
> > of working and contributing to open source projects.
> >
> > Sean Glover is a former member of the Akka team. He primarily maintained
> > Akka Streams and related projects Alpakka and Alpakka Kafka. He currently
> > uses Akka on the job and in other OSS projects he maintains.
> >
> > Phillip Warburton feels he is not enough of an expert to contribute code
> > but is interested in contributing in to document clean-room fixes.
> >
> > Andy Chen is a contributor on Akka and his work is based on the Akka
> > libraries.
> >
> > Jean-Luc Deprez works on a small team, mid sized software company,
> > subsidiary of a large corporate group. His team built a project on top of
> > Akka. The September 7th licence change came as a pretty hard personal blow.
> > He will divert his community participation this way, contributing in
> > discussions and issues. If the team figure out a fix, you can count on a PR.
> >
> > Greg Methvin is a maintainer on Play Framework (which is now
> > community-maintained). We are evaluating whether this can serve as a
> > replacement for Lightbend Akka going forward, as opposed to moving off Akka
> > entirely.
> >
> > Nicolas Vollmar is a maintainer on the akka-kryo-serialization project.
> >
> > PJ Fanning maintains a few akka related projects: swagger-akka-http and
> > micrometer-akka.
> >
> > Daniel Schröter is a maintainer of the akka-kryo-serialization project.
> > Altoo is using akka and has been regularly submitting bugfixes/improvements
> > to akka.
> >
> > Josep Prat is the top 5 contributor of the Akka HTTP module and did all
> > contributions during his spare time, also he is in position 45 of all time
> > committers in the Akka project.
> >
> > Matthew de Detrich is a contributor to both Akka and Alpakka, submitting
> > extra feature improvements as well as the wider Scala OS ecosystem in
> > general (i.e. contributions to Scala stdlib itself, Scalatest etc etc).
> > Most of these contributions were done in his spare time.
> >
> > Alexandru Nedelcu created Monix which is one of the popular
> > reactive/future/IO implementation used within the Scala ecosystem that
> > adheres to the Reactive Streams protocol. He is a very prolific contributor
> > to the Scala OS ecosystem, having been previously part of the Typelevel
> > steering committee and also happens to works at a company that heavily uses
> > Akka for its payment systems.
> >
> > Johannes Rudolph is a major contributor to akka and the lead developer for
> > akka-http.
> >
> > *Alignment:*
> >
> > Apache Flink is using Akka however they are looking for a replacement due
> > to the licence change. We expect that other Apache projects will require
> > the same.
> >
> > We believe that we can be a good community member.
> >
> >
> > *Known RisksProject Name*
> >
> > Several names were floated to replace the Akka name. There was a community
> > discussion and vote around the name
> >
> > We have selected the name Pekko after a vote on candidate names. Akka is
> > the Finnish goddess of fertility and the earth. Pekko is the FInnish god of
> > farming & protector of the crops which create a nice analogy in a sense. We
> > pronounce the name Peck-O.
> >
> > A search of the WIPO database and EU IPO Search did not turn up any active
> > Nice category 9 trademark registrations containing the phrase “pekko”. All
> > results were “pekko” compounded with other phrases.
> >
> > *Orphaned products*
> >
> > Pekko provides libraries that are used by major companies, Apache
> > projects, and individuals. The initial development team comprises
> > representatives from these organisations. We believe that Pekko will
> > attract open source developers that have contributed to Akka in the past
> > and want to see their work continue to be open source. We are here, not
> > because we are a potentially orphaned product, but rather because the
> > contributors to the existing product want to see the open source project
> > continue.
> >
> > *Inexperience with Open Source:*
> >
> &g

Apache license in source files (pekko)

[PJ Fanning]

Thanks everyone for supporting Pekko's application to join the Incubator.

I have a question about the licenses that appear in the source files.

Do we need to replace the Lightbend copyright at the top of the Pekko source 
files [1] with the generic Apache license [2]? Or would we use an Apache 
license that acknowledges the Lightbend copyright (ending in 2022)?

The LICENSE and NOTICE files that we include in git and in the release 
artifacts will include an acknowledgment of the Lightbend copyright. I've just 
never seen any ASF source files that have such a copyright.

Any guidance will be appreciated.

Regards,
PJ

[1] 
https://github.com/mdedetrich/akka-apache/blob/6680c47dcc2305906a44d7794081682211d7ee0b/akka-actor/src/main/scala/akka/actor/AbstractActor.scala
[2] 
https://github.com/apache/poi/blob/trunk/poi/src/main/java/org/apache/poi/POIDocument.java

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Apache license in source files (pekko)

[PJ Fanning]

Thanks Justin and Roman.

We'll leave the Lightbend licenses alone.

If there are significant modifications to an existing file, we will adjust the 
license comment to be an Apache license but also ackoweldge the pre-existing 
Lightbend license. 

Any new files will just get a standard Apache license.

On 2022/10/25 10:18:10 Roman Shaposhnik wrote:
> On Tue, Oct 25, 2022 at 8:39 AM Justin Mclean  
> wrote:
> >
> > Hi,
> >
> > I would perhaps change the headers to be the 3rd party ASF header with the 
> > copyright line to make it clear each file is under the Apache license.
> 
> What Justin said ;-)
> 
> Thanks,
> Roman.
> 
> P.S. Of course, all the new files we start creating should have a
> standard ASF header.
> 
> -
> 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: [DISCUSS] Graduate Apache Linkis(incubating) as an Apache Top Level Project

[PJ Fanning]

I agree that Linkis is ready to graduate. The community is well established and 
there was a large vote within that community to support this move [1].
I am a Linkis committer and recently joined the Incubator PMC. 

[1] https://lists.apache.org/thread/tnp165hs0k9rvntqz2f025sxsjlk6xsf

On 2022/11/23 07:34:10 david zollo wrote:
> +1
> As a mentor of Linkis, glad to see a diverse community being built, I think
> this project podling is ready
> to graduate from the incubator.
> 
> 
> 
> Best Regards
> 
> ---
> Apache DolphinScheduler PMC Chair & Apache SeaTunnel PPMC
> David
> Linkedin: https://www.linkedin.com/in/davidzollo
> Twitter: @WorkflowEasy 
> ---
> 
> 
> On Mon, Nov 21, 2022 at 10:44 PM ShaoFeng Shi 
> wrote:
> 
> > As one of Linkis's mentor, I see how the Linkis community growed up under
> > the Apache Way. The community is active, diversed, and the project is well
> > maintained by a group of young engineers. Each time when an issue be
> > addressed, it can be resolved quickly. I think the Linkis podling is ready
> > to graduate from the incubator.
> >
> > Best regards,
> >
> > Shaofeng Shi 史少锋
> > Apache Kylin PMC,
> > Apache Incubator PMC,
> > Email: shaofeng...@apache.org
> >
> > Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> > Join Kylin user mail group: user-subscr...@kylin.apache.org
> > Join Kylin dev mail group: dev-subscr...@kylin.apache.org
> >
> >
> >
> >
> > Shuai Di  于2022年11月21日周一 00:01写道：
> >
> > > Dear Apache Incubator Community,
> > >
> > > Apache Linkis has been incubating [1] since 2021-08-02 for over 15
> > > months. The Linkis community has grown rapidly under the guidance of
> > > mentors and the Apache Way. After self-checking the Linkis maturity
> > > model [2] and having discussion [3], we started a vote [4] for
> > > graduation within the Linkis community and got unanimous positive
> > > feedback [5]. We believe Apache Linkis (Incubating) is now ready to
> > > graduate to be a Top Level Project. We'd like to have a discussion
> > > with the incubator community and get more feedback.
> > >
> > > Here is an overview of the Apache Linkis(incubating) to help with the
> > > discussion.
> > >
> > > *Community*
> > >
> > > ● 4 new PPMC members were added, bringing the total number of PPMC
> > > members to 24 from 15 different organizations.
> > > ● 13 new committers were added(including the new PPMC members),
> > > bringing the total number of committers to 33 from 21 different
> > > organizations.
> > > ● 79 new contributors. The number of contributors is now 128 and growing.
> > > ● 20 biweekly online meetings were held in the community among PPMC
> > > members, committers, contributors, and users. The meeting minutes are
> > > recorded on the cwiki and mailing list [6][7].
> > > ● The dev@linkis mailing list currently has 113 subscribers.
> > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > > discussion at private@linkis [8]. Shuai Di(shua...@apache.org) was
> > > voted as Vice President.
> > >
> > > *Project*
> > >
> > > ● Apache Linkis(incubating) builds a computation middleware layer to
> > > facilitate connection, governance and orchestration between the upper
> > > applications and the underlying data engines.
> > > ● Linkis community released a total of 7 Apache releases [9] by 7
> > > different release managers from 6 different organizations.
> > > ● 1935 pull requests created, and 1894 pull requests closed [10].
> > > ● 1488 issues created, and 1271 issues closed [11].
> > > ● The release cadence is about 2 months, with an average of 200+
> > > issues and 270+ pull requests per release.
> > >
> > > *Brands, License, and Copyright*
> > >
> > > ● We submitted an application for the brand [12] and it has been
> > > reviewed and approved.
> > > ● Linkis community maintains project code on GitHub and all modules
> > > code is under Apache 2.0 license. We have reviewed all the
> > > dependencies and ensured they do not bring any license issues [13].
> > > All the status files, license headers, and copyright are up to date.
> > > ● Linkis official website [14] is compliant with Apache Foundation
> > > requirements.
> > >
> > > -
> > > BEGINNING OF DRAFT RESOLUTION
> > > -
> > >
> > > Establish the Apache Linkis Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests
> > > of the Foundation and consistent with the Foundation's purpose to
> > > establish a Project Management Committee charged with the creation and
> > > maintenance of open-source software, for distribution at no charge to
> > > the public, related to a distributed and computation middleware to
> > > facilitate connection, governance, and orchestration between the upper
> > > applications and the underlying data engines.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a 

Re: [VOTE] Graduate Apache Linkis(incubating) as an Apache Top Level Project

[PJ Fanning]

+1 (binding)

Linkis is in a good place to become a TLP.

Thanks Shuai Di for leading the discussion.

On Sun, 27 Nov 2022 at 11:18, Shuai Di  wrote:
>
> Dear Apache Incubator Community and IPMC members,
>
> After having the graduation discussion in the Linkis community [1], we
> have passed the vote within Linkis community [2] and the vote result
> was published[3].
> We then discussed the graduation for Linkis in the Apache Incubator
> Community [4], where no issues were raised and positive replies were
> received.
>
> I would like to start this voting thread to request graduating Apache
> Linkis(incubating) from Apache Incubator as a Top Level Project.
>
> Please provide your vote accordingly:
> [ ] +1 Yes, I support Linkis project to graduate from the Apache Incubator.
> [ ] +0 No opinion.
> [ ] -1 No, the Linkis 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 Linkis(incubating) to help with the
> vote.
>
> *Community*
>
> ● 4 new PPMC members were added, bringing the total number of PPMC
> members to 24 from 15 different organizations.
> ● 13 new committers were added(including the new PPMC members),
> bringing the total number of committers to 33 from 21 different
> organizations.
> ● 79 new contributors. The number of contributors is now 128 and growing.
> ● 21 biweekly online meetings were held in the community among PPMC
> members, committers, contributors, and users. The meeting minutes are
> recorded on the cwiki and mailing list [5].
> ● The dev@linkis mailing list currently has 113 subscribers [6].
> ● We've confirmed the VP, PMC, and Committers in the preparation
> discussion at private@linkis [7]. Shuai Di(shua...@apache.org) was
> voted as Vice President.
>
> *Project*
>
> ● Apache Linkis(incubating) builds a computation middleware layer to
> facilitate connection, governance and orchestration between the upper
> applications and the underlying data engines.
> ● Project maturity model is detailed in [8]
> ● Linkis has been incubating [9] since 2021-08-02 for over 15
> months.
> ● Linkis community released a total of 7 Apache releases [10] by 7
> different release managers from 6 different organizations.
> ● 1935 pull requests created, and 1894 pull requests closed [11].
> ● 1488 issues created, and 1271 issues closed [12].
> ● The release cadence is about 2 months, with an average of 200+
> issues and 270+ pull requests per release.
> ● Please refer to the Linkis project incubation status [13][14] for more
> information.
>
> *Brand, License, and Copyright*
>
> ● We submitted an application for the brand [15] and it has been
> reviewed and approved.
> ● Linkis community maintains project code on GitHub and all modules
> code is under Apache 2.0 license. We have reviewed all the
> dependencies and ensured they do not bring any license issues [16].
> All the status files, license headers, and copyright are up to date.
> ● Linkis official website [17] is compliant with Apache Foundation
> requirements [18].
>
> -
> BEGINNING OF DRAFT RESOLUTION
> -
>
> Establish the Apache Linkis Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests
> of the Foundation and consistent with the Foundation's purpose to
> establish a Project Management Committee charged with the creation and
> maintenance of open-source software, for distribution at no charge to
> the public, related to a distributed and computation middleware to
> facilitate connection, governance, and orchestration between the upper
> applications and the underlying data engines.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Linkis Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Linkis Project be and hereby is responsible
> for the creation and maintenance of software related to a computation
> middleware to facilitate connection, governance and orchestration
> between the upper applications and the underlying data engines; and be
> it further
>
> RESOLVED, that the office of "Vice President, Apache Linkis" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Linkis
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Linkis
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Linkis
> Project:
>
>  ●  Alex Young 
>  ●  Deyi Hua 
>  ●  Duo Zhang 
>  ●  HuaJin Zhang 
>  ●  Hui Zhu 
>  ●  Jacky Xie 
>  ●  Jerry Shao 
>  ●  Junping Du 
>  ●  Ke Zhou 
>  ●  Kelu Tao 
>  ●  Le Bai 
>  ●  Lido

Re: [DISCUSS] KIE Proposal

[PJ Fanning]

Is it possible the name is too generic and could cause confusion with
this existing ASF project?

* https://kie.readthedocs.io/en/latest/
* https://github.com/apache/servicecomb-kie

On Thu, 1 Dec 2022 at 22: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
>
> 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 cloud-native environment and tooling 
> is made available through KIE Tools.
>
> Background
>
> Experience has shown that a holistic approach is a practical requirement for 
> any  knowledge engineering and process automation. This requires a breadth of 
> capabilities able to model and execute an application’s data models, rules, 
> workflows, and events. These projects aim to provide a holistic approach with 
> a strong emphasis on congruency across them.
>
> Rationale
>
> Knowledge engineering and process automation have been and continue to play a 
> large part in today’s software lifecycle. To date, there have been few truly 
> open-source implementations of any of the specifications (DMN, PMML, BPMN, 
> CNCF Workflow, etc). The projects within Red Hat implement these standards 
> and fill that gap of having an open-source implementation.
>
>
> The projects within KIE also mesh well with other Apache projects such as 
> Apache Camel and Apache Airavata. Integrations could be done at the IoT level 
> with Apache PLC4X and others.
>
>
> Developers need a solution that follows, implements, and collaborates with 
> these industry specifications. The Apache Software Foundation would allow 
> these projects to continue to grow in a vendor-neutral environment and 
> promote further collaboration with existing integrations and future partners.
>
> Initial 
> Goals
>
> First and foremost, we aim to enlarge the community. KIE has primarily been 
> an open-source community of Red Hat Developers and users outside of Red Hat. 
> Adding IBM to the list of developers helps, but we would like to see more. We 
> have ideas for the various sub-projects, such as straight-through processing 
> support in Kogito, better spec compliance for the tooling, and more research 
> into language bindings for non-Java languages. We believe we can address some 
> of these while an Apache Incubator project.
>
> Current 
> Status
>
> Code for the various projects with the KIE community is all hosted on GitHub. 
> This includes Kogito, Drools, jBPM, and KIE Tools. All of the code is Apache 
> 2 licensed. Red Hat has been the project’s custodian since its inception and 
> has maintained leadership in that area. Moving forward into the Apache 
> Incubator, we would need to establish the habit of holding votes and meetings 
> and the project updates per the Apache Way.
>
>
> We also currently maintain a YouTube channel dedicated to the community and 
> projects, a Twitter presence, and a LinkedIn page for the KIE Community.
>
> Meritocracy:
>
> Red Hat runs all of its open-source projects as meritocracies, the KIE 
> Community is no different. This aspect would not change any. Kogito currently 
> does not make a distinction between “committer” and “PMC member” the same way 
> Apache does. That aspect would need implementation.
>
> Community:
>
> The KIE Community has an active base of contributors within and outside Red 
> Hat. Community mem

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

[PJ Fanning]

+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 project code on GitHub, and all
> > > modules
> > > code is under Apache 2.0 license. We have reviewed all the
> > > dependencies and ensured they do not bring any license issues [11]. All
> > > the status files, license headers, and copyright are up to date.
> > >
> > > ** PPMC members
> > >
> > > * Please see the proposed board resolution below and let us know what you
> > > think. The initial PMC members were passed by the vote [5] and the result
> > > was also announced [6].
> > >
> > > * affiliations of the current PPMC members of Sedona: 11 PPMC from 10
> > > different organizations
> > > Adam Binford: Maxar
> > > Kanchan Chowdhury: Arizona State University
> > > Paweł Kociński: GetInData
> > > Yitao Li: SafeGraph
> > > Netanel Malka: Upstream Security
> > > Mohame Sarwat: Wherobots Inc.
> > > Kengo Seki: NTT Data
> > > Sachio Wakai: KDDI
> > > Jinxuan Wu: Bloomberg LP
> > > Jia Yu: Wherobots Inc.
> > > Zongsi Zhang: Grab
> > >
> > > * new PPMC members since incubation: 5
> > > Adam Binford: Maxar
> > > Kanchan Chowdhury: Arizona State University
> > > Yitao Li: SafeGraph
> > > Sachio Wakai: KDDI
> > > Kengo Seki: NTT Data
> > >
> > > * Pending new PPMC members (due to pending CCLAs): 1
> > > Magdalena Wójciak: Billennium
> > >
> > > ** Graduation Resolution **
> > >
> > > Establish the Apache Sedona Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > the Foundation and consistent with the Foundation's purpose to establish
> > > a Project Management Committee charged with the creation and maintenance
> > > of open-source software, for distribution at no charge to the public,
> > > related to a big geospatial data processing engine. It provides an easy
> > > to use APIs for spatial data scientists to manage, wrangle, and process
> > > geospatial data.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache Sedona Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Sedona Project be and hereby is r

Re: Looking for a Champion: FuzzyLite

[PJ Fanning]

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

Fwd: Looking for a Champion: FuzzyLite

[PJ Fanning]

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: [VOLUNTEER WANTED]Incubator Shepherds

[PJ Fanning]

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

Re: DB2DOM

[PJ Fanning]

Thanks John for your interest in submitting your code to the ASF and
building a project team to maintain and release it.

You might want to read the Incubator Cookbook [1]  to become
acquainted with the processes we use.

The Pekko Proposal [2] is an example of a project that was accepted to
become an Incubator podling.

Would you be able to share your source code with us so that we can
have a look at it? All I found was a web site describing your tools at
a high level [3].

Do you have anyone else that has contributed code in the past and who
would be interested in continuing? One of the key features of an ASF
project is building a community.

Regards,
PJ

[1] https://incubator.apache.org/cookbook/
[2] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal
[3] https://db2dom.com/

On Wed, 21 Dec 2022 at 13:15, jcdale  wrote:
>
> Greetings;
>
> Please see below.
>
> Let's start there.
>
> Who is interested in meeting up with me that might be interested in 
> incubating this project and helping scratch back some lost Java folks and 
> bringing in some sysadmin folks to Java who might currently prefer Python etc?
>
> Sincerely,
>
> John
>
>
>
>
>
> --- Original Message ---
> On Wednesday, December 21st, 2022 at 3:39 AM, Mark Thomas  
> wrote:
>
>
> >
> >
> > John,
> >
> > The way to bring a project to the ASF is through the incubator. Lots of
> > useful information available at:
> >
> > https://incubator.apache.org/
> >
> > general@incubator.apache.org is the place to ask any questions.
> >
> > Mark
> >
> >
> > On 20/12/2022 13:25, jcdale wrote:
> >
> > > Hi Mark and Chris;
> > >
> > > Disclosure: I am on the list as jcdw...@gmail.com
> > >
> > > First off thanks for all the help through the years and all of your work
> > > on Tomcat.
> > >
> > > I have a software doodad that I would like to consider putting forward
> > > as an ASF project.
> > >
> > > Can I demo this for you and get your advice about how to proceed? I
> > > have very limited time and resources and need help (it took me over a
> > > decade to finally get the s/w to this point).
> > >
> > > I've attached my resume to help build some credibility (I found out last
> > > week that we won the SD Congressional App Challenge again this year,
> > > both apps were built on DB2DOM). Here is the 2022 winning entry:
> > > https://www.youtube.com/watch?v=-mNxGUkmCug&t=2s
> > > https://www.youtube.com/watch?v=-mNxGUkmCug&t=2s
> > >
> > > I'd like to see Java return to #1, and I think DB2DOM could do it.
> > >
> > > I believe the adoption curve would be very, very short, and may address
> > > some of the reasons so many people jumped to Python (this is unfortunate
> > > for Java, still a really great programming language with amazing
> > > institutional knowledge stored-up with talented people like us).
> > >
> > > Sincerely,
> > >
> > > John
>
> -
> 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: [DISCUSS] KIE Proposal

[PJ Fanning]

Could we get the proposal doc up on the ASF wiki?

On Tue 3 Jan 2023, 17:25 Jason Porter,  wrote:

> Sounds like there aren’t any further questions, but I can appreciate
> people just getting back to work from the end of the year. I’ll give it
> another day before we move on to the next stage, which I believe is a call
> for a vote, correct?
>
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>
> On Dec 23, 2022, at 09:20, Jason Porter  wrote:
>
> Are there any further questions anyone has about KIE? I know we're nearing
> the end of the year and people may not be watching as closely, but wanted
> to make sure since the discussion has died down.
>
> If there are no further questions, are we able to go to a vote?
> 
> From: Jason Porter 
> Sent: Tuesday, December 13, 2022 08:37
> To: general@incubator.apache.org 
> Subject: [EXTERNAL] RE: [DISCUSS] KIE Proposal
>
>
>
> 
> From: Calvin Kirs 
> Sent: Monday, December 12, 2022 23:31
> To: general@incubator.apache.org 
> Subject: [EXTERNAL] Re: [DISCUSS] KIE Proposal
>
> On Fri, Dec 9, 2022 at 11:45 PM Jason Porter 
> wrote:
>
> We don’t feel like KIE and Servicecomb-kie clash. One is an acronym (KIE-
> Knowledge Is Everything), and the other is a suffix. Both projects are very
> different as well. Servicecomb-kie is a configuration center for
> microservices written in Go, whereas KIE is a knowledge engineering and
> process automation solution written in Java. For example, how was this
> handled in the context of Apache DeltaCloud and Apache DeltaSpike; or
> Apache DataFu and Apache DataLab? Is there precedence within the ASF for
> similarly named projects? The two communities have also co-existed for
> roughly the same time, using the same names without clashes.
>
> That's not a problem If two projects are in different fields.
> we'd just need to be careful with the project description.
>
> Perfect! Thank you, Calvin.
>
>
>
> As was stated previously, the number of projects is much smaller than the
> number of GitHub repos. This is because KIE did not use a singular
> repository model within the GitHub organization. The projects we’re
> currently considering in this proposal are Kogito, jBPM, Drools, KIE-Tools,
> and another project for the CNCF Serverless Workflow implementation that is
> going through a naming process now. KIE-Tools is a little odd, though, as
> it doesn’t stand on its own well. The existing code base contains a lot of
> modules and code, which could be considered legacy, which we do not plan to
> move over. There will be a cleaning and pruning process to ensure a more
> relevant, sustainable, and forward-looking set of modules as code is moved
> over. This should further reduce the amount of code that is moved over. We
> understand we may need to collapse the repositories moving over to the ASF.
> Let us know if you want to see how everything rolls into a more flat
> structure.
>
>
> Regarding umbrella versus standalone projects, we believe that the unified
> and cohesive experience provides more value than just the sum of its parts.
> This is also not just about where we are now, but where we hope to evolve
> as a knowledge engineering platform. On the surface, those projects can be
> seen as independent in their business rules, decisions, and workflow
> domains. However, real-world use cases are more complex. Usually, they
> require a lot of interdependencies, for example, business rules
> orchestration is accomplished by using a workflow file definition (i.e.,
> BPMN), and complex workflow decisions are better modeled in DMN models. The
> aim is to try and drive consistency and ease of use across those
> technologies, in an integrated and holistic manner.
>
>
> If those projects end up as individual TLPs, it'll be up to users to write
> a lot of boiler-plate code - or create additional new projects to handle
> and abstract the unified experience.
>
>
> Of course, as a consequence of the unified vision, the current codebase is
> taking advantage of this unification, which means there's a lot of shared
> code among the projects. Moving away from this will also result in more
> top-level supporting projects to provide additional code, needed as
> foundational code or integration code, which may actually create more
> complexity and end-user confusion.
>
>
>
> Although it might not be the most popular example within Apache, KIE aims
> to provide a similar umbrella cohesiveness that Apache OpenOffice has for
> their sub-projects like Write and Calc. We really want the community to
> think of knowledge engineering as a whole domain of technologies for
> problem-solving, and not on individual silo technologies.
>
>
> Lastly, fracturing the community we have already created around the KIE
> brand and concept is certainly not ideal and will weaken the overall
> project brands and success. We believe we'll be able to leverage further
> what we currently have in the community a

Re: [DISCUSS] KIE Proposal

[PJ Fanning]

I did some of the wikification of the email but it's pretty time
consuming and I want to finish up for the evening.

The main item remaining is to put all the initial committers into the table.

On Tue, 3 Jan 2023 at 19:26, Jason Porter  wrote:
>
> I was just going to do this but looks like you beat me to it, PJ, thank you.
>
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>
> On Jan 3, 2023, at 09:42, PJ Fanning  wrote:
>
> This Message Is From an External Sender
> This message came from outside your organization.
> Could we get the proposal doc up on the ASF wiki?
>
> On Tue 3 Jan 2023, 17:25 Jason Porter,  wrote:
>>
>> Sounds like there aren’t any further questions, but I can appreciate people 
>> just getting back to work from the end of the year. I’ll give it another day 
>> before we move on to the next stage, which I believe is a call for a vote, 
>> correct?
>>
>> Jason Porter
>> Software Engineer
>> He/Him/His
>>
>> IBM
>>
>> On Dec 23, 2022, at 09:20, Jason Porter  wrote:
>>
>> Are there any further questions anyone has about KIE? I know we're nearing 
>> the end of the year and people may not be watching as closely, but wanted to 
>> make sure since the discussion has died down.
>>
>> If there are no further questions, are we able to go to a vote?
>> 
>> From: Jason Porter 
>> Sent: Tuesday, December 13, 2022 08:37
>> To: general@incubator.apache.org 
>> Subject: [EXTERNAL] RE: [DISCUSS] KIE Proposal
>>
>>
>>
>> 
>> From: Calvin Kirs 
>> Sent: Monday, December 12, 2022 23:31
>> To: general@incubator.apache.org 
>> Subject: [EXTERNAL] Re: [DISCUSS] KIE Proposal
>>
>> On Fri, Dec 9, 2022 at 11:45 PM Jason Porter  wrote:
>>
>> We don’t feel like KIE and Servicecomb-kie clash. One is an acronym (KIE- 
>> Knowledge Is Everything), and the other is a suffix. Both projects are very 
>> different as well. Servicecomb-kie is a configuration center for 
>> microservices written in Go, whereas KIE is a knowledge engineering and 
>> process automation solution written in Java. For example, how was this 
>> handled in the context of Apache DeltaCloud and Apache DeltaSpike; or Apache 
>> DataFu and Apache DataLab? Is there precedence within the ASF for similarly 
>> named projects? The two communities have also co-existed for roughly the 
>> same time, using the same names without clashes.
>>
>> That's not a problem If two projects are in different fields.
>> we'd just need to be careful with the project description.
>>
>> Perfect! Thank you, Calvin.
>>
>>
>>
>> As was stated previously, the number of projects is much smaller than the 
>> number of GitHub repos. This is because KIE did not use a singular 
>> repository model within the GitHub organization. The projects we’re 
>> currently considering in this proposal are Kogito, jBPM, Drools, KIE-Tools, 
>> and another project for the CNCF Serverless Workflow implementation that is 
>> going through a naming process now. KIE-Tools is a little odd, though, as it 
>> doesn’t stand on its own well. The existing code base contains a lot of 
>> modules and code, which could be considered legacy, which we do not plan to 
>> move over. There will be a cleaning and pruning process to ensure a more 
>> relevant, sustainable, and forward-looking set of modules as code is moved 
>> over. This should further reduce the amount of code that is moved over. We 
>> understand we may need to collapse the repositories moving over to the ASF. 
>> Let us know if you want to see how everything rolls into a more flat 
>> structure.
>>
>>
>> Regarding umbrella versus standalone projects, we believe that the unified 
>> and cohesive experience provides more value than just the sum of its parts. 
>> This is also not just about where we are now, but where we hope to evolve as 
>> a knowledge engineering platform. On the surface, those projects can be seen 
>> as independent in their business rules, decisions, and workflow domains. 
>> However, real-world use cases are more complex. Usually, they require a lot 
>> of interdependencies, for example, business rules orchestration is 
>> accomplished by using a workflow file definition (i.e., BPMN), and complex 
>> workflow decisions are better modeled in DMN models. The aim is to try and 
>> drive consistency and ease of use across those technologies, in an 
>> integrated and holistic manner.
>>
>>
>> If those project

Re: [DISCUSS] KIE Proposal

[PJ Fanning]

https://cwiki.apache.org/confluence/display/INCUBATOR/KIE+Proposal is
the work in progress page.

On Tue, 3 Jan 2023 at 19:53, PJ Fanning  wrote:
>
> I did some of the wikification of the email but it's pretty time
> consuming and I want to finish up for the evening.
>
> The main item remaining is to put all the initial committers into the table.
>
> On Tue, 3 Jan 2023 at 19:26, Jason Porter  wrote:
> >
> > I was just going to do this but looks like you beat me to it, PJ, thank you.
> >
> > Jason Porter
> > Software Engineer
> > He/Him/His
> >
> > IBM
> >
> > On Jan 3, 2023, at 09:42, PJ Fanning  wrote:
> >
> > This Message Is From an External Sender
> > This message came from outside your organization.
> > Could we get the proposal doc up on the ASF wiki?
> >
> > On Tue 3 Jan 2023, 17:25 Jason Porter,  wrote:
> >>
> >> Sounds like there aren’t any further questions, but I can appreciate 
> >> people just getting back to work from the end of the year. I’ll give it 
> >> another day before we move on to the next stage, which I believe is a call 
> >> for a vote, correct?
> >>
> >> Jason Porter
> >> Software Engineer
> >> He/Him/His
> >>
> >> IBM
> >>
> >> On Dec 23, 2022, at 09:20, Jason Porter  wrote:
> >>
> >> Are there any further questions anyone has about KIE? I know we're nearing 
> >> the end of the year and people may not be watching as closely, but wanted 
> >> to make sure since the discussion has died down.
> >>
> >> If there are no further questions, are we able to go to a vote?
> >> 
> >> From: Jason Porter 
> >> Sent: Tuesday, December 13, 2022 08:37
> >> To: general@incubator.apache.org 
> >> Subject: [EXTERNAL] RE: [DISCUSS] KIE Proposal
> >>
> >>
> >>
> >> 
> >> From: Calvin Kirs 
> >> Sent: Monday, December 12, 2022 23:31
> >> To: general@incubator.apache.org 
> >> Subject: [EXTERNAL] Re: [DISCUSS] KIE Proposal
> >>
> >> On Fri, Dec 9, 2022 at 11:45 PM Jason Porter  
> >> wrote:
> >>
> >> We don’t feel like KIE and Servicecomb-kie clash. One is an acronym (KIE- 
> >> Knowledge Is Everything), and the other is a suffix. Both projects are 
> >> very different as well. Servicecomb-kie is a configuration center for 
> >> microservices written in Go, whereas KIE is a knowledge engineering and 
> >> process automation solution written in Java. For example, how was this 
> >> handled in the context of Apache DeltaCloud and Apache DeltaSpike; or 
> >> Apache DataFu and Apache DataLab? Is there precedence within the ASF for 
> >> similarly named projects? The two communities have also co-existed for 
> >> roughly the same time, using the same names without clashes.
> >>
> >> That's not a problem If two projects are in different fields.
> >> we'd just need to be careful with the project description.
> >>
> >> Perfect! Thank you, Calvin.
> >>
> >>
> >>
> >> As was stated previously, the number of projects is much smaller than the 
> >> number of GitHub repos. This is because KIE did not use a singular 
> >> repository model within the GitHub organization. The projects we’re 
> >> currently considering in this proposal are Kogito, jBPM, Drools, 
> >> KIE-Tools, and another project for the CNCF Serverless Workflow 
> >> implementation that is going through a naming process now. KIE-Tools is a 
> >> little odd, though, as it doesn’t stand on its own well. The existing code 
> >> base contains a lot of modules and code, which could be considered legacy, 
> >> which we do not plan to move over. There will be a cleaning and pruning 
> >> process to ensure a more relevant, sustainable, and forward-looking set of 
> >> modules as code is moved over. This should further reduce the amount of 
> >> code that is moved over. We understand we may need to collapse the 
> >> repositories moving over to the ASF. Let us know if you want to see how 
> >> everything rolls into a more flat structure.
> >>
> >>
> >> Regarding umbrella versus standalone projects, we believe that the unified 
> >> and cohesive experience provides more value than just the sum of its 
> >> parts. This is also not just about where we are now, but where we hope to 
> >> evolve as a knowledge enginee

Re: Looking for a Champion: FuzzyLite

[PJ Fanning]

Hi Juan,
I'm willing to assist with putting together a proposal for admission to the 
Incubator.

You might notice in this Pekko example [1] and other proposals include a team 
of initial contributors. The rules within which Incubator podlings operate 
require that you have at least 3 individuals willing to vote on releases and 
such like.

I still think it might make sense to try to attract some volunteers before 
proceeding with creating the proposal. The Pekko team publicised the project in 
Github and on Social Media and was able to get a number of volunteers in this 
way.

[1] https://cwiki.apache.org/confluence/display/INCUBATOR/PekkoProposal 
[2] https://github.com/mdedetrich/akka-apache-project/discussions/3

Do you think this is an ok way to proceed?

Regards,
PJ



On 2022/12/20 22:23:31 Juan Rada-Vilela wrote:
> 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.
> >
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Are programming languages suitable for Apache?

[PJ Fanning]

Hi everyone,
I think the ASF has proved a good home for a large variety of
different projects. I don't see any reason why a project like Elm
couldn't flourish at the ASF.

One thing to be aware of is that the license on Elm Compiler is BSD
3-clause license [1]. Generally speaking, the ASF would require the
code to be granted to the foundation, including permission to change
over to the Apache 2 license. In a community split scenario, this
might not be feasible.
Maybe someone else with more expertise than me on the implications of
a BSD to Apache license switch can clarify the position.

Regards,
PJ

[1] https://github.com/elm/compiler/blob/master/LICENSE

On Fri, 6 Jan 2023 at 23:28, Dave Fisher  wrote:
>
> Apache Groovy - https://groovy.apache.org/
>
> Sent from my iPhone
>
> > On Jan 6, 2023, at 1:46 PM, Rupert Smith 
> >  wrote:
> >
> > Its been a long time since I was last involved as an Apache committer. Back
> > around 2004ish I contributed to the now defunct qpid project, which was an
> > implementation of the AMQP messaging protocol.
> >
> > These days, I am quite keen on the Elm programming language, but it is not
> > possible to contribute to its compiler+core packages, as only the BDFL
> > there has commit rights. The quality of the software is very high, and
> > there have been very few serious issues since its last release, but always
> > amongst the Elm community there is a recurring sense of frustration that
> > patches are ignored. It would seem eventually that some kind of community
> > fork needs to happen, if businesses using Elm are to feel secure in their
> > adoption of it. For this reason, I and others are exploring options.
> >
> > I like the values of Apache - openness, independance and plurality of
> > contributors - adopting some of the "Apache way" would seem to make sense
> > for a hypothetical fork of Elm.
> >
> > I looked at the list of Apache projects, and noticed that none are
> > programming languages (correct? Apache Harmony as an implementation of Java
> > was one). This also makes me wonder if Apache is a suitable place for such
> > a project. There are benefits to the bus-factor 1 BDFL model - a
> > programming language is a complex thing with sometimes subtle interactions
> > between its language features. Opinions are many, but turning them into a
> > cohesive set of ideas that make up a good language is not easy, so avoiding
> > all the distracting arguments by having things tightly controlled by a
> > single BDFL does make sense, and is not uncommon.
> >
> > On the other hand, what is really needed in this situation is the ability
> > to patch Elm, and to have a well run open source project through which to
> > do so.
> >
> > So I am curious to hear your thoughts on whether Apache is a suitable place
> > for a programming language and compiler project?

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] KIE proposal acceptance

[PJ Fanning]

+1

I've updated the Confluence page to remove the refs to IBM and RedHat.

On Mon, 9 Jan 2023 at 16:35, Jason Porter  wrote:
>
> Looks like I messed up sections. Happy to change, but I don't have edit 
> access to the Wiki. We have the Apache Camel project and Brian Proffit as 
> sponsors for the incubator project.
>
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>
> On Jan 9, 2023, at 08:02, Sheng Wu  wrote:
>
> I noticed the sponsor part of the proposal
>
> Sponsors
> IBM and Red Hat are the sponsors for the project.
>
> I think this sponsor part referring an ASF TLP, which usually be the
> incubator in here or other TLPs.
> These two companies may provide support to the developers, but this is
> not the meaning of the proposal.
>
> Sheng Wu 吴晟
> Twitter, wusheng1108
>
> Antoine Toulme  于2023年1月9日周一 22:58写道：
>
> Here is my +1 (binding). I worked with Drools long time ago and am excited to 
> see KIE take it to the next level!
>
> Cheers,
>
> Antoine
>
> On Jan 9, 2023, at 06:51, Jason Porter  wrote:
>
> I'd like to call a vote for the acceptance of KIE as an Apache Incubator 
> project as the conversation around the proposal has ended. The proposal is 
> available at [1].
>
> [1] https://cwiki.apache.org/confluence/display/INCUBATOR/KIE+Proposal
>
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>
>
>
> -
> 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
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[QUESTION] do pom files need to have a license header

[PJ Fanning]

Hi everyone,

The Apache Pekko builds use the sbt tool for building and this generates pom 
files for us. They do not include any headers (example [1]).
It seems the norm to add an XML comment with Apache License info (example from 
log4j [2]).
Does the Pekko team need to fix this or is it just a nicety to have the license 
header in the pom files? If the answer is that we do need to fix this, does 
this also apply to other published files? sbt generates and publishes a 
'buildinfo' file as part of the maven publish (example [2]).

Regards,
PJ


[1] 
https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.pom
[2] 
https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/2.19.0/log4j-api-2.19.0.pom
[3] 
https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.buildinfo

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[PJ Fanning]

I think this thread might need to be started again. If we are going to
vote, the email subject should be:

[VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

Example: https://lists.apache.org/thread/k9gj4hh2fbrkf41o3211gkt49p87nhvy

My vote is +1 (binding) regardless.

On Mon, 6 Feb 2023 at 16:27, Alex Luo  wrote:
>
> +1 non-binding
>
> Alex Luo
>
> On 2023/02/06 14:09:50 李晓双 wrote:
> > +1 non-binding
> >
> > 李晓双  于2023年2月6日周一 21:05写道：
> >
> > > +1 binding
> > >
> > > peacewong  于2023年2月6日周一 19:48写道：
> > >
> > >> +1 (non-binding)
> > >>
> > >> Congratulations!
> > >>
> > >> Wei Liu  于2023年2月6日周一 19:26写道：
> > >>
> > >> > +1
> > >> >
> > >> > Congratulations!
> > >> >
> > >> > On 2023/02/06 09:27:26 Eason Chen wrote:
> > >> > > Dear Apache Incubator Community,
> > >> > >
> > >> > > Apache EventMesh has been incubating [1] since 2021-02-18 for over 23
> > >> > > months. The EventMesh community has grown rapidly under the guidance
> > >> > > of mentors and the Apache Way. After self-checking the EventMesh
> > >> maturity
> > >> > > model [2] and having a discussion [3], we started a vote [4] for
> > >> > > graduation within the EventMesh community and got unanimous positive
> > >> > > feedback [5]. We believe Apache EventMesh (Incubating) is now ready 
> > >> > > to
> > >> > > graduate to be a Top Level Project. We'd like to have a discussion
> > >> > > with the incubator community and get more feedback.
> > >> > >
> > >> > > Here is an overview of the Apache EventMesh(incubating) to help with
> > >> > > the discussion.
> > >> > >
> > >> > > *Community*
> > >> > >
> > >> > > ● 5 new PPMC members were added, bringing the total number of PPMC
> > >> > > members to 14 from at least 9 different organizations.
> > >> > > ● 20 new Committers were added, bringing the total number of
> > >> > > committers to 42 from at least 23 different organizations.
> > >> > > ● 210+ new contributors participate in the community. The number of
> > >> > > contributors is now 240+ and growing.
> > >> > > ● 20 Bi-weekly online meetings were held among the committers,
> > >> > > contributors, and users. The meeting minutes are recorded on the
> > >> > > mailing list[6] and wiki [7].
> > >> > > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > >> > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > >> > > discussion at private@eventmesh [8]. Eason
> > >> > > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> > >> > >
> > >> > > *Project*
> > >> > >
> > >> > > ● Apache EventMesh(incubating) builds a fully serverless platform 
> > >> > > used
> > >> > > to build distributed event-driven applications.
> > >> > > ● EventMesh community released a total of 7 Apache releases [9] by 6
> > >> > > different release managers from 5 different organizations.
> > >> > > ● 1300+ issues created, and 1100+ issues closed [10].
> > >> > > ● 1600+ pull requests created, and 1600+ pull requests closed [11],
> > >> > > 2500+ commits added.
> > >> > > ● The release cadence is about 3 months, with an average of 180+
> > >> > > issues and 230+ pull requests per release.
> > >> > >
> > >> > > *Brands, License, and Copyright*
> > >> > >
> > >> > > ● We submitted an application for the brand [12], which has been
> > >> > > reviewed and approved.
> > >> > > ● EventMesh community maintains project code on GitHub and all 
> > >> > > modules
> > >> > > code is under Apache 2.0 license. We have reviewed all the
> > >> > > dependencies and ensured they do not bring any license issues [13].
> > >> > > All the status files, license headers, and copyright are up to date.
> > >> > > ● EventMesh official website [14] is compliant with Apache Foundation
> > >> > > requirements.
> > >> > >
> > >> > > -
> > >> > > BEGINNING OF DRAFT RESOLUTION
> > >> > > -
> > >> > >
> > >> > > Establish the Apache EventMesh Project
> > >> > >
> > >> > > WHEREAS, the Board of Directors deems it to be in the best interests
> > >> of
> > >> > > the Foundation and consistent with the Foundation's purpose to
> > >> establish
> > >> > > a Project Management Committee charged with the creation and
> > >> maintenance
> > >> > > of open-source software, for distribution at no charge to the public,
> > >> > > related to EventMesh is a fully serverless platform used to build
> > >> > > distributed event-driven applications.
> > >> > >
> > >> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > >> > > (PMC), to be known as the "Apache EventMesh Project", be and hereby 
> > >> > > is
> > >> > > established pursuant to Bylaws of the Foundation; and be it further
> > >> > >
> > >> > > RESOLVED, that the Apache EventMesh Project be and hereby is
> > >> responsible
> > >> > > for the creation and maintenance of software related to EventMesh is 
> > >> > > a
> > >> > > fully serverless platform used to bui

Re: [QUESTION] do pom files need to have a license header

[PJ Fanning]

Thanks everyone for the responses. I have raised an issue to investigate the 
possibilities about getting a header comment in the pom files we generate. I 
suspect we will need a change to the sbt build tool or one of its plugins.

On 2023/01/30 14:01:28 Jean-Baptiste Onofré wrote:
> Hi,
> 
> It's a better to have ASF header in all files where it's possible.
> However, it's sometime difficult (test static files, web content, ..).
> So if you can, it's better Pekko community fixes it.
> 
> Thanks,
> Regards
> JB
> 
> On Sun, Jan 29, 2023 at 6:31 PM PJ Fanning  wrote:
> >
> > Hi everyone,
> >
> > The Apache Pekko builds use the sbt tool for building and this generates 
> > pom files for us. They do not include any headers (example [1]).
> > It seems the norm to add an XML comment with Apache License info (example 
> > from log4j [2]).
> > Does the Pekko team need to fix this or is it just a nicety to have the 
> > license header in the pom files? If the answer is that we do need to fix 
> > this, does this also apply to other published files? sbt generates and 
> > publishes a 'buildinfo' file as part of the maven publish (example [2]).
> >
> > Regards,
> > PJ
> >
> >
> > [1] 
> > https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.pom
> > [2] 
> > https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-api/2.19.0/log4j-api-2.19.0.pom
> > [3] 
> > https://repository.apache.org/content/groups/snapshots/org/apache/pekko/pekko-actor_2.13/0.0.0+26546-767209a8-SNAPSHOT/pekko-actor_2.13-0.0.0+26546-767209a8-SNAPSHOT.buildinfo
> >
> > -
> > 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
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[QUESTION] are binary distributions/releases required?

[PJ Fanning]

Hi everyone,
The release management guide [1] only mentions 'source releases'. Every Apache 
project that I am familiar with also does binary releases. For applications, 
this makes sense - having a zip/tgz file that you can download and extract - 
that you can then readily start the application using a shell script. For libs, 
I'm sure these binary releases can be useful too but I'm wondering if they are 
strictly required.

Apache Pekko is a set of libraries as opposed to an application. Our build uses 
the sbt build tool and there isn't anything that I've come across that would 
produce something like the binary releases that other Apache projects release. 
This means we'd likely have to roll our own solution. 

In terms of prioritising work towards a v1.0.0 release, it's useful to know if 
we have items that could be de-prioritised.

If we do need to create binary releases, are there any guidelines to follow - 
or do we just look at other Apache libs and use their binary releases as a 
guide? 

Regards,
PJ

[1] https://incubator.apache.org/guides/releasemanagement.html

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [QUESTION] are binary distributions/releases required?

[PJ Fanning]

Thanks Julian for clarifying the terminology.

I think the general consensus in the Pekko team is that there is no call for 
creating binary artifacts distributions (example [1]). 

The initial user base of Pekko are users who currently use Akka but dislike the 
move to Business Source License 1.1. This user base are happy with jars 
released to Maven Central and we will be providing these as a convenience to 
our users.

If and when the source releases are approved and released, jars built at the 
same time as the source release will be published to Maven Central.

[1] 
https://www.apache.org/dyn/closer.lua/logging/log4j/2.19.0/apache-log4j-2.19.0-bin.zip


On 2023/02/08 16:46:03 Julian Hyde wrote:
> It’s useful to clarify the terminology. There’s no such thing as a “binary
> release”. Release policy [1] says:
> 
> > Every ASF release MUST contain one or more source packages
> 
> > All releases are in the form of the source materials needed to make
> changes
> > to the software being released.
> >
> > As a convenience to users that might not have the appropriate tools to
> build a
> > compiled version of the source, binary/bytecode packages MAY be
> distributed
> > alongside official Apache releases.”
> 
> The binary packages that may accompany a release are generally referred to
> as “binary artifacts” of the release.
> 
> Julian
> 
> [1] https://www.apache.org/legal/release-policy.html#artifacts
> 
> On Feb 8, 2023, at 7:19 AM, Dave Fisher  wrote:
> 
> Hi PJ,
> 
> Daffodil uses sbt and produces binary releases -
> https://daffodil.apache.org/releases/3.4.0/
> - https://GitHub.com/Apache/daffodil/
> 
> Best,
> Dave
> 
> Sent from my iPhone
> 
> On Feb 8, 2023, at 6:33 AM, PJ Fanning  wrote:
> 
> 
> Hi everyone,
> 
> The release management guide [1] only mentions 'source releases'. Every
> Apache project that I am familiar with also does binary releases. For
> applications, this makes sense - having a zip/tgz file that you can
> download and extract - that you can then readily start the application
> using a shell script. For libs, I'm sure these binary releases can be
> useful too but I'm wondering if they are strictly required.
> 
> 
> Apache Pekko is a set of libraries as opposed to an application. Our build
> uses the sbt build tool and there isn't anything that I've come across that
> would produce something like the binary releases that other Apache projects
> release. This means we'd likely have to roll our own solution.
> 
> 
> In terms of prioritising work towards a v1.0.0 release, it's useful to know
> if we have items that could be de-prioritised.
> 
> 
> If we do need to create binary releases, are there any guidelines to follow
> - or do we just look at other Apache libs and use their binary releases as
> a guide?
> 
> 
> Regards,
> 
> PJ
> 
> 
> [1] https://incubator.apache.org/guides/releasemanagement.html
> 
> 
> -
> 
> 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: [QUESTION] are binary distributions/releases required?

[PJ Fanning]

Thanks Hans. That would be the general plan with the Maven jar part of
our releases.
* as part of the RC where we stage a source release for people to vote
on, we will also push jars to repository.apache.org staging repo
* if the vote on the source release passes, we will release the source
release artifacts and also, use repository.apache.org webapp to
release the staged jars - so they will get pushed to Maven Central
* if the vote fails, we can use repository.apache.org webapp to drop
the staged jars as well or removing the source release candidate
artifacts

On Wed, 8 Feb 2023 at 21:39, Hans Van Akelyen
 wrote:
>
> Isn't staging for release on maven central the same as creating binary
> convenience artifacts?
>
> Staging to the ASF nexus to then be pushed to maven central is part of your
> release process [1]
>
> Cheers,
> Hans
>
> [1] https://infra.apache.org/publishing-maven-artifacts.html
>
>
> On Wed, 8 Feb 2023 at 20:15, PJ Fanning  wrote:
>
> > Thanks Julian for clarifying the terminology.
> >
> > I think the general consensus in the Pekko team is that there is no call
> > for creating binary artifacts distributions (example [1]).
> >
> > The initial user base of Pekko are users who currently use Akka but
> > dislike the move to Business Source License 1.1. This user base are happy
> > with jars released to Maven Central and we will be providing these as a
> > convenience to our users.
> >
> > If and when the source releases are approved and released, jars built at
> > the same time as the source release will be published to Maven Central.
> >
> > [1]
> > https://www.apache.org/dyn/closer.lua/logging/log4j/2.19.0/apache-log4j-2.19.0-bin.zip
> >
> >
> > On 2023/02/08 16:46:03 Julian Hyde wrote:
> > > It’s useful to clarify the terminology. There’s no such thing as a
> > “binary
> > > release”. Release policy [1] says:
> > >
> > > > Every ASF release MUST contain one or more source packages
> > >
> > > > All releases are in the form of the source materials needed to make
> > > changes
> > > > to the software being released.
> > > >
> > > > As a convenience to users that might not have the appropriate tools to
> > > build a
> > > > compiled version of the source, binary/bytecode packages MAY be
> > > distributed
> > > > alongside official Apache releases.”
> > >
> > > The binary packages that may accompany a release are generally referred
> > to
> > > as “binary artifacts” of the release.
> > >
> > > Julian
> > >
> > > [1] https://www.apache.org/legal/release-policy.html#artifacts
> > >
> > > On Feb 8, 2023, at 7:19 AM, Dave Fisher  wrote:
> > >
> > > Hi PJ,
> > >
> > > Daffodil uses sbt and produces binary releases -
> > > https://daffodil.apache.org/releases/3.4.0/
> > > - https://GitHub.com/Apache/daffodil/
> > >
> > > Best,
> > > Dave
> > >
> > > Sent from my iPhone
> > >
> > > On Feb 8, 2023, at 6:33 AM, PJ Fanning  wrote:
> > >
> > >
> > > Hi everyone,
> > >
> > > The release management guide [1] only mentions 'source releases'. Every
> > > Apache project that I am familiar with also does binary releases. For
> > > applications, this makes sense - having a zip/tgz file that you can
> > > download and extract - that you can then readily start the application
> > > using a shell script. For libs, I'm sure these binary releases can be
> > > useful too but I'm wondering if they are strictly required.
> > >
> > >
> > > Apache Pekko is a set of libraries as opposed to an application. Our
> > build
> > > uses the sbt build tool and there isn't anything that I've come across
> > that
> > > would produce something like the binary releases that other Apache
> > projects
> > > release. This means we'd likely have to roll our own solution.
> > >
> > >
> > > In terms of prioritising work towards a v1.0.0 release, it's useful to
> > know
> > > if we have items that could be de-prioritised.
> > >
> > >
> > > If we do need to create binary releases, are there any guidelines to
> > follow
> > > - or do we just look at other Apache libs and use their binary releases
> > as
> > > a guide?
> > >
> > >
> > > Regards,
> > >
> > > PJ
> > >
> > >
> > > [1] https://incubator.apache.org/guides/releasemanagement.html
> > >
> > >
> > > -
> > >
> > > 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
> >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [QUESTION] are binary distributions/releases required?

[PJ Fanning]

Hi Justin,
I'm struggling to find any examples of ASF jars pushed to maven
central that have anything other than the standard boilerplate Apache
LICENSE and NOTICE. Having a transitive dependency on another jar
doesn't appear to be mentioned in any jar LICENSE/NOTICE that I
checked.

Having code from another jar shaded within your jar - I'm guessing
that would be a case that needs mention in the jar's META-INF/LICENSE.

With Pekko, bundling classes from other non-Apache projects is not the
norm (with a small number of exceptions) - the pom.xml just lists
dependencies on the jars we need.

Is there anything else that affects what appears in a jar's META-INF
LICENSE and NOTICE?

Since we're not currently planning to create a set of binary artifacts
(zip and/or tgz) with jars including transitive dependency jars that
so many ASF projects create - presumably that means we don't need to
create the LICENSE-binary and NOTICE-binary that many projects create
- that contain lists of all the transitive dependencies with their
licenses. An example of this LICENSE-binary/NOTICE-binary usage
appears in the root dir of https://github.com/apache/spark.

Any clarifications would be much appreciated.


On Thu, 9 Feb 2023 at 01:04, Justin Mclean  wrote:
>
> Hi,
>
> Those jars are likely to have different LICENSE and NOTICE files so I would 
> suggest you vote on both at the same time.
>
> Kind Regards,
> Justin
> -
> 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] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[PJ Fanning]

+1 (binding) - project seems in good health and worthy to become a TLP

On Thu, 9 Feb 2023 at 11:17, YuanXin Hu  wrote:
>
> +1
>
> On 2023/02/09 09:44:03 Eason Chen wrote:
> > Dear Apache Incubator Community and IPMC members,
> >
> > After having the graduation discussion in the EventMesh community [1],
> > we passed the vote within the EventMesh community [2] and the vote
> > result was published[3].
> > We then discussed the graduation for EventMesh in the Apache Incubator
> > Community [4], where no issues were raised and positive replies were
> > received.
> >
> > I would like to start this voting thread to request graduating Apache
> > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >
> > Please provide your vote accordingly:
> > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > Apache Incubator.
> > [ ] +0 No opinion.
> > [ ] -1 No, the EventMesh 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 EventMesh(incubating) to help with the 
> > vote.
> >
> > *Community*
> >
> > ● 5 new PPMC members were added, bringing the total number of PPMC
> > members to 14 from at least 9 different organizations.
> > ● 20 new Committers were added, bringing the total number of
> > committers to 42 from at least 30 different organizations.
> > ● 220+ new contributors participate in the community. The number of
> > contributors is now 250+ and growing.
> > ● 20 Bi-weekly online meetings were held among the committers,
> > contributors, and users. The meeting minutes are recorded on the
> > mailing list[5] and cwiki [6].
> > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > ● We've confirmed the VP, PMC, and Committers in the preparation
> > discussion at private@eventmesh [7]. Eason
> > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >
> > *Project*
> >
> > ● Apache EventMesh(incubating) is a fully serverless platform used to
> > build distributed event-driven applications.
> > ● Project maturity model is detailed in [8].
> > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > different release managers from 5 different organizations.
> > ● 1300+ issues created, and 1100+ issues closed [11].
> > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > 2500+ commits added.
> > ● The release cadence is about 3 months, with an average of 180+
> > issues and 230+ pull requests per release.
> > ● Please refer to the EventMesh project incubation status [13][14] for
> > more information.
> >
> > *Brands, License, and Copyright*
> >
> > ● We applied the brand [15], which has been reviewed and approved.
> > ● EventMesh community maintains project code on GitHub and all modules
> > code is under Apache 2.0 license. We have reviewed all the
> > dependencies and ensured they do not bring any license issues [16].
> > All the status files, license headers, and copyright are up to date.
> > ● EventMesh official website [17] is compliant with Apache Foundation
> > requirements[18].
> >
> > -
> > BEGINNING OF DRAFT RESOLUTION
> > -
> >
> > Establish the Apache EventMesh Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to EventMesh is a fully serverless platform used to build
> > distributed event-driven applications.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> > for the creation and maintenance of software related to EventMesh is a
> > fully serverless platform used to build distributed event-driven
> > applications; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache EventMesh
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache EventMesh
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache EventMesh
> > Project:
> >
> >  * Alex Luo 
> >  * Du Heng  
> >  * Eason Chen   
> >  

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[PJ Fanning]

+1 (binding)

On Thu, 9 Feb 2023 at 14:56, Alex Luo  wrote:
>
> +1
>
> Alex Luo
>
> On 2023/02/09 13:45:01 Wei Liu wrote:
> > +1
> >
> > On 2023/02/09 12:19:14 Eason Chen wrote:
> > > Dear Apache Incubator Community and IPMC members,
> > >
> > > After having the graduation discussion in the EventMesh community [1],
> > > we passed the vote within the EventMesh community [2] and the vote
> > > result was published[3].
> > > We then discussed the graduation for EventMesh in the Apache Incubator
> > > Community [4], where no issues were raised and positive replies were
> > > received.
> > >
> > > I would like to start this voting thread to request graduating Apache
> > > EventMesh(incubating) from Apache Incubator as a Top Level Project.
> > >
> > > Please provide your vote accordingly:
> > > [ ] +1 Yes, I support the EventMesh project to graduate from the
> > > Apache Incubator.
> > > [ ] +0 No opinion.
> > > [ ] -1 No, the EventMesh 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 EventMesh(incubating) to help with the 
> > > vote.
> > >
> > > *Community*
> > >
> > > ● 5 new PPMC members were added, bringing the total number of PPMC
> > > members to 14 from at least 9 different organizations.
> > > ● 20 new Committers were added, bringing the total number of
> > > committers to 42 from at least 30 different organizations.
> > > ● 220+ new contributors participate in the community. The number of
> > > contributors is now 250+ and growing.
> > > ● 20 Bi-weekly online meetings were held among the committers,
> > > contributors, and users. The meeting minutes are recorded on the
> > > mailing list[5] and cwiki [6].
> > > ● The dev@eventmesh mailing list currently has 117 subscribers.
> > > ● We've confirmed the VP, PMC, and Committers in the preparation
> > > discussion at private@eventmesh [7]. Eason
> > > Chen(chenguangsh...@apache.org) was recommended as Vice President.
> > >
> > > *Project*
> > >
> > > ● Apache EventMesh(incubating) is a fully serverless platform used to
> > > build distributed event-driven applications.
> > > ● Project maturity model is detailed in [8].
> > > ● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> > > ● EventMesh community released a total of 7 Apache releases [10] by 6
> > > different release managers from 5 different organizations.
> > > ● 1300+ issues created, and 1100+ issues closed [11].
> > > ● 1600+ pull requests created, and 1600+ pull requests closed [12],
> > > 2500+ commits added.
> > > ● The release cadence is about 3 months, with an average of 180+
> > > issues and 230+ pull requests per release.
> > > ● Please refer to the EventMesh project incubation status [13][14] for
> > > more information.
> > >
> > > *Brands, License, and Copyright*
> > >
> > > ● We applied the brand [15], which has been reviewed and approved.
> > > ● EventMesh community maintains project code on GitHub and all modules
> > > code is under Apache 2.0 license. We have reviewed all the
> > > dependencies and ensured they do not bring any license issues [16].
> > > All the status files, license headers, and copyright are up to date.
> > > ● EventMesh official website [17] is compliant with Apache Foundation
> > > requirements[18].
> > >
> > > -
> > > BEGINNING OF DRAFT RESOLUTION
> > > -
> > >
> > > Establish the Apache EventMesh Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > the Foundation and consistent with the Foundation's purpose to establish
> > > a Project Management Committee charged with the creation and maintenance
> > > of open-source software, for distribution at no charge to the public,
> > > related to a fully serverless platform used to build distributed
> > > event-driven applications.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache EventMesh Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> > > for the creation and maintenance of software related to EventMesh is a
> > > fully serverless platform used to build distributed event-driven
> > > applications; and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> > > hereby is created, the person holding such office to serve at the
> > > direction of the Board of Directors as the chair of the Apache EventMesh
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache EventMesh
> > > Project; and be it further
> > >
> > > RESOLVED, that the persons listed immediately below be and hereb

Re: [VOTE] Graduate Apache EventMesh(incubating) as an Apache Top Level Project

[PJ Fanning]

+1 (binding) - project seems in good health and worthy to become a TLP

On Fri, 10 Feb 2023 at 14:48, ShanPeng Qing  wrote:
>
>
>
>
> +1, congratulations.
>
>
> At 2023-02-10 10:31:56, "Eason Chen"  wrote:
> >Dear Apache Incubator Community and IPMC members,
> >
> >After having the graduation discussion in the EventMesh community [1],
> >we passed the vote within the EventMesh community [2] and the vote
> >result was published[3].
> >We then discussed the graduation for EventMesh in the Apache Incubator
> >Community [4], where no issues were raised and positive replies were
> >received.
> >
> >I would like to start this voting thread to request graduating Apache
> >EventMesh(incubating) from Apache Incubator as a Top Level Project.
> >
> >Please provide your vote accordingly:
> >[ ] +1 Yes, I support the EventMesh project to graduate from the
> >Apache Incubator.
> >[ ] +0 No opinion.
> >[ ] -1 No, the EventMesh 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 EventMesh(incubating) to help with the 
> >vote.
> >
> >*Community*
> >
> >● 5 new PPMC members were added, bringing the total number of PPMC
> >members to 14 from at least 9 different organizations.
> >● 20 new Committers were added, bringing the total number of
> >committers to 42 from at least 30 different organizations.
> >● 220+ new contributors participate in the community. The number of
> >contributors is now 250+ and growing.
> >● 20 Bi-weekly online meetings were held among the committers,
> >contributors, and users. The meeting minutes are recorded on the
> >mailing list[5] and cwiki [6].
> >● The dev@eventmesh mailing list currently has 117 subscribers.
> >● We've confirmed the VP, PMC, and Committers in the preparation
> >discussion at private@eventmesh [7]. Eason
> >Chen(chenguangsh...@apache.org) was recommended as Vice President.
> >
> >*Project*
> >
> >● Apache EventMesh(incubating) builds a fully serverless platform for
> >distributed event-driven applications.
> >● Project maturity model is detailed in [8].
> >● EventMesh has been incubating [9] since 2021-02-18 for over 23 months.
> >● EventMesh community released a total of 7 Apache releases [10] by 6
> >different release managers from 5 different organizations.
> >● 1300+ issues created, and 1100+ issues closed [11].
> >● 1600+ pull requests created, and 1600+ pull requests closed [12],
> >2500+ commits added.
> >● The release cadence is about 3 months, with an average of 180+
> >issues and 230+ pull requests per release.
> >● Please refer to the EventMesh project incubation status [13][14] for
> >more information.
> >
> >*Brands, License, and Copyright*
> >
> >● We applied the brand [15], which has been reviewed and approved.
> >● EventMesh community maintains project code on GitHub and all modules
> >code is under Apache 2.0 license. We have reviewed all the
> >dependencies and ensured they do not bring any license issues [16].
> >All the status files, license headers, and copyright are up to date.
> >● EventMesh official website [17] is compliant with Apache Foundation
> >requirements[18].
> >
> >-
> >BEGINNING OF DRAFT RESOLUTION
> >-
> >
> >Establish the Apache EventMesh Project
> >
> >WHEREAS, the Board of Directors deems it to be in the best interests of
> >the Foundation and consistent with the Foundation's purpose to establish
> >a Project Management Committee charged with the creation and maintenance
> >of open-source software, for distribution at no charge to the public,
> >related to a fully serverless platform used to build distributed
> >event-driven applications.
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> >(PMC), to be known as the "Apache EventMesh Project", be and hereby is
> >established pursuant to Bylaws of the Foundation; and be it further
> >
> >RESOLVED, that the Apache EventMesh Project be and hereby is responsible
> >for the creation and maintenance of software related to a fully
> >serverless platform used to build distributed event-driven applications;
> >and be it further
> >
> >RESOLVED, that the office of "Vice President, Apache EventMesh" be and
> >hereby is created, the person holding such office to serve at the
> >direction of the Board of Directors as the chair of the Apache EventMesh
> >Project, and to have primary responsibility for management of the
> >projects within the scope of responsibility of the Apache EventMesh
> >Project; and be it further
> >
> >RESOLVED, that the persons listed immediately below be and hereby are
> >appointed to serve as the initial members of the Apache EventMesh
> >Project:
> >
> > * Alex Luo 
> > * Du Heng  
> > * Eason Chen   
> > * Francois Papon   
> > * Jean-Baptiste Onofré 
> > * Junping Du   
> 

Re: Re: [DISCUSS] Incubating Proposal for OpenDAL

[PJ Fanning]

Looks like a strong candidate. I would echo Willem's point about needing
less reliance on 1 committer.

On Sat 18 Feb 2023, 17:18 KimmKing,  wrote:

> +1, it is a "delicious" project.
>
>
> BTW:  "Apache-2.0 WITH LLVM-exception (5)" should be modified/removed in
> future?
>
>
>
>
>
>
> --
>
> Kimm King(kimmk...@apache.org/kimmk...@163.com)
> Apache Dubbo&ShardingSphere PMC Member
> github&twitter: kimmking
>
>
>
>
>
> At 2023-02-17 21:12:59, "Willem Jiang"  wrote:
> >+1, it's an interesting project. I'd like to be a mentor of this project.
> >BTW, even though there are  37 contributors, I found Xuanwo did most
> >of the development, which is not a good bus factor[1] of this project.
> >We can make it better during the incubating process.
> >
> >[1]https://en.wikipedia.org/wiki/Bus_factor
> >
> >
> >Willem Jiang
> >
> >Twitter: willemjiang
> >Weibo: 姜宁willem
> >
> >On Fri, Feb 17, 2023 at 7:22 AM tison  wrote:
> >>
> >> Hi IPMC,
> >>
> >> I would like to propose OpenDAL[1] as a new apache incubator project,
> you
> >> can find the proposal[2] of OpenDAL for more detail.
> >>
> >> [1] https://github.com/datafuselabs/opendal
> >> [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal
> >>
> >> Best,
> >> tison.
> >>
> >> Full text of the proposal below:
> >>
> >> ## Abstract
> >>
> >> OpenDAL means “Open Data Access Layer”. It’s a Rust library that helps
> >> developers access data freely, painlessly, and efficiently over multiple
> >> services, including AWS S3, HDFS, POSIX-compatible file systems, and so
> on.
> >>
> >> ## Proposal
> >>
> >> OpenDAL provides the following features to support developers accessing
> >> data freely, painlessly, and efficiently:
> >>
> >> - Freely
> >> - Access different storage services in the same way
> >> - Behavior tests for all services
> >> - Cross-language/project bindings (working in progress)
> >> - Painlessly
> >> - **100%** of documents covered
> >> - Powerful [Layers](
> >> https://opendal.databend.rs/opendal/layers/index.html)
> >> - Automatic [retry](
> >> https://opendal.databend.rs/opendal/layers/struct.RetryLayer.html)
> support
> >> - Full observability support: [logging](
> >> https://opendal.databend.rs/opendal/layers/struct.LoggingLayer.html
> >> ), [tracing](
> >> https://opendal.databend.rs/opendal/layers/struct.TracingLayer.html),
> and
> >> [metrics](
> >> https://opendal.databend.rs/opendal/layers/struct.MetricsLayer.html).
> >> - Native chaos testing
> >> - Native service-side encryption support
> >> - Efficiently
> >> - Zero cost: mapping to underlying API calls directly
> >> - Best effort: auto-pick the best `read`/`seek`/`next`
> implementations
> >> based on services
> >> - [Auto metadata reuse](
> >> https://opendal.databend.rs/rfcs/0561-list-metadata-reuse.html): avoid
> >> extra `metadata` calls
> >>
> >> OpenDAL was originally designed to be used by the Databend project but
> is
> >> now being used by Mozilla's sccache, DeepETH's mars, and several
> database
> >> startups.
> >>
> >> We believe that the OpenDAL project will provide diversity value to the
> >> community if OpenDAL is brought into the Apache incubator.
> >>
> >> ## Background
> >>
> >> OpenDAL is being developed by an open-source community from day one and
> is
> >> owned by DatafuseLabs. The project has been launched in February 2022.
> >>
> >> ## Rationale
> >>
> >> OpenDAL provides a unified storage abstraction layer that simplifies the
> >> interfacing of different storage services. In addition, OpenDAL provides
> >> further advanced storage encapsulation, enabling enhancements such as
> >> automatic retry, request optimization, and observability. OpenDAL makes
> it
> >> possible to develop once and run on any storage service.
> >>
> >> ## Initial Goals
> >>
> >> By transferring ownership of the project to the ASF, OpenDAL expects to
> >> ensure its neutrality and further encourage and facilitate the adoption
> of
> >> OpenDAL by the community.
> >>
> >> Some of the areas we would like to focus on during the Apache incubation
> >> phase include:
> >>
> >> - A healthier community: more maintainers and contributors will be able
> to
> >> participate in OpenDAL and own different modules.
> >> - Wider adoption: OpenDAL can be adopted by more open source/commercial
> >> projects, which in turn drives its own functionality.
> >> - Richer integration: OpenDAL enables greater integration of storage
> >> services and offers a wider range of language bindings.
> >>
> >> ## Current Status
> >>
> >> ### Meritocracy
> >>
> >> We intend to radically expand the initial developer and user community
> by
> >> running the project the 'Apache way'. Users and new contributors will be
> >> respected and welcomed. They will earn credit by participating in the
> >> community and providing quality patches/support to move the project
> >> forward. They will also be encouraged to provide non-code contributions
> >> (documentation, e

Re: [VOTE] Accept OpenDAL into the Apache Incubator

[PJ Fanning]

+1 (binding) - looks like a good candidate

On Tue 21 Feb 2023, 16:09 Twice,  wrote:

> +1. Good luck!
>
> Best,
> Twice
>
> On Tue, Feb 21, 2023 at 9:25 PM tison  wrote:
>
> > Hi all,
> >
> > Following up on the [DISCUSS] thread on OpenDAL[1], I would like to call
> a
> > VOTE to accept OpenDAL into the Apache Incubator, please check out the
> > OpenDAL Proposal from the incubator wiki[2].
> >
> > Please cast your vote:
> >
> > [ ] +1, bring OpenDAL into the Incubator
> > [ ] +0, I don't care either way
> > [ ] -1, do not bring OpenDAL into the Incubator, because...
> >
> > The vote will open at least for 72 hours, and only votes from the
> Incubator
> > PMC members are binding, but votes from everyone are welcome.
> >
> > [1] https://lists.apache.org/thread/px7wjcjy3rd4s59d4d3ll1x6y11d240r
> > [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/OpenDAL+Proposal
> >
> > Best,
> > tison.
> >
>

Re: [VOTE] Retire Marvin-AI from Incubator

[PJ Fanning]

+1 - It's a pity to see the project retired but at this stage, it
seems to be the only real option.

On Wed, 22 Feb 2023 at 15:11, Calvin Kirs  wrote:
>
> Hi,
>
> Marvin-AI has been incubating since 2018-08-27.
>
> Since 2021, activity has been low, and the chances of attracting new
> committers and building a vibrant community seem very slim at this
> point.
>
> At the same time, the project also missed many reports last year, and
> no one responded to the PPMC roll call.
>
> The community discussion and vote can be found here[1],[2].
>
> I therefore propose to retire Marvin-AI from the Incubator.
>
> Voting will start now and will remain open for at least 72 hours.
>
> Notice:
>
> Because the dev vote didn't get enough +1, so it's not a laze vote.
>
> If you are interested in this and are willing to contribute, please
> don't hesitate to vote your -1.
>
>
> [ ] +1 Retire Marvin-AI
> [ ] -1 Keep Marvin-AI and I’m willing to join to make it an Apache Community.
>
> [1]https://lists.apache.org/thread/6w0s115gnvsww3ptjt3f1xcrr02211hr
> [2]https://lists.apache.org/thread/hpd7fmjm138r09jrzd7d8jdyz3360q52
>
>
> --
> 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

Re: [VOTE] Accept Paimon into the Apache Incubator

[PJ Fanning]

+1 (binding). Looks like an exciting project.

On Mon, 6 Mar 2023 at 10:48, Xiaoqiao He  wrote:
>
> +1 (binding)
> Good luck!
>
> Best Regards,
> - He Xiaoqiao
>
> On Mon, Mar 6, 2023 at 4:56 PM Keyong Zhou  wrote:
>
> > +1 (non-binding)
> > Good luck!
> >
> > Thanks,
> > Keyong Zhou
> >
> > Yu Li  于2023年3月6日周一 15:59写道：
> >
> > > Hi All,
> > >
> > > Following up on the [DISCUSS] thread on Paimon [1], I would like to call
> > > a VOTE to accept Paimon into the Apache Incubator, please check out
> > > the Paimon Proposal from the incubator wiki [2].
> > >
> > >
> > > Please cast your vote:
> > >
> > >
> > > [ ] +1, bring Paimon into the Incubator
> > >
> > > [ ] +0, I don't care either way
> > >
> > > [ ] -1, do not bring Paimon into the Incubator, because...
> > >
> > >
> > > The vote will open at least for 72 hours, and only votes from the
> > Incubator
> > > PMC are binding, but votes from everyone are welcome.
> > >
> > > Best Regards,
> > > Yu
> > >
> > > [1] https://lists.apache.org/thread/hr3d7tpw02w6ybrnnlf3hcbhfxotwpvn
> > > [2] https://cwiki.apache.org/confluence/display/INCUBATOR/PaimonProposal
> > >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Retire the Spot podling

[PJ Fanning]

+1 (binding)

I'm sorry to say it but it appears the project no longer has enough
support to continue as a podling.

On Mon, 13 Mar 2023 at 21:43, Christian Grobmeier  wrote:
>
> Hello,
>
> as recently discussed, I think the Spot podling is ready for retirement.
>
> Several roll calls were made, like this one:
> https://lists.apache.org/list?priv...@spot.apache.org:2022-10
>
> There has been no activity for a while; there are no signs of change soon.
>
> Please vote:
>
> [ ] +1, retire
> [ ] -1 don't retire, because...
>
> Please don't hesitate to vote -1 if you feel this podling should remain.
>
> This vote will be kept open for at least the usual 72 hours.
>
> Kind regards,
> Christian
>
> -
> 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] Retire PageSpeed

[PJ Fanning]

+1 (binding)

On Wed, 15 Mar 2023 at 03:51, Dave Fisher  wrote:
>
> +1 (binding)
>
> Best,
> Dave
>
> Sent from my iPhone
>
> > On Mar 13, 2023, at 1:47 PM, Christian Grobmeier  
> > wrote:
> >
> > Hello,
> >
> > as recently discussed, I think the PageSpeed podling is ready for 
> > retirement.
> >
> > https://lists.apache.org/thread/jxw7mqmpcfxxp0mnnx28o0k78tym507b
> >
> > There has been no activity for a while; there are no signs of change soon.
> >
> > Please vote:
> >
> > [ ] +1, retire
> > [ ] -1 don't retire, because...
> >
> > Please don't hesitate to vote -1 if you feel this podling should remain.
> >
> > This vote will be kept open for at least the usual 72 hours.
> >
> > Kind regards,
> > Christian
> >
> > -
> > 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
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Apache tiles

[PJ Fanning]

Hi Laurent,
I don't want to write off the possibility of a Jakarta variant of
Tiles joining the Apache Incubator - but the fact that Apache Tiles
doesn't have an active community around it is going to be a major
impediment. For Apache projects and podlings to succeed, they need a
number of contributors to get involved.
Could you start by putting your code up on Github or somewhere similar
and adding documentation that highlights that you are looking for
collaborators? Maybe there are some forums where some remaining users
of Tiles can be contacted?

There is no impediment to you simply releasing your Jakarta variant of
Tiles yourself or via some organisation that you are involved with
(e.g. a company that you work with). If you go this route, the ASF
would look like to see that you remove all the ASF branding and
ideally, change the package names.

If you want to avoid having to do all the branding changes and see the
new project join/rejoin the ASF, then I think that you'll need to come
back to us with more collaborators and probably some indication that
they are bought into keeping the project going over the foreseeable
future.

Regards,
PJ


On Sat, 18 Mar 2023 at 06:32, Laurent Schoelens
 wrote:
>
> Hi everyone,
>
> I’m working on Apache Tiles porting to Jakarta EE (without support of 
> freemarker and velocity, since both of them are still going with javax API) 
> and my work is going to reach it’s end – all builds are successful, jdk17 
> baseline and updated dependencies (as far as I know) – but still uncommited 
> to my personal github account.
>
> I know Tiles is in Attic land of Apache but I’d which to make this first step 
> (Jakarta migration) go to open-source world, without creating new projects 
> out of the box.
> Tiles is a framework I use on a project, with Spring and since Spring 6 has 
> migrated to Jakarta API, I’m stuck to Spring 5.X if I stay on this. Changing 
> technology is an option for frontend application but not until a good rework 
> that may take months (or years, depending on time we have to do that 
> migration).
> Having a Tiles Jakarta port would be great since the technology itself is 
> working well on my project.
>
> Do you know what can I do to make this properly, according to Apache work ?
>
> Thanks in advance for your help.
>
> Regards.
> L. SCHOELENS

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

podling reports and incubator pmc report to the board (May 2023)

[PJ Fanning]

Hi everyone,
Apologies if I missed it but there does not appear to be a May 2023
wiki page for the podling reports.
I checked https://cwiki.apache.org/confluence/display/INCUBATOR/Reports

I've been doing some of the shepherd reports and have been checking in
on those pages to see what podlings I've been assigned for May.

Is it possible that the way we do the report has changed or is this
month's reporting just delayed?

Regards,
PJ

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Kvrocks(incubating) as a TLP

[PJ Fanning]

+1 (binding)

Kvrocks project seems to be in a very healthy position to move forward as a TLP.

On Sat, 13 May 2023 at 09:43, Yuan Wang  wrote:
>
> +1 (non-binding)
>
> We already used it for several years in production environment, very glad
> to see this happen, good luck!
>
> Best Regards
> Yuan Wang
>
> peacewong  于2023年5月13日周六 13:55写道：
>
> > +1 (non-binding)
> >
> > Good Luck!
> >
> > Best regards,
> > Peace Wong
> > Liang Chen  于2023年5月13日周六 13:50写道：
> >
> > > +1(binding)
> > >
> > > Regards
> > > Liang
> > >
> > > hulk  于2023年5月12日周五 05:55写道：
> > >
> > > > Hello all,
> > > >
> > > > We've got positive feedback on the DISCUSS thread[1], I'd like to start
> > > an
> > > > official VOTE thread now.
> > > >
> > > > Please vote on the resolution pasted below to graduate Apache Kvrocks
> > > from
> > > > the incubator to the Top Level Project.
> > > >
> > > > [ ] +1 Graduate Apache Kvrocks from the Incubator.
> > > > [ ] +0 No opinion.
> > > > [ ] -1 Don't graduate Apache Kvrocks from the Incubator because ...
> > > >
> > > > This vote will open for at least 72 hours.
> > > >
> > > > Many thanks to our mentors and everyone else for their support.
> > > >
> > > > [1] https://lists.apache.org/thread/ld8x1wvh1n745j96ksy0pmy92gwn2t06
> > > >
> > > > ---
> > > >
> > > > Establish the Apache Kvrocks Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > > the Foundation and consistent with the Foundation's purpose to
> > establish
> > > > a Project Management Committee charged with the creation and
> > maintenance
> > > > of open-source software, for distribution at no charge to the public,
> > > > related to a distributed key-value NoSQL database, supporting the rich
> > > > data structure.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache Kvrocks Project", be and hereby is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache Kvrocks Project be and hereby is responsible
> > > > for the creation and maintenance of software related to a distributed
> > > > key-value NoSQL database, supporting the rich data structure; and be it
> > > > further
> > > >
> > > > RESOLVED, that the office of "Vice President, Apache Kvrocks" be and
> > > > hereby is created, the person holding such office to serve at the
> > > > direction of the Board of Directors as the chair of the Apache Kvrocks
> > > > Project, and to have primary responsibility for management of the
> > > > projects within the scope of responsibility of the Apache Kvrocks
> > > > Project; and be it further
> > > >
> > > > RESOLVED, that the persons listed immediately below be and hereby are
> > > > appointed to serve as the initial members of the Apache Kvrocks
> > Project:
> > > >
> > > >  * Alfejik Liu  
> > > >  * Hulk Lin 
> > > >  * Jean-Baptiste Onofré 
> > > >  * Liang Chen   
> > > >  * Mingyang Liu 
> > > >  * Von Gosling  
> > > >  * Xiaoqiao He  
> > > >  * Yaroslav Stepanchuk  
> > > >  * Yuan Wang
> > > >  * Zili Chen
> > > >
> > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hulk Lin be appointed to
> > > > the office of Vice President, Apache Kvrocks, to serve in accordance
> > > > with and subject to the direction of the Board of Directors and the
> > > > Bylaws of the Foundation until death, resignation, retirement, removal
> > > > or disqualification, or until a successor is appointed; and be it
> > > > further
> > > >
> > > > RESOLVED, that the Apache Kvrocks Project be and hereby is tasked with
> > > > the migration and rationalization of the Apache Incubator Kvrocks
> > > > podling; and be it further
> > > >
> > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > > > Kvrocks podling encumbered upon the Apache Incubator PMC are hereafter
> > > > discharged.
> > > >
> > >
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

switching Pekko to use the WIP Disclaimer

[PJ Fanning]

Hi everyone,

The Pekko project has been going 8 months and we are really in need of
getting a release out. Akka recently announced CVEs but have said they
will not backport them to the OSS release lines. [1]

We have tried to get through a number of licensing problems but a
number still remain.
Some more were found today [2] and I found a few more searching
around. The problem is that Lightbend appears to have borrowed a lot
of code from different sources. None of these sources appears to have
problematic licenses.

We'll try to sort out some more of the header and license file
problems before trying another RC but they are time consuming. It's
hard to get anyone to do the tasks. I've done a lot but I am fed up of
doing so many. It's not just reading through thousands of lines of
ancient code - there are usually arguments about what the licensing
implication is when we find code that is based on non-Akka code.

If the next Pekko RC was done using the Work in Progress Disclaimer
[3], would the Incubator PMC give us a little leeway on sorting out
the remaining license header issues later (and allow us to do a
release)?

If there is no hope of getting some leeway and that we must solve
everything before we can make a release, we can bring this back to the
Pekko community and see if we can find volunteers.

[1] https://akka.io/security/
[2] https://lists.apache.org/thread/mo611z4dpro1373r4f5pbgtlyjmhhtz9
[3] 
https://incubator.apache.org/policy/incubation.html#work_in_progress_disclaimer

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: switching Pekko to use the WIP Disclaimer

[PJ Fanning]

Thanks Justin for your feedback.

The DISCLAIMER-WIP would only be used for next few months while we
address the remaining issues. There would be no intention to stop
trying to resolve them.

On Tue, 20 Jun 2023 at 04:47, Justin Mclean  wrote:
>
> Hi,
>
> Yes, using the work-in-progress disclaimer does give you some leeway. 
> However, it may not be as much as you think. See [1].
>
> Note that issues such as:
> • Missing ASF headers
> • 3rd party Category A bundled code licenses not listed in LICENSE
> • Including uncategorised source code
>
> Need to be listed in the DISCLAIMER-WIP and fixed in the next release. Some 
> projects have taken a couple of releases to fix all issues, but progress in 
> each release needs to be made. A project can't graduate with WIP disclaimer 
> in place.
>
> Kind Regards,
> Justin
>
> 1. https://issues.apache.org/jira/browse/LEGAL-469
>
>
> -
> 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

is it ok to modify copyright headers that have no end year?

[PJ Fanning]

Hi everyone,

The Pekko community is working on a release of our core repository. We
have a number of other repositories that we will release later.

In one of these downstream repositories, the source code has Lightbend
copyrights that say (example [1]):

Copyright (C) since 2016 Lightbend Inc.

Since the Pekko forked this code at a point in September 2022, is it
ok to change this copyright to this?

Copyright (C) 2016-2022 Lightbend Inc.

It doesn't seem right to leave the copyright claim open ended and
effectively implying that any changes made this year by the Apache
Pekko community are covered by Lightbend copyright.

Generally, I wouldn't modify any headers like this but this one seems
to require modification.

Any insights would be appreciated.

Regards,
PJ

[1] 
https://github.com/apache/incubator-pekko-connectors/blob/178795f6882e2d06524962f30359691889489fd5/s3/src/main/scala/org/apache/pekko/stream/connectors/s3/Utils.scala#L11

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: is it ok to modify copyright headers that have no end year?

[PJ Fanning]

Thanks Craig. I've created a Jira.

https://issues.apache.org/jira/browse/LEGAL-645


On Mon, 26 Jun 2023 at 15:52, Craig Russell  wrote:
>
> Hi PJ,
>
> I don't know the answer to your question but I do think that this is a 
> non-standard copyright notice that should be changed.
>
> I'd suggest opening a LEGAL JIRA for an official response (and perhaps once 
> it's resolved, it would be a good FAQ).
>
> Warm regards,
> Craig
>
> > On Jun 26, 2023, at 07:40, PJ Fanning  wrote:
> >
> > Hi everyone,
> >
> > The Pekko community is working on a release of our core repository. We
> > have a number of other repositories that we will release later.
> >
> > In one of these downstream repositories, the source code has Lightbend
> > copyrights that say (example [1]):
> >
> > Copyright (C) since 2016 Lightbend Inc.
> >
> > Since the Pekko forked this code at a point in September 2022, is it
> > ok to change this copyright to this?
> >
> > Copyright (C) 2016-2022 Lightbend Inc.
> >
> > It doesn't seem right to leave the copyright claim open ended and
> > effectively implying that any changes made this year by the Apache
> > Pekko community are covered by Lightbend copyright.
> >
> > Generally, I wouldn't modify any headers like this but this one seems
> > to require modification.
> >
> > Any insights would be appreciated.
> >
> > Regards,
> > PJ
> >
> > [1] 
> > https://github.com/apache/incubator-pekko-connectors/blob/178795f6882e2d06524962f30359691889489fd5/s3/src/main/scala/org/apache/pekko/stream/connectors/s3/Utils.scala#L11
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> Craig L Russell
> c...@apache.org
>
>
> -
> 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: is it ok to modify copyright headers that have no end year?

[PJ Fanning]

Thanks everyone. I'll leave the license headers as they are.

On 2023/06/27 00:49:07 Paul King wrote:
> IANAL, but the advice I've been given informally by IP lawyer friends many
> years ago is don't change the existing copyright.
> 
> You could instead amend to something like:
> 
> Original version:
> > Copyright (C) since 2016 Lightbend Inc.
> > Subsequent changes made by the Apache Pekko community:
> > Copyright 2022 The Apache Software Foundation.
> 
> 
> Also, at the time, it was commented by the same lawyer folks that in many
> (but not all) jurisdictions, you can leave the year out of individual files
> as long as you have a generic NOTICE file with the year range, e.g.
> 2022-2023 for Pekko. The date specifics for any individual file/change can
> be determined "Ex Post Facto" from the version control system. But I
> presume the LEGAL folks will give you further up to date info.
> 
> Cheers, Paul.
> 
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Virus-free.www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> 
> On Tue, Jun 27, 2023 at 12:40 AM PJ Fanning  wrote:
> 
> > Hi everyone,
> >
> > The Pekko community is working on a release of our core repository. We
> > have a number of other repositories that we will release later.
> >
> > In one of these downstream repositories, the source code has Lightbend
> > copyrights that say (example [1]):
> >
> > Copyright (C) since 2016 Lightbend Inc.
> >
> > Since the Pekko forked this code at a point in September 2022, is it
> > ok to change this copyright to this?
> >
> > Copyright (C) 2016-2022 Lightbend Inc.
> >
> > It doesn't seem right to leave the copyright claim open ended and
> > effectively implying that any changes made this year by the Apache
> > Pekko community are covered by Lightbend copyright.
> >
> > Generally, I wouldn't modify any headers like this but this one seems
> > to require modification.
> >
> > Any insights would be appreciated.
> >
> > Regards,
> > PJ
> >
> > [1]
> > https://github.com/apache/incubator-pekko-connectors/blob/178795f6882e2d06524962f30359691889489fd5/s3/src/main/scala/org/apache/pekko/stream/connectors/s3/Utils.scala#L11
> >
> > -
> > 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: Question on GitHub

[PJ Fanning]

Use the ASF Self Serve tool [1] to create the git repos in ASF gitbox
and they will be mirrored on GitHub automatically.

It's easy to copy the git history from an existing git repo into the
new ASF ones.

[1] https://selfserve.apache.org/

On Tue, 27 Jun 2023 at 14:42, Dave Fisher  wrote:
>
> They are required to have an ASF served repository either SVN or GiT. Infra 
> has setup the ability to keep the ASF git repository in sync with GitHub 
> repositories in the Apache org space. Podlings starting incubation are 
> supposed to transfer their repositories to the ASF.
>
> Best,
> Dave
>
> Sent from my iPhone
>
> > On Jun 27, 2023, at 6:33 AM, Brian Proffitt  wrote:
> >
> > The KIE podling has a question that I don't know the answer to. They are
> > wondering if they are required to mirror their source into the Apache
> > GitHib organization? They will be hosting their code in their own GH repo,
> > but they want to know if the mirror is necessary as well.
> >
> > BKP
> >
> >
> > Brian Proffitt
> > VP, Marketing & Publicity
> > Co-organizer, Community Over Code
> > Member, Apache Software Foundation
> > Member, Apache Community Development & Incubator PMCs
> > Red Hat Open Source Program Office
>
>
> -
> 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] Release Apache StreamPark(Incubating) 2.1.1-rc1

[PJ Fanning]

+1 (binding)

I checked the source and binary tar.gz files.
- asc and sha512 files are valid
- LICENSE and NOTICE look ok - I did raise an small issue in your GitHub issues 
[1]
- DISCLAIMER is in the tar.gz files
- no jars in src tar.gz
- I built the jars from scratch using the src tar.gz with no issues

[1] https://github.com/apache/incubator-streampark/issues/2815

On 2023/06/27 11:34:52 Willem Jiang wrote:
> +1 (binding)
> Here is what I checked:
> - The checksums and signatures are validated.
> - The LICENSE and NOTICE files look good to me.
> - There is DISCLAIMER-WIP
> - No binary files in the source release
> - I can build the binary from the source kit.
> 
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> 
> On Mon, Jun 26, 2023 at 10:44 AM Chunjin Mu  wrote:
> >
> > Hello Incubator Community:
> >
> > This is a call for a vote to release Apache StreamPark(Incubating) version 
> > 2.1.1-RC1.
> > The Apache StreamPark community has voted on and approved a proposal to 
> > release Apache StreamPark(Incubating) version 2.1.1-RC1.
> > We now kindly request the Incubator PMC members review and vote on this 
> > incubator release.
> > Apache StreamPark, Make stream processing easier! easy-to-use streaming 
> > application development framework and operation platform.
> >
> > StreamPark community vote thread:
> > https://lists.apache.org/thread/mxrp760t5xy1fd6rs3fggj0cxrh7lohb
> >
> > Vote result thread:
> > https://lists.apache.org/thread/6rhodhnblrs8n1vwcoxzmb0knb81sw66
> >
> > The release candidates:
> > https://dist.apache.org/repos/dist/dev/incubator/streampark/2.1.1-RC1/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-streampark/releases/tag/v2.1.1-rc1
> >
> > The artifacts signed with PGP key [E3E3F36B], corresponding to 
> > [muchun...@apache.org], that can be found in keys file:
> > https://downloads.apache.org/incubator/streampark/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
> >
> > More detailed checklist please refer:
> > • 
> > https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> > Steps to validate the release， Please refer to:
> > • https://www.apache.org/info/verification.html
> > • https://streampark.apache.org/community/release/how-to-verify
> >
> >
> > How to Build:
> >
> > 1) clone source code:
> > > git clone -b v2.1.1-rc1 g...@github.com:apache/incubator-streampark.git
> >
> > 2) build project:
> > > cd incubator-streampark && sh ./build.sh
> >
> > or compile by
> > mvn -Pscala-2.11,shaded,webapp,dist -DskipTests clean install
> > mvn -Pscala-2.12,shaded,webapp,dist -DskipTests clean install
> >
> >
> >
> >
> > Thanks,
> >
> > On behalf of Apache StreamPark(Incubating) community
> >
> >
> > Best,
> > ChunJin Mu
> 
> -
> 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] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

[PJ Fanning]

The release looks good to me, generally.

I'm wondering about your LICENSE [1] though.
It doesn't appear to acknowledge some third party code that is borrowed [2] [3].

Apologies if this has been addressed before but I can't find any
discussion about this in previous vote threads.



[1] https://github.com/apache/incubator-opendal/blob/main/LICENSE
[2] 
https://github.com/apache/incubator-opendal/blob/a8ae017877d38a4362099eab6380d8f54fa4ab6f/core/src/raw/http_util/body.rs#L94
[3] 
https://github.com/apache/incubator-opendal/blob/a8ae017877d38a4362099eab6380d8f54fa4ab6f/core/src/services/memcached/backend.rs#L275

On Wed, 28 Jun 2023 at 15:31, Chojan Shang  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) 0.38.0-rc1. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/ny0t1szlkrb8060j0w9gnj45oov18snm
>
> Vote result thread:
>
> https://lists.apache.org/thread/0l64s4w4yh19nzgfhg3cslm7cq10k7yd
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.38.0-rc1/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git branch for the release:
>
> https://github.com/apache/incubator-opendal/tree/release-0.38.0-rc1
>
> Please download, verify, and test.
>
> The VOTE will pass after got 3 binding approve.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
>
> Thanks.
>
> Sincerely,
> PsiACE

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

do we need to go through an Incubator PMC for a build tool?

[PJ Fanning]

Hi everyone,

The Apache Pekko community has a tool that is used as part of building
our web site [1].
sbt-paradox-pekko [2] applies the theme to the Pekko web site. It is
not useful for outside users.
We require that a Java/Scala jar is published because this tool is
used in a number of different Pekko projects (ie different Apache git
repos that the Pekko team maintain).
We haven't yet released an official 1.0.0 jar and are using a snapshot jar.
If we wanted to publish an official 1.0.0 jar, would we need to have
an Incubator PMC vote on it. We will have a Pekko discussion and
possibly a vote if it seems appropriate.

Any insights would be appreciated.

Regards,
PJ

[1] https://pekko.apache.org
[2] https://github.com/apache/incubator-pekko-sbt-paradox

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache OpenDAL(incubating) 0.38.0-rc1 - Incubator Vote Round 1

[PJ Fanning]

Thanks Xuanwo for the explanation.

+1 (binding)

- I checked the downloads and the SHA512 and ASC files are valid.
- LICENSE/NOTICE/DISCLAIMER are fine
- no binary files
- ASF headers on source files
- `cargo build` works fine

On Wed, 28 Jun 2023 at 17:43, Xuanwo  wrote:
>
> Thanks for raising those questions!
>
> - For 
> https://github.com/apache/incubator-opendal/blob/a8ae017877d38a4362099eab6380d8f54fa4ab6f/core/src/raw/http_util/body.rs#L94
>
> `Borrow` here is more like `Inspired`, we don't take hyper's code directly. 
> We should update the comments here.
>
> hyper code can be found here: 
> https://docs.rs/hyper/latest/src/hyper/body/to_bytes.rs.html#47-82
>
> - For 
> https://github.com/apache/incubator-opendal/blob/a8ae017877d38a4362099eab6380d8f54fa4ab6f/core/src/services/memcached/backend.rs#L275
>
> memcached service has been completely rewritten and no longer contains any 
> code from bb8-memcached. The comment here is outdated and needs to be updated.
>
> On Wed, Jun 28, 2023, at 23:08, PJ Fanning wrote:
> > The release looks good to me, generally.
> >
> > I'm wondering about your LICENSE [1] though.
> > It doesn't appear to acknowledge some third party code that is borrowed [2] 
> > [3].
> >
> > Apologies if this has been addressed before but I can't find any
> > discussion about this in previous vote threads.
> >
> >
> >
> > [1] https://github.com/apache/incubator-opendal/blob/main/LICENSE
> > [2]
> > https://github.com/apache/incubator-opendal/blob/a8ae017877d38a4362099eab6380d8f54fa4ab6f/core/src/raw/http_util/body.rs#L94
> > [3]
> > https://github.com/apache/incubator-opendal/blob/a8ae017877d38a4362099eab6380d8f54fa4ab6f/core/src/services/memcached/backend.rs#L275
> >
> > On Wed, 28 Jun 2023 at 15:31, Chojan Shang  wrote:
> >>
> >> Hello Incubator PMC,
> >>
> >> The Apache OpenDAL community has voted and approved the release of Apache
> >> OpenDAL(incubating) 0.38.0-rc1. We now kindly request the IPMC members
> >> review and vote for this release.
> >>
> >> OpenDAL is a data access layer that allows users to easily and efficiently
> >> retrieve data from various storage services in a unified way.
> >>
> >> OpenDAL community vote thread:
> >>
> >> https://lists.apache.org/thread/ny0t1szlkrb8060j0w9gnj45oov18snm
> >>
> >> Vote result thread:
> >>
> >> https://lists.apache.org/thread/0l64s4w4yh19nzgfhg3cslm7cq10k7yd
> >>
> >> The release candidate:
> >>
> >> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.38.0-rc1/
> >>
> >> This release has been signed with a PGP available here:
> >>
> >> https://downloads.apache.org/incubator/opendal/KEYS
> >>
> >> Git branch for the release:
> >>
> >> https://github.com/apache/incubator-opendal/tree/release-0.38.0-rc1
> >>
> >> Please download, verify, and test.
> >>
> >> The VOTE will pass after got 3 binding approve.
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove with the reason
> >>
> >> To learn more about apache opendal, please see https://opendal.apache.org/
> >>
> >> Checklist for reference:
> >>
> >> [ ] Download links are valid.
> >> [ ] Checksums and signatures.
> >> [ ] LICENSE/NOTICE files exist
> >> [ ] No unexpected binary files
> >> [ ] All source files have ASF headers
> >> [ ] Can compile from source
> >>
> >> More detailed checklist please refer to:
> >> https://github.com/apache/incubator-opendal/tree/main/scripts
> >>
> >> To compile from source, please refer to:
> >> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
> >>
> >>
> >> Thanks.
> >>
> >> Sincerely,
> >> PsiACE
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
>
> --
> Xuanwo
>
> -
> 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

[VOTE] Release Apache Pekko(incubating) 1.0.0-RC2

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating) version 1.0.0-RC2.

A vote has already happened on the Apache Pekko dev list:

https://lists.apache.org/thread/dzjmzypxsqg1jx8j25rx4ld5yjpfmxfj

Result thread:

https://lists.apache.org/thread/lpgprqlktpd9rbvz0cgjvpzrmq020b9x

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.0-RC2/

This release has been signed with a PGP key available here:

https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS

Release Notes:

https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.0-RC2/RELEASE_NOTES_1.0.0.txt

Git branch for the release:

https://github.com/apache/incubator-pekko/tree/v1.0.0-RC2
Git commit ID: 2f8ef56626066f7f859c7ed77ca1c69950fd70b1

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging";


The vote will be left open until 23:00 UTC on 3 July 2023.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] All source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Thanks,

PJ Fanning

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[CANCEL] [VOTE] Release Apache Pekko(incubating) 1.0.0-RC2

[PJ Fanning]

I'll cancel this. Justin McLean says that we need 3 PPMC votes and we don't 
have those yet. I can't find any Incubator docs about the 3 PPMC votes rule but 
it does seem like a convention.


On 2023/06/29 00:10:14 PJ Fanning wrote:
> Hello Incubator Community,
> 
> This is a call for a vote to release Apache Pekko(incubating) version 
> 1.0.0-RC2.
> 
> A vote has already happened on the Apache Pekko dev list:
> 
> https://lists.apache.org/thread/dzjmzypxsqg1jx8j25rx4ld5yjpfmxfj
> 
> Result thread:
> 
> https://lists.apache.org/thread/lpgprqlktpd9rbvz0cgjvpzrmq020b9x
> 
> The release candidate:
> 
> https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.0-RC2/
> 
> This release has been signed with a PGP key available here:
> 
> https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS
> 
> Release Notes:
> 
> https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.0-RC2/RELEASE_NOTES_1.0.0.txt
> 
> Git branch for the release:
> 
> https://github.com/apache/incubator-pekko/tree/v1.0.0-RC2
> Git commit ID: 2f8ef56626066f7f859c7ed77ca1c69950fd70b1
> 
> Please download, verify, and test.
> 
> We have also staged jars in the Apache Nexus Repository. These were
> built with the same code
> as appears in this Source Release Candidate. We would appreciate if
> users could test with these too.
> If anyone finds any serious problems with these jars, please also
> notify us on this thread.
> 
> https://repository.apache.org/content/groups/staging/org/apache/pekko/
> 
> In sbt, you can add this resolver.
> 
> resolvers += "Apache Pekko Staging" at
> "https://repository.apache.org/content/groups/staging";
> 
> 
> The vote will be left open until 23:00 UTC on 3 July 2023.
> 
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
> 
> To learn more about Apache Pekko, please see https://pekko.apache.org/
> 
> Checklist for reference:
> 
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
> 
> To compile from the source, please refer to:
> 
> https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> 
> Some notes about verifying downloads can be found at:
> 
> https://pekko.apache.org/download.html#verifying-downloads
> 
> 
> Here is my +1 (binding).
> 
> Thanks,
> 
> PJ Fanning
> 
> -
> 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

release votes - should there be a minimum number of days that the vote is open for?

[PJ Fanning]

Hi everyone,

I'll go with the flow on this but I've noticed that some release votes specify 
details about some minimum number of days that the thread will be open for. 
Some other vote threads do not specify a time line and are liable to lead to an 
announcement of a result as soon as 3 votes come in.

I favour having transparency on this. Not everyone is available to look at the 
release candidates on the day the vote starts.

If the general consensus is that it's up to the person calling the vote to 
decide, then that's fine.
The release management page expresses no opinion on this [1]

Regards,
PJ

[1] https://incubator.apache.org/guides/releasemanagement.html

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: release votes - should there be a minimum number of days that the vote is open for?

[PJ Fanning]

Thanks Hans for the link. I knew there was a 3 day requirement, I just wasn't 
sure where it was documented.

I looked at the general list again and I was incorrect. The votes seem to 
always adhere to the 3 day rule.

On 2023/07/01 11:45:49 hans.van.akel...@gmail.com wrote:
> Hi PJ,
> 
> If we look at the Release policy it states that it SHOULD remain open for at 
> least 72 hours [1].
> In case we are talking about an emergency release/patch the 72 hours rule can 
> be ignored.
> 
> Cheers,
> Hans
> 
> [1] https://www.apache.org/legal/release-policy.html#release-approval
> On 1 Jul 2023 at 13:14 +0200, general@incubator.apache.org, wrote:
> >
> > https://incubator.apache.org/guides/releasemanagement.html
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

[PJ Fanning]

Adding the Incubator general list.

My view would be that non-snapshot binary artifacts should be signed
with a personal signing key - ideally the signing key that was used to
release the related source release. Unfortunately, this would mean
adding a user's signing key to the Apache GitHub account as a secret
so that the automated GitHub Action job could access it. I don't see
how we could allow personal signing keys to be added like this.

On Mon, 3 Jul 2023 at 10:18, tison  wrote:
>
> cc security
>
> Missed in the first place.
>
> Best,
> tison.
>
>
> tison  于2023年6月29日周四 22:21写道：
>>
>> Hi security team members,
>>
>> I'm tison from OpenDAL Podling[1], a Rust lib providing Java binding.
>>
>> I already verify that GitHub Actions work well for automatically deploying 
>> OpenDAL Java binding[2].
>>
>> When integrating it with upstream (apache/incuabtor-opendal), I met a 
>> problem that deploying Maven projects requires NEXUS credentials. For my 
>> personal repo, I can config my Apache ID and password as secrets. For apache 
>> repos, it requires handing over the credentials to INFRA team member. Even I 
>> can trust the member, it's a bit less than awesome.
>>
>> Fortunately, INFRA provides two org-wise secrets NEXUS_USER and NEXUS_PW for 
>> doing so[3]. But it's limited to deploying snapshots only. INFRA member 
>> suggested me to consult security team for approval for such automatic 
>> deployment and they would help to grant related permissions if approved.
>>
>> Please help review the request to support ASF projects deploying Maven 
>> project via GitHub Actions.
>>
>> Best,
>> tison.
>>
>> [1] http://github.com/apache/incubator-opendal
>> [2] https://github.com/tisonkun/ci-opendal/actions/runs/5326589752
>> [3] 
>> https://github.com/apache/incubator-opendal/blob/f887b671c0aae523d8862762eec71e6179e0975c/.github/workflows/bindings_java.yml#L192
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

[PJ Fanning]

One of my Pekko colleagues found that this process is documented. I
wasn't aware that this approach has been approved as long as the
security team signs off.

https://infra.apache.org/release-signing.html#automated-release-signing

On Mon, 3 Jul 2023 at 12:04, tison  wrote:
>
> Update mailing list. Or if I should start a new thread totally?
>
> Best,
> tison.
>
>
> tison  于2023年7月3日周一 19:00写道：
>
> > Hi Daniel,
> >
> > Thanks for your information! That can be an alternative for the signing
> > key.
> >
> > Right now the blocker I met is 403 from the Nexus server which I suspect
> > is the lack of permissions from the Nexus credentials. Could you confirm or
> > correct it?
> >
> > Best,
> > tison.
> >
> >
> > tison  于2023年7月3日周一 18:58写道：
> >
> >> Hi PJ,
> >>
> >> Thanks for sharing your thoughts!
> >>
> >> For signing key, it's a resolved topic from my perspective. I use -
> >>
> >> 1. A signing key commented with OPENDAL CODE AUTO SIGNING KEY[1]
> >> 2. Load the key from our 1password service, while since it's a specific
> >> key, I feel comfortable to pass it to INFRA member and configure as a
> >> secret alternatively.
> >>
> >> Best,
> >> tison.
> >>
> >> [1] https://dist.apache.org/repos/dist/release/incubator/opendal/KEYS
> >>
> >>
> >> PJ Fanning  于2023年7月3日周一 18:52写道：
> >>
> >>> Adding the Incubator general list.
> >>>
> >>> My view would be that non-snapshot binary artifacts should be signed
> >>> with a personal signing key - ideally the signing key that was used to
> >>> release the related source release. Unfortunately, this would mean
> >>> adding a user's signing key to the Apache GitHub account as a secret
> >>> so that the automated GitHub Action job could access it. I don't see
> >>> how we could allow personal signing keys to be added like this.
> >>>
> >>> On Mon, 3 Jul 2023 at 10:18, tison  wrote:
> >>> >
> >>> > cc security
> >>> >
> >>> > Missed in the first place.
> >>> >
> >>> > Best,
> >>> > tison.
> >>> >
> >>> >
> >>> > tison  于2023年6月29日周四 22:21写道：
> >>> >>
> >>> >> Hi security team members,
> >>> >>
> >>> >> I'm tison from OpenDAL Podling[1], a Rust lib providing Java binding.
> >>> >>
> >>> >> I already verify that GitHub Actions work well for automatically
> >>> deploying OpenDAL Java binding[2].
> >>> >>
> >>> >> When integrating it with upstream (apache/incuabtor-opendal), I met a
> >>> problem that deploying Maven projects requires NEXUS credentials. For my
> >>> personal repo, I can config my Apache ID and password as secrets. For
> >>> apache repos, it requires handing over the credentials to INFRA team
> >>> member. Even I can trust the member, it's a bit less than awesome.
> >>> >>
> >>> >> Fortunately, INFRA provides two org-wise secrets NEXUS_USER and
> >>> NEXUS_PW for doing so[3]. But it's limited to deploying snapshots only.
> >>> INFRA member suggested me to consult security team for approval for such
> >>> automatic deployment and they would help to grant related permissions if
> >>> approved.
> >>> >>
> >>> >> Please help review the request to support ASF projects deploying
> >>> Maven project via GitHub Actions.
> >>> >>
> >>> >> Best,
> >>> >> tison.
> >>> >>
> >>> >> [1] http://github.com/apache/incubator-opendal
> >>> >> [2] https://github.com/tisonkun/ci-opendal/actions/runs/5326589752
> >>> >> [3]
> >>> https://github.com/apache/incubator-opendal/blob/f887b671c0aae523d8862762eec71e6179e0975c/.github/workflows/bindings_java.yml#L192
> >>> >>
> >>>
> >>> -
> >>> 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: do we need to go through an Incubator PMC for a build tool?

[PJ Fanning]

Adding the Pekko mentors to the thread if that's ok.

It's not a blocker for us to use a snapshot version of the
Pekko-specific build tool but it would be tidier if we could release a
stable version to Maven Central. If this requires us to release a
source artifact via the full voting procedure then that is fine. I
just want to make sure that this is a necessary step before going that
route.

On Wed, 28 Jun 2023 at 18:38, PJ Fanning  wrote:
>
> Hi everyone,
>
> The Apache Pekko community has a tool that is used as part of building
> our web site [1].
> sbt-paradox-pekko [2] applies the theme to the Pekko web site. It is
> not useful for outside users.
> We require that a Java/Scala jar is published because this tool is
> used in a number of different Pekko projects (ie different Apache git
> repos that the Pekko team maintain).
> We haven't yet released an official 1.0.0 jar and are using a snapshot jar.
> If we wanted to publish an official 1.0.0 jar, would we need to have
> an Incubator PMC vote on it. We will have a Pekko discussion and
> possibly a vote if it seems appropriate.
>
> Any insights would be appreciated.
>
> Regards,
> PJ
>
> [1] https://pekko.apache.org
> [2] https://github.com/apache/incubator-pekko-sbt-paradox

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: do we need to go through an Incubator PMC for a build tool?

[PJ Fanning]

Thanks Claude but I am not familiar with the terminology of 'Petri
route'. Would you be able to provide more detail?

So far based on the existing feedback - the aim is to just set up an
RC for this component and go through the regular voting process on it.
A Pekko community discussion and vote followed by an Incubator team
vote.


On Tue, 4 Jul 2023 at 10:44, Claude Warren  wrote:
>
> You could try the Petri route if the devs are ASF members.
>
> On Mon, Jul 3, 2023 at 5:12 PM Sheng Wu  wrote:
>
> > Hi
> >
> > If we want that jar under asf package on maven central, yes, a new version
> > is required a vote on dev first, then incubator.
> > Meanwhile, if we have all mentors(ipmc members as well) voted, we just
> > need to carry votes to incubator mail list, and another 3 days.
> >
> > Just one thing, if the jar has dependencies, we need to check license
> > compatibility.
> >
> > PJ Fanning 于2023年7月3日 周一17:06写道：
> >
> >> Adding the Pekko mentors to the thread if that's ok.
> >>
> >> It's not a blocker for us to use a snapshot version of the
> >> Pekko-specific build tool but it would be tidier if we could release a
> >> stable version to Maven Central. If this requires us to release a
> >> source artifact via the full voting procedure then that is fine. I
> >> just want to make sure that this is a necessary step before going that
> >> route.
> >>
> >> On Wed, 28 Jun 2023 at 18:38, PJ Fanning  wrote:
> >> >
> >> > Hi everyone,
> >> >
> >> > The Apache Pekko community has a tool that is used as part of building
> >> > our web site [1].
> >> > sbt-paradox-pekko [2] applies the theme to the Pekko web site. It is
> >> > not useful for outside users.
> >> > We require that a Java/Scala jar is published because this tool is
> >> > used in a number of different Pekko projects (ie different Apache git
> >> > repos that the Pekko team maintain).
> >> > We haven't yet released an official 1.0.0 jar and are using a snapshot
> >> jar.
> >> > If we wanted to publish an official 1.0.0 jar, would we need to have
> >> > an Incubator PMC vote on it. We will have a Pekko discussion and
> >> > possibly a vote if it seems appropriate.
> >> >
> >> > Any insights would be appreciated.
> >> >
> >> > Regards,
> >> > PJ
> >> >
> >> > [1] https://pekko.apache.org
> >> > [2] https://github.com/apache/incubator-pekko-sbt-paradox
> >>
> > --
> > Sheng Wu 吴晟
> >
> > Apache SkyWalking
> > Apache Incubator
> > Apache ShardingSphere, ECharts, DolphinScheduler podlings
> > Zipkin
> > Twitter, wusheng1108
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [REQUEST] Grant permission to deploy Maven project via GitHub Actions

[PJ Fanning]

Hi Tison,

Would it be possible to provide us with links to documentation about
how you deploy your binary artifacts and how they can be revoked if a
vote fails?

I think this is useful for IPMC members when they are reviewing your
release candidates. It's nice to review the binaries as well as the
source artifacts, even if the source artifacts are the main point of
the vote.

When staging RCs for review, I tend to use
* dist.apache.org (this is where the source artifacts go anyway)
* repository.apache.org (jars)

Files on dist.apache.org can be deleted when votes fail.
With repository.apache.org, the release is a 2 phase process. You
first push to 'staging' and then you can use its Nexus UI to drop or
release the staged artifacts after the vote.

OpenDAL is mainly in Rust but you also have a large number of language
bindings (see libraries list [1]), existing and planned. So
presumably, you are using a large number of different packaging tools
for your binary releases. Many of us in the IPMC would not be familiar
with all these packaging tools.

You may already have documentation and if so, could you share a link?

If there is no shareable documentation, would you be able to tell us
which Crate Registry do you use for your RC Rust binaries? Do we have
a custom registry that allows us to remove the binaries for releases
that fail?

Any information would be appreciated.

Regards,
PJ

[1] https://github.com/apache/incubator-opendal

On Tue, 4 Jul 2023 at 05:29, Greg Stein  wrote:
>
> Tison: STOP cross-posting between private and public lists. You have been
> advised to stop doing so once, and this is now TWICE. No more.
>
> Regards,
> Greg Stein
> Infrastructure Administrator, ASF
>
>
> On Mon, Jul 3, 2023 at 6:01 AM tison  wrote:
>
> > Hi Daniel,
> >
> > Thanks for your information! That can be an alternative for the signing
> > key.
> >
> > Right now the blocker I met is 403 from the Nexus server which I suspect is
> > the lack of permissions from the Nexus credentials. Could you confirm or
> > correct it?
> >
> > Best,
> > tison.
> >
> >
> > tison  于2023年7月3日周一 18:58写道：
> >
> > > Hi PJ,
> > >
> > > Thanks for sharing your thoughts!
> > >
> > > For signing key, it's a resolved topic from my perspective. I use -
> > >
> > > 1. A signing key commented with OPENDAL CODE AUTO SIGNING KEY[1]
> > > 2. Load the key from our 1password service, while since it's a specific
> > > key, I feel comfortable to pass it to INFRA member and configure as a
> > > secret alternatively.
> > >
> > > Best,
> > > tison.
> > >
> > > [1] https://dist.apache.org/repos/dist/release/incubator/opendal/KEYS
> > >
> > >
> > > PJ Fanning  于2023年7月3日周一 18:52写道：
> > >
> > >> Adding the Incubator general list.
> > >>
> > >> My view would be that non-snapshot binary artifacts should be signed
> > >> with a personal signing key - ideally the signing key that was used to
> > >> release the related source release. Unfortunately, this would mean
> > >> adding a user's signing key to the Apache GitHub account as a secret
> > >> so that the automated GitHub Action job could access it. I don't see
> > >> how we could allow personal signing keys to be added like this.
> > >>
> > >> On Mon, 3 Jul 2023 at 10:18, tison  wrote:
> > >> >
> > >> > cc security
> > >> >
> > >> > Missed in the first place.
> > >> >
> > >> > Best,
> > >> > tison.
> > >> >
> > >> >
> > >> > tison  于2023年6月29日周四 22:21写道：
> > >> >>
> > >> >> Hi security team members,
> > >> >>
> > >> >> I'm tison from OpenDAL Podling[1], a Rust lib providing Java binding.
> > >> >>
> > >> >> I already verify that GitHub Actions work well for automatically
> > >> deploying OpenDAL Java binding[2].
> > >> >>
> > >> >> When integrating it with upstream (apache/incuabtor-opendal), I met a
> > >> problem that deploying Maven projects requires NEXUS credentials. For my
> > >> personal repo, I can config my Apache ID and password as secrets. For
> > >> apache repos, it requires handing over the credentials to INFRA team
> > >> member. Even I can trust the member, it's a bit less than awesome.
> > >> >>
> > >> >> Fortunately, INFRA provides two org-wise secrets NEXUS_USER

[VOTE] Release Apache Pekko(incubating) 1.0.0-RC3

[PJ Fanning]

Hello Incubator community,

This is a call for a vote to release Apache Pekko(incubating) version 1.0.0-RC3.

The Pekko community vote result:

https://lists.apache.org/thread/dwfc5h4jdvwld4z6fhzm87x1fyrv3gw4

The Pekko community vote thread:

https://lists.apache.org/thread/gkn1b3mddgo82doj4c0f38o26wwbm0fs

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.0-RC3/

This release has been signed with a PGP key available here:

https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS

Release Notes:

https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Core+Release+Notes

Git branch for the release:

https://github.com/apache/incubator-pekko/tree/v1.0.0-RC3
Git commit ID: 4ce1095b4b48f5cdd31342ab9f0950bd44a2829a

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging";


The vote will be left open until 23:00 UTC on 8 July 2023.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] All source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Ryan Skraba has also voted +1 (binding) on the Pekko community vote.

Thanks,

PJ Fanning (Apache Pekko PPMC member and Incubator PMC member)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Access to Incubator Wiki - Submission of Podling report - Apache Training

[PJ Fanning]

The cwiki Confluence instance requires your Apache username and
password. If you login with those credentials and you still can't edit
the page, you should check what your setup is in the whimsy tool[1].

[1] https://whimsy.apache.org

On Wed, 5 Jul 2023 at 19:34, Lars Francke  wrote:
>
> Hi Mirko,
>
> I'm afraid I can't remember the procedure to get access to that Wiki
> but I will read it now and move it there!
>
> Thank you very much.
>
> Cheers,
> Lars
>
> On Wed, Jul 5, 2023 at 2:25 PM Mirko Kämpf  wrote:
> >
> > Hello,
> >
> > I intend to submit the draft of the podling report to this page:
> > *https://cwiki.apache.org/confluence/display/incubator/July2023#training
> > *
> >
> > But unfortunately, I still have no write permission to this wiki.
> > My username is: mirko.kae...@gmail.com
> >
> >
> > Here is the draft in the *Apache Training Wiki:*
> > https://cwiki.apache.org/confluence/display/TRAINING/Podling+Reports#PodlingReports-July2023
> > 
> >
> > And at the end of this mail is the full text of the draft.
> >
> > It has been shared on the project's developer list.
> > No comments so far.
> >
> > Cheers,
> > Mirko
> >
> >
> >
> >
> >
> > July 2023
> >
> > *Training
> > *
> >
> > The Training project aims to develop resources which can be used for
> > training purposes in various media formats, languages and for various
> > Apache and non-Apache target projects.
> >
> > Training has been incubating since 2019-02-21.
> >
> > In June, we started adjusting the project goals. Besides a pure focus on
> > content creation tools we have identified the need for two additional
> > aspects:
> > (1) For ASF processes some documentation exists, e.g.
> > https://community.apache.org/contributor-ladder, but the ASF member journey
> > is still a challenge for many new members, especially those with less
> > coding experience.
> > As a solution it has been suggested to provide training material for the
> > following problems:
> > * You've just graduated to a TLP. What are the challenges you will now face?
> > * New committer onboarding
> > * New PMC member onboarding
> > * New PMC Chair onboarding
> > * New board member onboarding
> >
> > (2) Creation of some general recommendations/guidelines for:
> >  * managing/validation of training material contributions of arbitrary ASF
> > projects
> > has been propsed.
> >
> > Initial discussion of the topics have been started.
> >
> > *We expand our focus now on the following aspects:*
> >
> > *We have to work on strategies to increase the** participation and the
> > visibility of the project and its goals.*
> >
> > *Besides requests** for contributions from individual contributors** from
> > other Apache projects we want to show what the Apache Training project can
> > offer to those projects**.*
> >
> > *We should build on the assumption that synergy and network effects can
> > help us to increase the community around training and skill management
> > topics.*
> >
> >
> > *Three most important unfinished issues to address before graduating:*
> > 
> >
> >1. Improve the community participation (other Apache projects should
> >actively be linked to this project, since they "have the content")
> >2. *(Re)define the short-, mid-, and long-term goals of the project.*
> >3. *Select an approach to handle non coding / non document related tasks
> >(e.g., community related activities on events)*
> >4. *Create a strategy how this projects contributes to or is supported
> >by other Apache projects*
> >5. Create a tutorial on how the tools provided by this project can be
> >used to create own content
> >6. Review current policies around contribution review and releases to
> >find a pragmatic compromise
> >
> > *Are there any issues that the IPMC or ASF Board need to be aware of?*
> > 
> >
> > The Training Project needs more contribution from other Apache projects,
> > hence a clear communication strategy for interlinking existing projects
> > with the Apache Training project is needed.
> >
> > We need feedback from other Apache projects on the presentations and
> > trainings developed till now.
> >
> >
> >
> > *In order to improve this collaboration we suggest to investigate the
> > status of other project’s documentation in a systematic approach,
> > especially with an eye on available training related material.*
> >
> > *How has the community developed since the last report?*
> > 

Re: [VOTE] Release Apache Pekko(incubating) 1.0.0-RC3

[PJ Fanning]

Adding the Pekko mentors, if that's ok.

If anyone has time to review the RC, we would really appreciate it.

On Wed, 5 Jul 2023 at 14:10, Ryan Skraba  wrote:
>
> Just for the form here (more details in dev@pekko list)
>
> +1 (binding)
>
> This code is already very mature, I focused on the form and process to
> getting this (very anticipated) release out!
>
> Thanks so much for doing this work.  I look forward to seeing the other
> pekko artifacts released!
>
> Ryan
>
>
>
> On Wed, Jul 5, 2023 at 1:12 AM PJ Fanning  wrote:
>
> > Hello Incubator community,
> >
> > This is a call for a vote to release Apache Pekko(incubating) version
> > 1.0.0-RC3.
> >
> > The Pekko community vote result:
> >
> > https://lists.apache.org/thread/dwfc5h4jdvwld4z6fhzm87x1fyrv3gw4
> >
> > The Pekko community vote thread:
> >
> > https://lists.apache.org/thread/gkn1b3mddgo82doj4c0f38o26wwbm0fs
> >
> > The release candidate:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.0-RC3/
> >
> > This release has been signed with a PGP key available here:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS
> >
> > Release Notes:
> >
> > https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Core+Release+Notes
> >
> > Git branch for the release:
> >
> > https://github.com/apache/incubator-pekko/tree/v1.0.0-RC3
> > Git commit ID: 4ce1095b4b48f5cdd31342ab9f0950bd44a2829a
> >
> > Please download, verify, and test.
> >
> > We have also staged jars in the Apache Nexus Repository. These were
> > built with the same code
> > as appears in this Source Release Candidate. We would appreciate if
> > users could test with these too.
> > If anyone finds any serious problems with these jars, please also
> > notify us on this thread.
> >
> > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> >
> > In sbt, you can add this resolver.
> >
> > resolvers += "Apache Pekko Staging" at
> > "https://repository.apache.org/content/groups/staging";
> >
> >
> > The vote will be left open until 23:00 UTC on 8 July 2023.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > To learn more about Apache Pekko, please see https://pekko.apache.org/
> >
> > Checklist for reference:
> >
> > [ ] Download links are valid.
> > [ ] Checksums and signatures.
> > [ ] LICENSE/NOTICE files exist
> > [ ] No unexpected binary files
> > [ ] All source files have ASF headers
> > [ ] Can compile from source
> >
> > To compile from the source, please refer to:
> >
> >
> > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> >
> > Some notes about verifying downloads can be found at:
> >
> > https://pekko.apache.org/download.html#verifying-downloads
> >
> >
> > Here is my +1 (binding).
> >
> > Ryan Skraba has also voted +1 (binding) on the Pekko community vote.
> >
> > Thanks,
> >
> > PJ Fanning (Apache Pekko PPMC member and Incubator PMC member)
> >
> > -
> > 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

[VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating) Sbt
Paradox Plugin version 1.0.0-RC1.

The Pekko vote thread:

https://lists.apache.org/thread/n8gklhdn82dk8n0mhyt5morczhd5dfnr

The Pekko community thread:

https://lists.apache.org/thread/57vqzyhpsz02njjklgr8j4rjztbk60n4


The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/sbt-paradox-1.0.0-RC1/

This release has been signed with a PGP key available here:

https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS

Purpose:

This is a build tool used in Apache Pekko projects to build the web pages.

Git branch for the release:

https://github.com/apache/incubator-pekko-sbt-paradox/releases/tag/v1.0.0-RC1
Git commit ID: 4003ccdee81abce31a39c337abfcfde0b924bc62

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging";

The vote will be left open until 23:00 UTC on 13 July 2023.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] All source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko-sbt-paradox#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Thanks,

PJ Fanning

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Pekko, incubating, 1.0.0-RC3

[PJ Fanning]

Hi everyone,

The vote passes with 3 binding +1s and no other votes.

PJ Fanning
Ryan Skraba
Ayush Saxena

Vote thread:

https://lists.apache.org/thread/k4xd18lnt2g1v5ofovzdnoklglpo1hy1

It will take a few days to complete the release and announcements.

Thanks to everyone who reviewed the release artifacts.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

[PJ Fanning]

Thanks Justin. We can fix up those issues and do another RC.

The one I am confused about is:
- LICENSE is missing some 3rd party code [2] (Mozilla licensed)

There is no license header on the file we copied and slightly modified.

https://github.com/lightbend/paradox/blob/8e30c341f1f8351a19b71599219d2f636ba68eb4/themes/generic/src/main/assets/js/groups.js

Its project license is the Apache License.

https://github.com/lightbend/paradox/blob/8e30c341f1f8351a19b71599219d2f636ba68eb4/LICENSE

Can you tell us why you think this file is in fact Mozilla licensed?





On Wed, 12 Jul 2023 at 01:15, Justin Mclean  wrote:
>
> Hi,
>
> Sorry but it’s - 1 (binding from me). The source release seems to contain 
> code that is licensed under a Category B Mozilla license and missing headers 
> from files.
>
> I checked:
> - incubating in name
> - signatures and hashes are fine
> - DISCLAIMER exists
> - LICENSE is missing some 3rd party code [2] (Mozilla licensed)
> - This file is also under the MIT license [3] but not mentioned in LICENSE
> - Files are missing ASF or other header [1][4][5]
> - No unexpected binary files
> - Can compile from source
>
> Kind Regards,
> Justin
>
> 1.  ./plugin/src/main/scala/org/apache/pekko/PekkoParadoxPlugin.scala
> 2.  ./theme/src/main/assets/assets/javascripts/groups.js
> 3.   ./theme/src/main/assets/assets/javascripts/paradox-material-theme.js
> 4.  ./theme/src/main/assets/assets/stylesheets/pekko-theme.css
> 5.  ./theme/src/main/assets/partials/extra_nav_links.st
>
>
> -
> 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] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

[PJ Fanning]

Thanks Matthew. It makes sense that sample code is often licensed
under more permissive licenses.

Working out the date on which this documentation was published is
going to be tricky. I followed a GitHub link [1] from the page
referenced in groups.js and the file history is pretty garbled due to
file renames and eventually runs into a dead end.

We may have to include both the CC0 and MIT licenses, just in case.

[1] 
https://github.com/mdn/content/blob/main/files/en-us/web/api/document/cookie/index.md

On Thu, 13 Jul 2023 at 08:42, Matthew de Detrich
 wrote:
>
> I just had a quick look into this and according to
> https://github.com/mdn/content/blob/main/LICENSE.md#licenses-for-code-examples-and-snippets
> the licensed code snippet (which is what the source file in question is
> referring to) it should be CC0 license if the code snippet was added after
> August 20, 2010 and if it was added before its MIT license (see
> https://github.com/mdn/content/blob/main/LICENSE.md#added-before-august-20-2010
> ).
>
> MIT is compatible with Apache 2 license and CCO is also compatible with
> Apache 2 license since its effectively public domain (see
> https://creativecommons.org/share-your-work/public-domain/cc0/ and
> https://wiki.creativecommons.org/wiki/CC0_FAQ#Can_anyone_use_a_work_that_is_distributed_under_CC0.3F).
> It would be quite shocking if we couldn't use CCO source code as the whole
> point of the license is to waive all copyright, ip and related rights and
> this is why CCO is typically used for code samples/configuration (it's to
> avoid problems like this) and Apache seems to agree as well, see
> https://www.apache.org/legal/resolved.html#handling-public-domain-licensed-works,
> specifically
>
> > You can include works in the public domain (or covered by a license
> treated similarly) within Apache products. You must provide attribution (in
> a similar fashion to the Category A list).
>
> > Licenses that we treat as similar to public domain:
> > Creative Commons CC0 “No Rights Reserved”
> > Creative Commons Public Domain Certification
>
> Kind regards,
> Matthew
>
>
> On Thu, Jul 13, 2023 at 3:08 AM Justin Mclean 
> wrote:
>
> >
> > Hi,
> >
> > > There is no license header on the file we copied and slightly modified.
> > >
> > >
> > https://github.com/lightbend/paradox/blob/8e30c341f1f8351a19b71599219d2f636ba68eb4/themes/generic/src/main/assets/js/groups.js
> >
> > That contains code from [1] which I thought was licensed under the MPL
> > [2], but it looks like this situation may have changed and depends on the
> > date that code was submitted. [3] So either, depending on the license, the
> > code can’t be included in a source release OR it can but you n need to add
> > the license information to LICENSE.
> >
> > > Its project license is the Apache License.
> >
> > That may be but parts of that file are not under the terms of the Apache
> > License.
> >
> > Kind Regards,
> > Justin
> >
> > 1. https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie
> > 2. https://www.mozilla.org/en-US/about/legal/terms/mozilla/
> > 3. https://github.com/mdn/content/blob/main/LICENSE.md
>
>
>
> --
>
> Matthew de Detrich
>
> *Aiven Deutschland GmbH*
>
> Immanuelkirchstraße 26, 10405 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> *m:* +491603708037
>
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache Pekko (Incubating) 1.0.0 available

[PJ Fanning]

Hi everyone,

The Apache Pekko (Incubating) Team is happy to announce the release of
Apache Pekko (Incubating) 1.0.0.

Apache Pekko (Incubating) is an open source toolkit and runtime
simplifying the construction of concurrent and distributed
applications on the JVM. It is a fork of Akka and has come about
because Akka has moved from being Apache licensed to being licensed
under a Business Software License.

This release covers the core modules. Other modules like Pekko HTTP
will be released separately (and hopefully soon).

Download Links:
https://pekko.apache.org/download.html#pekko-core

Release Notes:
https://pekko.apache.org/docs/pekko/current/release-notes/index.html#1-0-0

Website:
https://pekko.apache.org/

Issues:
https://github.com/apache/incubator-pekko/issues

Mailing list: d...@pekko.apache.org

Jars are published to Maven Central using the groupId: org.apache.pekko

Thanks to everyone who participated in the development and release.

Apache Pekko (Incubating) Team

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

[PJ Fanning]

Thanks Justin for clarifying. Based on Johannes' input, we think that
we don't need to add anything to the license for these Mozilla links.
The links are there to point at the API documentation and none of the
sample code that appears in that documentation was copied.

On Fri, 14 Jul 2023 at 00:05, Justin Mclean  wrote:
>
> HI,
>
> Both CC0 [1] and MIT [2] are treated as Category A licenses so can be 
> included in a source release.
>
> Kind Regards,
> Justin
>
> 1. 
> https://www.apache.org/legal/resolved.html#handling-public-domain-licensed-works
> 2. https://www.apache.org/legal/resolved.html#category-a

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

[PJ Fanning]

I have checked random strings from the groups.js and have not found
them in the mozilla file.

https://developer.mozilla.org/en-US/docs/Web/API/Document/cookie

Justin - could you highlight one or 2 examples where you think code was copied?

On Fri, 14 Jul 2023 at 00:43, Justin Mclean  wrote:
>
> Hi,
>
> Looking as the code I disagree, you can see parts of the code have been 
> copied and modified.
>
> Kind Regard
> Justin
>
> > On 14 Jul 2023, at 9:12 am, PJ Fanning  wrote:
> >
> > Thanks Justin for clarifying. Based on Johannes' input, we think that
> > we don't need to add anything to the license for these Mozilla links.
> > The links are there to point at the API documentation and none of the
> > sample code that appears in that documentation was copied.
> >
> > On Fri, 14 Jul 2023 at 00:05, Justin Mclean  
> > wrote:
> >>
> >> HI,
> >>
> >> Both CC0 [1] and MIT [2] are treated as Category A licenses so can be 
> >> included in a source release.
> >>
> >> Kind Regards,
> >> Justin
> >>
> >> 1. 
> >> https://www.apache.org/legal/resolved.html#handling-public-domain-licensed-works
> >> 2. https://www.apache.org/legal/resolved.html#category-a
> >
> > -
> > 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
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

[PJ Fanning]

So the groups.js has some documentation from that mozilla page copied
as a comment. This is not an uncommon practice. The text is not in
example code and most people would assume that the copying of small
fragments of documentation as code comments is fair use.

Since the comment is not important, we can remove it.

Is there any non-comment content in groups.js that is copied? I still
don't see any examples of this.

On Fri, 14 Jul 2023 at 01:52, Justin Mclean  wrote:
>
> HI,
>
> Sorry I meant to say:
> “...but the cookie code puts method calls on SEPERATE lines in the same 
> style...“
>
> Justin
> -
> 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] Release Apache Pekko(incubating) Sbt Paradox Plugin 1.0.0-RC1

[PJ Fanning]

The -1 is accepted and the vote is cancelled.

Other than the groups.js issue, we have already addressed all the
other issues in the git repo in preparation for an eventual RC2.


On Fri, 14 Jul 2023 at 09:31, Claude Warren  wrote:
>
> Justin,
>
> I agree with 80% of your assessment and agree that a -1 is warranted.  
> However, [2] is clearly a copy of the original lightbend code [6] which is 
> licensed under Apache V2.  Lightbend's LICENSE file shows no other 
> attribution and the URLs in the code appear to point to documentation about 
> Cookies and how they function in general and how to access them via 
> javascript.  I do not see the level of similarity between the example code 
> and the code in question to assume that it was copied.  I do note that there 
> are only so many ways to set and get cookies and that most of the code seems 
> to fall under the generic cookie API.
>
> The Pekko code clearly has the Lightbend attribution and Apache License 2.0 
> reference.
>
> For these reasons I think you should withdraw [2] from your list of issues.
>
> Claude
>
> [6]  
> https://github.com/lightbend/paradox/blob/8e30c341f1f8351a19b71599219d2f636ba68eb4/themes/generic/src/main/assets/js/groups.js
>
>
> On 2023/07/12 00:14:45 Justin Mclean wrote:
> > Hi,
> >
> > Sorry but it’s - 1 (binding from me). The source release seems to contain 
> > code that is licensed under a Category B Mozilla license and missing 
> > headers from files.
> >
> > I checked:
> > - incubating in name
> > - signatures and hashes are fine
> > - DISCLAIMER exists
> > - LICENSE is missing some 3rd party code [2] (Mozilla licensed)
> > - This file is also under the MIT license [3] but not mentioned in LICENSE
> > - Files are missing ASF or other header [1][4][5]
> > - No unexpected binary files
> > - Can compile from source
> >
> > Kind Regards,
> > Justin
> >
> > 1.  ./plugin/src/main/scala/org/apache/pekko/PekkoParadoxPlugin.scala
> > 2.  ./theme/src/main/assets/assets/javascripts/groups.js
> > 3.   ./theme/src/main/assets/assets/javascripts/paradox-material-theme.js
> > 4.  ./theme/src/main/assets/assets/stylesheets/pekko-theme.css
> > 5.  ./theme/src/main/assets/partials/extra_nav_links.st
> >
> >
> > -
> > 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
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

clutch repo - is it incorrectly saying Pekko has no distribution area?

[PJ Fanning]

Hi everyone,

It's possible that we haven't created the distribution area properly
and if so, could someone point out how we can fix this?

Clutch Report

https://incubator.apache.org/clutch/

Heading P relates to the distribution area

https://dist.apache.org/repos/dist/release/incubator/

and this has

https://dist.apache.org/repos/dist/release/incubator/pekko

And this has a KEYS file and a release.

Is there something we missed? Is there some yml/xml/conf somewhere
that we need to update?

Any pointers would be appreciated.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache DevLake (Incubating) v0.17.0-rc2

[PJ Fanning]

+1 (binding)

I checked:
- incubating in name
- signatures and hashes are ok
- No unexpected binary files
- LICENSE/NOTICE/DISCLAIMER are fine
- ASF headers exist on most files (exceptions seem ok like .md and .csv)

I tried to build the binaries but they go compiler has sent my laptop into a 
tail spin and I'm going to reboot as soon as soon I send this mail.


On 2023/07/18 12:47:41 Zikuan An wrote:
> Hello everyone,
> 
> This is a call for vote to release Apache DevLake (Incubating) v0.17.0-rc2.
> The Apache DevLake community has voted on and approved a proposal to
> release Apache DevLake (Incubating) version v0.17.0-rc2.
> 
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> Community vote thread:
> 
> https://lists.apache.org/thread/s8dxqob0kcr94klxhd3dlyd3rfy1tsvx
> 
> 
> Community vote result thread:
> 
> https://lists.apache.org/thread/11snoww7k35mlof72870mj56fl5hhrcs
> 
> 
> The release candidates:
> 
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.17.0-incubating-rc2
> 
> 
> Git tag for the release:
> 
> https://github.com/apache/incubator-devlake/releases/tag/v0.17.0-rc2
> 
> 
> Keys to verify the Release Candidate:
> 
> https://downloads.apache.org/incubator/devlake/KEYS
> 
> 
> How to build:
> 
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> 
> 
> 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
> 
> Zikuan An
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Pekko(incubating) 1.0.1-RC1

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating) version 1.0.1-RC1.

The discussion thread:

https://lists.apache.org/thread/9dpqhmy1x9jcq3bfzjjsxssow2cfyfvy

The Pekko Community vote:

https://lists.apache.org/thread/kz51dmo0jc2lo4gbwo63h9hgxrpqn6jr

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.1-RC1/

This release has been signed with a PGP key available here:

https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS

Release Notes:

https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Core+Release+Notes

Git branch for the release:

https://github.com/apache/incubator-pekko/tree/v1.0.1-RC1
Git commit ID: a3f48833c97501a0193f4135f99c5f6ea04a03dd

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging";


The VOTE will remain open for 72 hours or until we have enough binding
approvals.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Thanks,

PJ Fanning (Apache Pekko PPMC member and Incubator PMC member)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] IP Clearance of Pekko HTTP CORS code donation

[PJ Fanning]

Hi everyone,

The Apache Pekko community has voted to accept a code donation - a
CORS module that has been added to the Pekko HTTP repository (a much
larger repository, of which the CORS module is just a small
component).

Vote Result

https://lists.apache.org/thread/yc67o21wg3sj2h364gdpd9j1trofhgnw

Vote Thread

https://lists.apache.org/thread/swhjbg1r1gcl74lf28m6j50s8j09xm95

IP Clearance Form

https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/pekko-http-cors.xml

There appears to be a problem with the building of the HTML for the
Incubator site.

The vote is by lazy consensus and will be left open for 72 hours.

Regards,
PJ

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] IP Clearance of Pekko HTTP CORS code donation

[PJ Fanning]

The code is
https://github.com/lomigmegard/pekko-http-cors/

The PR to add it to Pekko HTTP is
https://github.com/apache/incubator-pekko-http/pull/208

Lomig Mégard has signed an iCLA - by far the largest contributor.
https://lists.apache.org/thread/9y23g0mr8drtsbtvnzkkfs9c54d2dls2

The other contributors only provided very small patches.
2 of them include Matthew de Detrich and I - 2 Pekko PPMC members.




On Sun, 23 Jul 2023 at 00:22, Justin Mclean  wrote:
>
> Hi,
>
> It not easy to check what is being donated here.  Can you point to the 3rd 
> party repo or a tar/zip of the donated code?
>
> I can see an SGA has been signed, but did the contributors agree to the 
> donation and do we have ICLAs for any of them?
>
> Kind Regards,
> Justin
> -
> 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] Release Apache Pekko(incubating) 1.0.1-RC1

[PJ Fanning]

Thanks Ryan. I've removed the `.sha512.asc` files. I built those in error.

On Mon, 24 Jul 2023 at 18:35, Ryan Skraba  wrote:
>
> Hello!
>
> I've validated this RC: 1.0.1-RC1 at r63059
> - The SHA512 hash is OK.
> - The source file is signed correctly.
> - The signature 6BA4DA8B1C88A49428A29C3D0C69C1EF41181E13 is found in the
> KEYS
> file, and on at least one keyserver.
> - The source file is consistent with the GitHub tag v1.0.1-RC1, which
> corresponds to commit
> https://github.com/apache/incubator-pekko/tree/a3f48833c97501a0193f4135f99c5f6ea
> 04a03dd
>   - Some dot-files used for building are excluded, which is OK.
>   - The files explicitly excluded by create_pristine_sources (such as
> .gitignore and the submodule tools/releasing/shared) are not present.
> - Has a LICENSE file and NOTICE files.  The LICENSE file starts with the
> ASL2
> text.
> - Does not contain any compiled binaries.
> - Has many artifacts at
> https://repository.apache.org/content/repositories/orgapachepekko-1014/
>
> I've looked at the difference on GitHub and this is an appropriate patch
> release version.
>
> I've built the artifacts locally and did a (very simple) smoke test on the
> published artifacts.
>
> It looks like you're signing the .sha512 files, which is harmless but
> probably unnecessary.
>
> All my best and congratulations on the first patch release of Pekko!
>
> Ryan Skraba
>
>
> On Mon, Jul 24, 2023 at 5:05 PM Matthew de Detrich
>  wrote:
>
> > I have already done all of the checks as part of the pekko-dev [VOTE]
> >
> > +1 from me
> >
> > Regards
> >
> > On Sat, Jul 22, 2023 at 1:06 AM PJ Fanning  wrote:
> >
> > > Hello Incubator Community,
> > >
> > > This is a call for a vote to release Apache Pekko(incubating) version
> > > 1.0.1-RC1.
> > >
> > > The discussion thread:
> > >
> > > https://lists.apache.org/thread/9dpqhmy1x9jcq3bfzjjsxssow2cfyfvy
> > >
> > > The Pekko Community vote:
> > >
> > > https://lists.apache.org/thread/kz51dmo0jc2lo4gbwo63h9hgxrpqn6jr
> > >
> > > The release candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/pekko/1.0.1-RC1/
> > >
> > > This release has been signed with a PGP key available here:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS
> > >
> > > Release Notes:
> > >
> > >
> > https://cwiki.apache.org/confluence/display/PEKKO/Pekko+Core+Release+Notes
> > >
> > > Git branch for the release:
> > >
> > > https://github.com/apache/incubator-pekko/tree/v1.0.1-RC1
> > > Git commit ID: a3f48833c97501a0193f4135f99c5f6ea04a03dd
> > >
> > > Please download, verify, and test.
> > >
> > > We have also staged jars in the Apache Nexus Repository. These were
> > > built with the same code
> > > as appears in this Source Release Candidate. We would appreciate if
> > > users could test with these too.
> > > If anyone finds any serious problems with these jars, please also
> > > notify us on this thread.
> > >
> > > https://repository.apache.org/content/groups/staging/org/apache/pekko/
> > >
> > > In sbt, you can add this resolver.
> > >
> > > resolvers += "Apache Pekko Staging" at
> > > "https://repository.apache.org/content/groups/staging";
> > >
> > >
> > > The VOTE will remain open for 72 hours or until we have enough binding
> > > approvals.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > To learn more about Apache Pekko, please see https://pekko.apache.org/
> > >
> > > Checklist for reference:
> > >
> > > [ ] Download links are valid.
> > > [ ] Checksums and signatures.
> > > [ ] LICENSE/NOTICE files exist
> > > [ ] No unexpected binary files
> > > [ ] Can compile from source
> > >
> > > To compile from the source, please refer to:
> > >
> > >
> > >
> > https://github.com/apache/incubator-pekko/blob/main/README.md#building-from-source
> > >
> > > Some notes about verifying downloads can be found at:
> > >
> > > https://pekko.apache.org/download.html#verifying-downloads
> > >
> > >
> > > Here is my +1 (binding).
> > >
> > > Thanks,
> > >
> > > PJ Fanning (Apache Pekko PPMC member and Incubator PMC member)
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> > --
> >
> > Matthew de Detrich
> >
> > *Aiven Deutschland GmbH*
> >
> > Immanuelkirchstraße 26, 10405 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >
> > *m:* +491603708037
> >
> > *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> >

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [VOTE] Release Apache Pekko, incubating, 1.0.1-RC1

[PJ Fanning]

Hi everyone,

The vote passes with 3 binding +1s and no other votes.

Matthew de Detrich
Ryan Skraba
PJ Fanning

Vote thread:

https://lists.apache.org/thread/yxwll4hf47s5j941or2w0gsbsq08nm3j

It will take a few days to complete the release and announcements.

Thanks to everyone who reviewed the release artifacts.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Retire Apache Tuweni

[PJ Fanning]

+1

Best of luck with the non-ASF version of Tuweni.

On 2023/07/24 05:31:41 Antoine Toulme wrote:
> Hello all,
> Tuweni has been incubating since 2019-03-25.
> 
> Since 2022, activity has been low, and the chances of attracting new
> committers and building a vibrant community seem very slim at this
> point.
> 
> The community discussion and vote can be found here[1],[2].
> 
> I therefore propose to retire Tuweni from the Incubator.
> 
> Voting will start now and will remain open for at least 72 hours.
> 
> Cheers,
> 
> Antoine
> 
> [1]: https://lists.apache.org/thread/t243vk87lxyz07o19fg87ffj2lsodnok
> [2]: https://lists.apache.org/thread/gnxsl6rs698p2jy16djf1coo1pt0k3wd
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Little "upside" at the Wayang podling

[PJ Fanning]

It does seem like a good idea to do a 2 phase release to the Apache Nexus 
Repository. I think a lot of Apache projects use that approach. It means that 
the binary artifacts can be checked during the release voting along side the 
source release. Nexus allows you the drop the artifacts or to release them and 
this can be a good way to handle unsuccessful and successful release votes 
(respectively).

It might make sense to bring the 0.7.0 release to an Incubator vote and if it 
passes then there isn't much harm. The Wayang team have announced this release 
on their dev mailing list but don't appear to have updated their download page 
[1] yet. Could we get them to respond to all the announcement emails to say 
that release vote is not yet complete and to ask people not use this release 
until the vote is finished?

If the Incubator vote fails, I'm not sure but it may be feasible to see if the 
Maven team can remove the 0.7.0 artifacts.

[1] https://wayang.apache.org/download/

On 2023/07/25 09:28:00 Christofer Dutz wrote:
> Hi all,
> 
> yesterday the Wayang podling was following the “release documentation” of a 
> TLP and “forgot” to do the round over the IPMC.
> However, they’ve already moved things to the release distro area (from where 
> they’ve removed it after me contacting them) but in Nexus they clicked on 
> “release” and the artifacts are out in the wild.
> 
> How to generally deal with this situation? I think in general it would be 
> good, if releasing maven artifacts in Nexus was a two step thing … a) the 
> project clicks on “release” and then an IPMC member has to confirm that.
> 
> Chris
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Little "upside" at the Wayang podling

[PJ Fanning]

The difference here is that this release has just been made and has
only been announced on the Wayang dev list. I find no evidence of it
on the Wayang web site nor in the Apache announce mailing list.

I understand the leftpad case but I don't think this is a similar
case. Users who have upgraded to Wayang 0.7.0 can downgrade to Wayang
0.6.0.

On Tue, 25 Jul 2023 at 13:19, tison  wrote:
>
> >So I guess we have to check how we can remove the artifacts.
>
> A central repository should not _remove_ artifacts. Rust's cargo crate can
> mark as yanked and prevent further dependent but remain all the existing
> one. Revoke artifacts can cause significant downstream effect - you may
> take leftpad on npmjs as an example.
>
> Best,
> tison.
>
>
> Christofer Dutz  于2023年7月25日周二 19:14写道：
>
> > Hi PJ,
> >
> > Unfortunately, I had to vote -1 on the release and there’s no way on earth
> > it would pass Justin ;-) …
> > So, there will be another one.
> >
> > So I guess we have to check how we can remove the artifacts.
> >
> > Chris
> >
> >
> > Von: PJ Fanning 
> > Datum: Dienstag, 25. Juli 2023 um 11:47
> > An: general@incubator.apache.org 
> > Betreff: Re: Little "upside" at the Wayang podling
> > It does seem like a good idea to do a 2 phase release to the Apache Nexus
> > Repository. I think a lot of Apache projects use that approach. It means
> > that the binary artifacts can be checked during the release voting along
> > side the source release. Nexus allows you the drop the artifacts or to
> > release them and this can be a good way to handle unsuccessful and
> > successful release votes (respectively).
> >
> > It might make sense to bring the 0.7.0 release to an Incubator vote and if
> > it passes then there isn't much harm. The Wayang team have announced this
> > release on their dev mailing list but don't appear to have updated their
> > download page [1] yet. Could we get them to respond to all the announcement
> > emails to say that release vote is not yet complete and to ask people not
> > use this release until the vote is finished?
> >
> > If the Incubator vote fails, I'm not sure but it may be feasible to see if
> > the Maven team can remove the 0.7.0 artifacts.
> >
> > [1] https://wayang.apache.org/download/
> >
> > On 2023/07/25 09:28:00 Christofer Dutz wrote:
> > > Hi all,
> > >
> > > yesterday the Wayang podling was following the “release documentation”
> > of a TLP and “forgot” to do the round over the IPMC.
> > > However, they’ve already moved things to the release distro area (from
> > where they’ve removed it after me contacting them) but in Nexus they
> > clicked on “release” and the artifacts are out in the wild.
> > >
> > > How to generally deal with this situation? I think in general it would
> > be good, if releasing maven artifacts in Nexus was a two step thing … a)
> > the project clicks on “release” and then an IPMC member has to confirm that.
> > >
> > > Chris
> > >
> > >
> >
> > -
> > 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

[RESULT] [VOTE] IP Clearance of Pekko HTTP CORS code donation

[PJ Fanning]

The vote passes by lazy consensus.

https://lists.apache.org/thread/m7vm57jwk9r4o2knmgmtfk19dd8wrsbs

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache Pekko (Incubating) 1.0.1 available

[PJ Fanning]

Hi everyone,

The Apache Pekko (Incubating) Team is happy to announce the release of
Apache Pekko (Incubating) 1.0.1.

Apache Pekko (Incubating) is an open source toolkit and runtime
simplifying the construction of concurrent and distributed
applications on the JVM. It is a fork of Akka and has come about
because Akka has moved from being Apache licensed to being licensed
under a Business Software License.

This release covers the core modules. Other modules like Pekko HTTP
will be released separately (and hopefully soon).

Download Links:
https://pekko.apache.org/download.html#pekko-core

Release Notes:
https://pekko.apache.org/docs/pekko/1.0/release-notes/index.html#1-0-1

Website:
https://pekko.apache.org/

Issues:
https://github.com/apache/incubator-pekko/issues

Mailing list: d...@pekko.apache.org

Jars are published to Maven Central using the groupId: org.apache.pekko

Thanks to everyone who participated in the development and release.

Apache Pekko (Incubating) Team

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: When can an IP clearance start?

[PJ Fanning]

The IP Clearance process is described here.

https://incubator.apache.org/ip-clearance/

My understanding is that you can take your time with completing this.
Get the software grant agreements registered with the ASF Secretary
and get as many contributors as possible to sign ASF iCLAs.

Presumably, you're going to have to go through the code and replace
the license headers - probably with the standard Apache one.

https://www.apache.org/legal/src-headers.html

You should check for code that originates from outside the KIE team.
That will have to be mentioned in your project license and possibly
also the notice (depending on how that 3rd party code is licensed).
These sources can include other projects but also places like
Stackoverflow or examples in standalone projects. You may find that
some 3rd party code may have a license that is not compatible with the
Apache license.

You can probably complete the IP Clearance just before you intend your
first Apache release(s) or you may even be able to delay it if you
need to expedite a release.

When you are doing releases, the Incubator PMC requires a 2 phase
release. The PPMC approves the release candidate and then the
Incubator PMC. Part of the release vote is to have people check the
licensing etc of the source files in the release.

I'm sure other Incubator PMC members can correct any mistakes in this
email but hopefully, it's a reasonable summary.

On Thu, 27 Jul 2023 at 19:31, Jason Porter  wrote:
>
> We’re currently working through some issues with a software grant, but there 
> is a light at the end of the tunnel. Do we need to wait for the software 
> grant to finalize before starting an IP clearance? If not, that’s available 
> self-serve somewhere, correct?
>
> --
> Jason Porter
> Software Engineer
> He/Him/His
>
> IBM
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Pekko(incubating) HTTP 1.0.0-RC2

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating) HTTP
version 1.0.0-RC2.

The discussion thread:

https://lists.apache.org/thread/ogfbr3g2otd35gjct06bj2ll5lbh8bzd

The Pekko Result:

https://lists.apache.org/thread/s25zj36m74pwr6ty97p0cpk8nxny06s7

The Pekko Vote Thread:

https://lists.apache.org/thread/t1lqqps1lj9tds7n8cxl3h9k67ovr8wy

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/HTTP-1.0.0-RC2/

This release has been signed with a PGP key available here:

https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS

Release Notes:

https://pekko.apache.org/docs/pekko-http/current/release-notes/index.html

Git branch for the release:

https://github.com/apache/incubator-pekko-http/tree/v1.0.0-RC2
Git commit ID: 37f35d6bccd9913c6dd108004581a9abcb91343e

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code
as appears in this Source Release Candidate. We would appreciate if
users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging";


The vote will be left open for at least 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] Source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko-http/blob/main/README.md#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

Thanks,

PJ Fanning (Apache Incubator PMC member and Pekko PPMC member)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pekko(incubating) HTTP 1.0.0-RC2

[PJ Fanning]

Thanks Justin for the info.

Matthew de Detrich has also voted on the Pekko PPMC thread, so that
makes 3 +1 (binding) votes so far.

On Sat, 29 Jul 2023 at 14:30, Justin Mclean  wrote:
>
> Hi,
>
> I've already voted +1 on the project's mailing list.
>
> If any IPMC members vote +1 on the previous vote it best to note that in the 
> vote email.
>
> Kind Regards,
> Justin
> -
> 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] Release Apache Pekko(incubating) CONNECTORS-KAFKA 1.0.0-RC1

[PJ Fanning]

I think this vote was started too early because we only have 2 PPMC
votes on the original Pekko vote thread. We'll see if we can get more
PPMC votes.

Justin McLean and I both voted on the PPMC vote so that means we have
3 +1 binding votes so far.

On Sat, 29 Jul 2023 at 15:37, Matthew de Detrich
 wrote:
>
> Hello Incubator Community,
>
> This is a call for a vote to release Apache Pekko(incubating)
> CONNECTORS-KAFKA
> version 1.0.0-RC1.
>
> The discussion thread:
>
> https://lists.apache.org/thread/4mqb0x8gvjoffr14kcfn9h8fy71srk6f
>
> The Pekko Result:
>
> https://lists.apache.org/thread/tfo10wdn4bvk9myxjxqxlw7fmob72sch
>
> The Pekko Vote Thread:
>
> https://lists.apache.org/thread/tfo10wdn4bvk9myxjxqxlw7fmob72sch
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/pekko/CONNECTORS-KAFKA-1.0.0-RC1/
>
> This release has been signed with a PGP key available here:
>
> https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS
>
> Release Notes:
>
> https://pekko.apache.org/docs/pekko-connectors-kafka/current/release-notes/index.html
>
> Git branch for the release:
>
> https://github.com/apache/incubator-pekko-connectors-kafka/tree/v1.0.0-RC1
> Git commit ID: 0245d7a3e8dee648308bb49831ff96415851cc46
>
> Please download, verify, and test.
>
> We have also staged jars in the Apache Nexus Repository. These were
> built with the same code
> as appears in this Source Release Candidate. We would appreciate if
> users could test with these too.
> If anyone finds any serious problems with these jars, please also
> notify us on this thread.
>
> https://repository.apache.org/content/groups/staging/org/apache/pekko/
>
> In sbt, you can add this resolver.
>
> resolvers += "Apache Pekko Staging" at
> "https://repository.apache.org/content/groups/staging";
>
>
> The vote will be left open for at least 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about Apache Pekko, please see https://pekko.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] Source files have ASF headers
> [ ] Can compile from source
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-pekko-connectors-kafka/blob/main/README.md#building-from-source
>
> Some notes about verifying downloads can be found at:
>
> https://pekko.apache.org/download.html#verifying-downloads
>
>
> Here is my +1 (binding).
>
> Thanks,
>
> --
>
> Matthew de Detrich
>
> *Aiven Deutschland GmbH*
>
> Immanuelkirchstraße 26, 10405 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> *m:* +491603708037
>
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Livy 0.8.0-incubating (RC1)

[PJ Fanning]

I had a look at your binary zip. There is a problem with the
thirdparty license. I raised this.

https://issues.apache.org/jira/browse/LIVY-981

There are GPL and LGPL licensed jars in the zip. I'm not sure but I
thought we couldn't include jars with category X licenses in our
binary distributions.
It could be that Category X licenses are only a problem with Source Releases.

https://www.apache.org/legal/resolved.html#category-x

Some of the jars are dual licensed. We could choose to use the more
permissive licenses in these cases.


  GNU General Public Library:

* Streaming API for XML (javax.xml.stream:stax-api:1.0-2 - no url defined)

  GNU Lesser General Public License (LGPL), Version 2.1:

* JAX-RS provider for JSON content type
(org.codehaus.jackson:jackson-jaxrs:1.8.3 -
http://jackson.codehaus.org)
* Xml Compatibility extensions for Jackson
(org.codehaus.jackson:jackson-xc:1.8.3 - http://jackson.codehaus.org)

  GPL:

* JTransforms (com.github.rwl:jtransforms:2.4.0 -
http://sourceforge.net/projects/jtransforms/)

  GPL2 w/ CPE:

* JAXB API bundle for GlassFish V3 (javax.xml.bind:jaxb-api:2.2.2
- https://jaxb.dev.java.net/)
* JAXB RI (com.sun.xml.bind:jaxb-impl:2.2.3-1 - http://jaxb.java.net/)
* javax.ws.rs-api (javax.ws.rs:javax.ws.rs-api:2.0.1 -
http://jax-rs-spec.java.net)
* jersey-client (com.sun.jersey:jersey-client:1.9 -
https://jersey.java.net/jersey-client/)
* jersey-core (com.sun.jersey:jersey-core:1.9 -
https://jersey.java.net/jersey-core/)
* jersey-guice (com.sun.jersey.contribs:jersey-guice:1.9 -
https://jersey.java.net/jersey-contribs/jersey-guice/)
* jersey-json (com.sun.jersey:jersey-json:1.9 -
https://jersey.java.net/jersey-json/)
* jersey-server (com.sun.jersey:jersey-server:1.9 -
https://jersey.java.net/jersey-server/)

  LGPL:

* JTransforms (com.github.rwl:jtransforms:2.4.0 -
http://sourceforge.net/projects/jtransforms/)

  LGPL 2.1:

* Javassist (org.javassist:javassist:3.18.1-GA - http://www.javassist.org/)


On Mon, 31 Jul 2023 at 18:25, Damon Cortesi  wrote:
>
> Hello Incubator Community,
>
> The Apache Livy has recently been working on reviving the Livy project
> and would like to call for a vote to release Apache Livy(Incubating)
> version 0.8.0-incubating-rc1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
> • https://lists.apache.org/thread/ypv03984tmqhq6lnlt50msdx9g9ykkwm
>
> Vote result thread:
> • https://lists.apache.org/thread/842ytoz8mgkoo0qbzlnmfkhwtn0chjnc
>
> The release candidate:
> • https://dist.apache.org/repos/dist/dev/incubator/livy/0.8.0-incubating-rc1
>
> Git tag for the release:
> • https://github.com/apache/incubator-livy/releases/tag/v0.8.0-incubating-rc1
>
>
> Public keys file:
> • https://dist.apache.org/repos/dist/dev/incubator/livy/KEYS
>
> The change log is available in:
> • 
> https://github.com/apache/incubator-livy/compare/v0.7.1-incubating-rc1...v0.8.0-incubating-rc1
>
> Dev instructions:
> • https://github.com/apache/incubator-livy/tree/master/dev/docker
>
> 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,
> Damon Cortesi
>
> -
> 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] Release Apache Livy 0.8.0-incubating (RC1)

[PJ Fanning]

I've had a closer look and it looks like THIRD-PARTY file is including
license info for jars that you don't even ship.

It seems that you actually have no problematic jars except perhaps
that ldapsdk jar. This issue is worth reading.

https://issues.apache.org/jira/browse/LEGAL-160

I've raised this issue about your THIRD-PARTY file.

https://issues.apache.org/jira/browse/LIVY-982

The format of that THIRD-PARTY file makes it very hard to use.

On Mon, 31 Jul 2023 at 19:35, Damon Cortesi  wrote:
>
> Thank you for the detailed report, will take a look!
>
> On 2023/07/31 18:10:21 PJ Fanning wrote:
> > I had a look at your binary zip. There is a problem with the
> > thirdparty license. I raised this.
> >
> > https://issues.apache.org/jira/browse/LIVY-981
> >
> > There are GPL and LGPL licensed jars in the zip. I'm not sure but I
> > thought we couldn't include jars with category X licenses in our
> > binary distributions.
> > It could be that Category X licenses are only a problem with Source 
> > Releases.
> >
> > https://www.apache.org/legal/resolved.html#category-x
> >
> > Some of the jars are dual licensed. We could choose to use the more
> > permissive licenses in these cases.
> >
> >
> >   GNU General Public Library:
> >
> > * Streaming API for XML (javax.xml.stream:stax-api:1.0-2 - no url 
> > defined)
> >
> >   GNU Lesser General Public License (LGPL), Version 2.1:
> >
> > * JAX-RS provider for JSON content type
> > (org.codehaus.jackson:jackson-jaxrs:1.8.3 -
> > http://jackson.codehaus.org)
> > * Xml Compatibility extensions for Jackson
> > (org.codehaus.jackson:jackson-xc:1.8.3 - http://jackson.codehaus.org)
> >
> >   GPL:
> >
> > * JTransforms (com.github.rwl:jtransforms:2.4.0 -
> > http://sourceforge.net/projects/jtransforms/)
> >
> >   GPL2 w/ CPE:
> >
> > * JAXB API bundle for GlassFish V3 (javax.xml.bind:jaxb-api:2.2.2
> > - https://jaxb.dev.java.net/)
> > * JAXB RI (com.sun.xml.bind:jaxb-impl:2.2.3-1 - http://jaxb.java.net/)
> > * javax.ws.rs-api (javax.ws.rs:javax.ws.rs-api:2.0.1 -
> > http://jax-rs-spec.java.net)
> > * jersey-client (com.sun.jersey:jersey-client:1.9 -
> > https://jersey.java.net/jersey-client/)
> > * jersey-core (com.sun.jersey:jersey-core:1.9 -
> > https://jersey.java.net/jersey-core/)
> > * jersey-guice (com.sun.jersey.contribs:jersey-guice:1.9 -
> > https://jersey.java.net/jersey-contribs/jersey-guice/)
> > * jersey-json (com.sun.jersey:jersey-json:1.9 -
> > https://jersey.java.net/jersey-json/)
> > * jersey-server (com.sun.jersey:jersey-server:1.9 -
> > https://jersey.java.net/jersey-server/)
> >
> >   LGPL:
> >
> > * JTransforms (com.github.rwl:jtransforms:2.4.0 -
> > http://sourceforge.net/projects/jtransforms/)
> >
> >   LGPL 2.1:
> >
> > * Javassist (org.javassist:javassist:3.18.1-GA - 
> > http://www.javassist.org/)
> >
> >
> > On Mon, 31 Jul 2023 at 18:25, Damon Cortesi  wrote:
> > >
> > > Hello Incubator Community,
> > >
> > > The Apache Livy has recently been working on reviving the Livy project
> > > and would like to call for a vote to release Apache Livy(Incubating)
> > > version 0.8.0-incubating-rc1.
> > >
> > > We now kindly request the Incubator PMC members review and vote on this
> > > incubator release.
> > >
> > > Community vote thread:
> > > • https://lists.apache.org/thread/ypv03984tmqhq6lnlt50msdx9g9ykkwm
> > >
> > > Vote result thread:
> > > • https://lists.apache.org/thread/842ytoz8mgkoo0qbzlnmfkhwtn0chjnc
> > >
> > > The release candidate:
> > > • 
> > > https://dist.apache.org/repos/dist/dev/incubator/livy/0.8.0-incubating-rc1
> > >
> > > Git tag for the release:
> > > • 
> > > https://github.com/apache/incubator-livy/releases/tag/v0.8.0-incubating-rc1
> > >
> > >
> > > Public keys file:
> > > • https://dist.apache.org/repos/dist/dev/incubator/livy/KEYS
> > >
> > > The change log is available in:
> > > • 
> > > https://github.com/apache/incubator-livy/compare/v0.7.1-incubating-rc1...v0.8.0-incubating-rc1
> > >
> > > Dev instructions:
> > > • https://github.com/apache/incubator-livy/tree/master/dev/docker
> > >
> > > The vote will be open for at least 72 hours or until the necessary number
> > > of votes are reached.
> > >
> > >

Re: [VOTE] Release Apache Livy 0.8.0-incubating (RC1)

[PJ Fanning]

+1 (binding)

The source release seems fine.
* incubating in name
* signing and checksums are ok
* LICENSE/NOTICE/DISCLAIMER are ok
* source files have ASL headers
* maven build works

The binary zips seem ok but it would be nice to do something with the
THIRD-PARTY file in future releases.

On Mon, 31 Jul 2023 at 19:51, PJ Fanning  wrote:
>
> I've had a closer look and it looks like THIRD-PARTY file is including
> license info for jars that you don't even ship.
>
> It seems that you actually have no problematic jars except perhaps
> that ldapsdk jar. This issue is worth reading.
>
> https://issues.apache.org/jira/browse/LEGAL-160
>
> I've raised this issue about your THIRD-PARTY file.
>
> https://issues.apache.org/jira/browse/LIVY-982
>
> The format of that THIRD-PARTY file makes it very hard to use.
>
> On Mon, 31 Jul 2023 at 19:35, Damon Cortesi  wrote:
> >
> > Thank you for the detailed report, will take a look!
> >
> > On 2023/07/31 18:10:21 PJ Fanning wrote:
> > > I had a look at your binary zip. There is a problem with the
> > > thirdparty license. I raised this.
> > >
> > > https://issues.apache.org/jira/browse/LIVY-981
> > >
> > > There are GPL and LGPL licensed jars in the zip. I'm not sure but I
> > > thought we couldn't include jars with category X licenses in our
> > > binary distributions.
> > > It could be that Category X licenses are only a problem with Source 
> > > Releases.
> > >
> > > https://www.apache.org/legal/resolved.html#category-x
> > >
> > > Some of the jars are dual licensed. We could choose to use the more
> > > permissive licenses in these cases.
> > >
> > >
> > >   GNU General Public Library:
> > >
> > > * Streaming API for XML (javax.xml.stream:stax-api:1.0-2 - no url 
> > > defined)
> > >
> > >   GNU Lesser General Public License (LGPL), Version 2.1:
> > >
> > > * JAX-RS provider for JSON content type
> > > (org.codehaus.jackson:jackson-jaxrs:1.8.3 -
> > > http://jackson.codehaus.org)
> > > * Xml Compatibility extensions for Jackson
> > > (org.codehaus.jackson:jackson-xc:1.8.3 - http://jackson.codehaus.org)
> > >
> > >   GPL:
> > >
> > > * JTransforms (com.github.rwl:jtransforms:2.4.0 -
> > > http://sourceforge.net/projects/jtransforms/)
> > >
> > >   GPL2 w/ CPE:
> > >
> > > * JAXB API bundle for GlassFish V3 (javax.xml.bind:jaxb-api:2.2.2
> > > - https://jaxb.dev.java.net/)
> > > * JAXB RI (com.sun.xml.bind:jaxb-impl:2.2.3-1 - http://jaxb.java.net/)
> > > * javax.ws.rs-api (javax.ws.rs:javax.ws.rs-api:2.0.1 -
> > > http://jax-rs-spec.java.net)
> > > * jersey-client (com.sun.jersey:jersey-client:1.9 -
> > > https://jersey.java.net/jersey-client/)
> > > * jersey-core (com.sun.jersey:jersey-core:1.9 -
> > > https://jersey.java.net/jersey-core/)
> > > * jersey-guice (com.sun.jersey.contribs:jersey-guice:1.9 -
> > > https://jersey.java.net/jersey-contribs/jersey-guice/)
> > > * jersey-json (com.sun.jersey:jersey-json:1.9 -
> > > https://jersey.java.net/jersey-json/)
> > > * jersey-server (com.sun.jersey:jersey-server:1.9 -
> > > https://jersey.java.net/jersey-server/)
> > >
> > >   LGPL:
> > >
> > > * JTransforms (com.github.rwl:jtransforms:2.4.0 -
> > > http://sourceforge.net/projects/jtransforms/)
> > >
> > >   LGPL 2.1:
> > >
> > > * Javassist (org.javassist:javassist:3.18.1-GA - 
> > > http://www.javassist.org/)
> > >
> > >
> > > On Mon, 31 Jul 2023 at 18:25, Damon Cortesi  wrote:
> > > >
> > > > Hello Incubator Community,
> > > >
> > > > The Apache Livy has recently been working on reviving the Livy project
> > > > and would like to call for a vote to release Apache Livy(Incubating)
> > > > version 0.8.0-incubating-rc1.
> > > >
> > > > We now kindly request the Incubator PMC members review and vote on this
> > > > incubator release.
> > > >
> > > > Community vote thread:
> > > > • https://lists.apache.org/thread/ypv03984tmqhq6lnlt50msdx9g9ykkwm
> > > >
> > > > Vote result thread:
> > > > • https://lists.apache.org/thread/842ytoz8mgkoo0qbzlnmfkhwtn0chjnc
> > > >
> > > > The release candidate:
> > > > • 
> >

[RESULT] [VOTE] Release Apache Pekko(incubating) HTTP 1.0.0-RC2

[PJ Fanning]

The vote passes with 3 binding +1s.

Vote Thread:

https://lists.apache.org/thread/33bqomsl277ttr7k2mrc9twn4m6h2g86

Votes
Justin McLean
Matthew de Detrich
PJ Fanning

The release will be finalised and announced over the coming days.

Thanks to everyone who reviewed the RC.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSSION] The retirement of the Apache DataLab (Moving to Apache Attic)

[PJ Fanning]

It appears the DataLab community has voted to retire the project.

https://lists.apache.org/thread/v238c8hnwn1sn58v7xglo6dk4phcw5v3

If that is what they want then I support moving DataLab to the Attic.

On Wed, 2 Aug 2023 at 09:28, Ruslan Kulynych  wrote:
>
> Hi all,
>
> The DataLab project has been in the incubator for too long, as a result many 
> developers have moved on to other projects,
> which has caused the project to slow down significantly, especially in the 
> last seven months.
> So I'd like to start a discussion about the project retirement and moving it 
> to the Apache Attic.
>
> The discussion will remain open for at least a week.
>
> Please share your thoughts.
>
> Best regards,
> Ruslan Kulynych
>
> -
> 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

[ANNOUNCE] Apache Pekko (Incubating) HTTP 1.0.0 available

[PJ Fanning]

Hi everyone,

The Apache Pekko (Incubating) Team is happy to announce the release of
Apache Pekko (Incubating) HTTP 1.0.0.

Apache Pekko (Incubating) is an open source toolkit and runtime
simplifying the construction of concurrent and distributed
applications on the JVM. It is a fork of Akka and has come about
because Akka has moved from being Apache licensed to being licensed
under a Business Software License.

Download Links:
https://pekko.apache.org/download.html#pekko-http

Release Notes:
https://pekko.apache.org/docs/pekko-http/1.0.0/release-notes/index.html#1-0-0

Website:
https://pekko.apache.org/

Issues:
https://github.com/apache/incubator-pekko-http/issues

Mailing list: d...@pekko.apache.org

Jars are published to Maven Central using the groupId: org.apache.pekko

Thanks to everyone who participated in the development and release.

Apache Pekko (Incubating) Team

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Apache infrastructure for CI?

[PJ Fanning]

In practice, a lot of teams now use GitHub Actions. There are secrets
set up on it for publishing to our Apache Nexus instance
(repository.apache.org) - at the Apache organization level.

There is a Jenkins instance maintained by the Apache Infrastructure team.

https://ci-builds.apache.org/

The Infra team have contact details here:

https://infra.apache.org/

Or use JIRA:

https://issues.apache.org/jira/projects/INFRA/

On Wed, 2 Aug 2023 at 15:43, Alex Porcelli  wrote:
>
> Is there an infrastructure in Apache for CI (Jenkins, etc) for its projects?
>
> If yes, where can we find more information on how to onboard?
>
> If not, how do projects deal with CI infrastructure?
>
> Regards,
> Alex Porcelli
> KIE Podling
>
> -
> 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: New Mentor Question: IP Clearance

[PJ Fanning]

There is a recent thread with some details but maybe someone can provide more.

https://lists.apache.org/thread/h11mkl9yd9584dnqv8qoyg8r6ftg2qp1

On Wed, 2 Aug 2023 at 19:32, Brian Proffitt  wrote:
>
> As a Champion/Mentor for KIE, I need to start the IP clearance process, and
> the workflow described in the IP Clearance page[1] clearly states:
>
> "This form is not for new projects.
> This is for projects and PMCs that have already been created and are
> receiving a code donation into an existing codebase. Any code that was
> developed outside of the ASF SVN repository and our public mailing lists
> must be processed like this, even if the external developer is already an
> ASF committer.
>
> "Incubating projects should follow the procedure described in the incubator
> mentor guide and report status via STATUS tracking."
>
> Okay, cool, so I follow the link to the incubator mentor guide[2] and
> there's only a self-referencing anchor link about "Start IP clearance"
>
> The question: what is the procedure I need to follow?
>
> Thanks!
> BKP
>
> [1] https://incubator.apache.org/ip-clearance/index.html
> [2] https://incubator.apache.org/guides/mentor.html
>
>
>
> Brian Proffitt
> VP, Marketing & Publicity

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache Pekko(incubating) Management 1.0.0-RC2

[PJ Fanning]

Hello Incubator Community,

This is a call for a vote to release Apache Pekko(incubating)
Management version 1.0.0-RC2.

The discussion thread:

https://lists.apache.org/thread/g1hhcsvzbd8o1zdholds41k0jrknrx3q

The Pekko Vote result:

https://lists.apache.org/thread/qyxjkpwyok42hzvkvhor2pc6bkkpmhwz

The Pekko Vote thread:

https://lists.apache.org/thread/d2b6h8zffms05m725v21v08c4m4gjq4j

The release candidate:

https://dist.apache.org/repos/dist/dev/incubator/pekko/MANAGEMENT-1.0.0-RC2/

This release has been signed with a PGP key available here:

https://dist.apache.org/repos/dist/dev/incubator/pekko/KEYS

Release Notes:

https://pekko.apache.org/docs/pekko-management/current/release-notes/index.html

Git branch for the release:

https://github.com/apache/incubator-pekko-management/tree/v1.0.0-RC2
Git commit ID: c1bab5a116b7f4c654f9d7ae3886a344e0f3771e

Please download, verify, and test.

We have also staged jars in the Apache Nexus Repository. These were
built with the same code as appears in this Source Release Candidate.
We would appreciate if users could test with these too.
If anyone finds any serious problems with these jars, please also
notify us on this thread.

https://repository.apache.org/content/groups/staging/org/apache/pekko/

In sbt, you can add this resolver.

resolvers += "Apache Pekko Staging" at
"https://repository.apache.org/content/groups/staging";


The Vote will be left open for at least 72 hours.

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

To learn more about Apache Pekko, please see https://pekko.apache.org/

Checklist for reference:

[ ] Download links are valid.
[ ] Checksums and signatures.
[ ] LICENSE/NOTICE files exist
[ ] No unexpected binary files
[ ] Source files have ASF headers
[ ] Can compile from source

To compile from the source, please refer to:

https://github.com/apache/incubator-pekko-management/blob/main/README.md#building-from-source

Some notes about verifying downloads can be found at:

https://pekko.apache.org/download.html#verifying-downloads


Here is my +1 (binding).

2 other +1 (binding) votes were also registered on the Pekko vote thread.

Justin McLean
Matthew de Detrich


Thanks,

PJ Fanning (Apache Incubator PMC member)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Retirement of the Apache DataLab

[PJ Fanning]

+1 (binding)

On Wed, 9 Aug 2023 at 10:28, Ruslan Kulynych  wrote:
>
> Hi all,
>
> Based on discussion[1], I would like to call for a vote to retire the Apache 
> DataLab.
>
> The voting will last for at least one week to ensure that everyone has time 
> to express their opinions.
>
> Please vote accordingly:
>
> [] +1 Approve
> [] +0 No opinion
> [] -1 Disapprove with a reason
>
> [1]: https://lists.apache.org/thread/k3zsksrkd5k0147pxzqndrhgsg2o6x6j
>
> Thank you all for your participation.
>
> Best regards,
> Ruslan Kulynych
>
> -
> 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: Looking for a Champion (and mentors) for the Hexagon Toolkit

[PJ Fanning]

Hi Juan José,

Your project looks like you've put a lot of time and effort into it.
It certainly looks like a good candidate.

My one concern is that Apache Incubator projects require votes about
procedural items like doing releases so that means you need to have a
few community members to start with. It is an important goal of any
incubating project to grow the community over time but the ASF rules
require that you have to start with a few active members.

Do you have a few Hexagon contributors who would be interested in
acting as PPMC [1] members of a potential Apache Incubator project?

It can be quite a time consuming process to bring code into an Apache
Incubator project and to modify all the code and documentation to
apply the correct licensing and branding.

Regards,
PJ

[1] https://incubator.apache.org/guides/ppmc.html

On Wed, 9 Aug 2023 at 22:56, Juan José Aguililla
 wrote:
>
> Hello Apache Members,
>
> I would love to move the Hexagon Toolkit development to the ASF. To
> briefly describe the project: Hexagon is a microservices toolkit
> written in Kotlin. Its purpose is to ease the building of server
> applications (Web applications or REST APIs).
>
> The project's goals are:
> * Provide a programmatic way to handle HTTP requests. With a similar
> developer experience as Javalin: https://javalin.io or Express:
> https://expressjs.com
> * Provide a tool backed by an OSS foundation instead of a company
> * Modular architecture
>   * Each functionality has its own "Port"
>   * Ports are implemented by adapters. They can be switched without
> changing application code
>   * Modules are layered (i.e.: REST > HTTP Server) not carrying unused
> functionalities (and their dependencies)
>   * Orthogonal ports: Ports can be used by other Ports or standalone
> as opposed to duplicating code (i.e.: JSON on HTTP clients and
> servers)
> * No code generation (on the core). It can be added later to generate
> code, but not relying on code generation to create applications
> * Bare minimum dependencies. Ideally, only a third party dependency by adapter
> * Native Image: client applications can generate native images easily
> (the toolkit tests are passed natively on Windows, macOS and Linux)
> * No reflection. This makes easier to reason about programs, and eases
> the native image generation
> * Developed in Kotlin and meant to be used with Kotlin, but I'm
> considering porting it to Java
>
> The reasons to enter the Apache Incubator are:
> * First, to get feedback to decide if it is worthy to keep the project
> open, and know which changes would be needed to make it appealing to
> developers.
> * Second, to create a community around to take the toolkit further
> * And lastly, to get a broader reach for developers to use it for
> their applications
>
> These are some relevant links:
> * https://hexagonkt.com
> * https://github.com/hexagonkt
> * https://twitter.com/hexagon_kt
>
> Thank you very much for your time! I keep waiting for news from your side.
>
>
> Cheers,
> Juanjo
>
> -
> 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