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 licens
nity 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 wro
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,
> > >
&
estions 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
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
inclu
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.
en 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 W
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
l
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 licen
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/2
+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 vo
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 s
+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,
>
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 proj
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
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 tr
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
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, whic
ks 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 pr
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 ma
ly 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
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 req
+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
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 n
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
> 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, 2
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 us
licy.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
&g
ps://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 art
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 fr
+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 (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 EventMe
+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 discu
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
+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 in
+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 an
+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
+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, li
+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.
>
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 contribu
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'v
+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
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.
So
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
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.
S
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,
> >
>
/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
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
+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
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://gi
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
rvice 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 abou
://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
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
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 com
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 loo
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
ur 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/incubato
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
t; >> 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 necessa
esolved 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 co
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 P
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 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:
>
> > H
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
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
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/8e30c341f1f8351a19b715992
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
f
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 com
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,
:
>
> 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 t
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,
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
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 thi
+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
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)
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/yc67o21wg3sj2h364gdpd9j1trofhgn
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 contr
kko!
>
> 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 P
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
+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 th
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 relea
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
> >
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
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 com
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,
pile 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 Incu
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 v
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
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.
'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 202
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
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
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 be
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 ha
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 I
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 descri
inding).
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.apach
+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 a
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 wi
1 - 100 of 404 matches
Mail list logo
