You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pekko.apache.org by Matthew Benedict de Detrich <ma...@aiven.io.INVALID> on 2023/06/01 08:47:34 UTC
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
If they are happy to donate the code is the code grant necessary?
On Thu, 1 June 2023, 00:36 Justin Mclean, <ju...@classsoftware.com> wrote:
> Hi,
>
> If they (and the community/committers behind it) want to donate it to the
> ASF then that’s fine, but it’s also OK if it remains a 3rd party as it
> licensed under the ALv2. I’m not seeing any issues here.
>
> Kind Regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by PJ Fanning <fa...@apache.org>.
We have the Software Grant and I've created an IP Clearance file:
https://incubator.apache.org/ip-clearance/pekko-connectors-aws-spi.html
If anyone has any changes to suggest or objections, please respond on this thread.
I will open a vote on the Apache Incubator mailing list in a few days. IP Clearance still needs Incubator approval - this applies to TLPs and podlings.
On 2024/02/05 09:51:55 PJ Fanning wrote:
> I created https://github.com/matsluni/aws-spi-akka-http/discussions/238 to see if Matthias Lüneberg is willing to grant the code to us.
>
>
> On 2024/02/05 08:50:07 Arnout Engelen wrote:
> > On Mon, Feb 5, 2024 at 1:52 AM Matthew de Detrich
> > <ma...@aiven.io.invalid> wrote:
> >
> > > So now that Pekko Connectors is at 1.1.x I think it's time to revive the
> > > discussion for integrating aws-spi-pekko-http within Pekko Connectors
> > > itself.
> > >
> >
> > In general, I think it shouldn't be a goal to include 'everything' into
> > Pekko Connectors - having an active ecosystem of connectors outside of
> > Apache Pekko itself would be a sign of health, and we should only have
> > connectors in the projects that we're prepared to maintain long-term. Also,
> > now that the first Pekko releases are out, the 'bootstrapping' problems
> > might be less urgent because of compatibility.
> >
> > That said...
> >
> >
> > > it makes sense to include aws-spi-pekko-http[1] within
> > > pekko itself because its critical dependency to build many projects within
> > > pekko connectors (AwsLambda, DynamoDb, EventBridge, Kinesis, Sns, Sqs) and
> > > it also has no real use outside of pekko-connectors considering its an SPI
> > > between AWS SDK and akka/pekko http
> >
> >
> > This seems like a strong reason to indeed pull the functionality provided
> > by aws-spi-pekko-http into Pekko Connectors.
> >
> >
> > Kind regards,
> >
> > Arnout
> >
> > , i.e. same deal with akka-http-cors
> > > (which is now official part of Pekko Http). Given critical time constraints
> > > at the time it made sense to fork aws-spi-akka-http into aws-spi-pekko-http
> > > but seeing as we are now working on Pekko Connectors 1.1.x now is the
> > > perfect opportunity to revisit this.
> > >
> > > Another thing to note is that due to
> > > https://github.com/pjfanning/aws-spi-pekko-http not being contained within
> > > Pekko Connectors we had to duplicate code that exposes implementation
> > > details[2] which would ordinarily not be required if contained within the
> > > pekko-connectors repository.
> > >
> > > Some of the obvious questions apply i.e. shall we do this officially like
> > > we did with akka-http-cors i.e. create an SGA and reach out to the official
> > > author? Another thing to note is that the project itself is not that big,
> > > i.e. the entire implementation is 3 files[3] with the largest one being
> > > ~200 lines long and the sources appear to be predominantly written by a
> > > single author so if we go ahead with an SGA, if accepted by the author the
> > > licensing/code origin should be quite trivial.
> > >
> > > 1: https://github.com/pjfanning/aws-spi-pekko-http
> > > 2:
> > >
> > > https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-2.12/com/github/pjfanning/pekkohttpspi
> > > ,
> > >
> > > https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-2.13/com/github/pjfanning/pekkohttpspi
> > > and
> > >
> > > https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-3/com/github/pjfanning/pekkohttpspi
> > > 3:
> > >
> > > https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala/com/github/pjfanning/pekkohttpspi
> > >
> > > On Sun, Jun 25, 2023 at 7:06 PM Justin Mclean <ju...@classsoftware.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > Regarding ICLAs for software grants, it may depend on how the software is
> > > > licensed. It is nice to have an ICLA for every major contributor, and if
> > > > the software was under an OS license, then it is needed. However, in this
> > > > case, it’s under ALv2, so ICLAs are just nice to have but not required.
> > > >
> > > > Kind Regards,
> > > > Justin
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > > For additional commands, e-mail: dev-help@pekko.apache.org
> > > >
> > > >
> > >
> > > --
> > >
> > > Matthew de Detrich
> > >
> > > *Aiven Deutschland GmbH*
> > >
> > > Immanuelkirchstraße 26, 10405 Berlin
> > >
> > > Alexanderufer 3-7, 10117 Berlin
> > >
> > > Amtsgericht Charlottenburg, HRB 209739 B
> > >
> > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > >
> > > *m:* +491603708037
> > >
> > > *w:* aiven.io *e:* matthew.dedetrich@aiven.io
> > >
> >
> >
> > --
> > Arnout Engelen
> > ASF Security Response
> > Committer on Apache Pekko
> > Committer on NixOS
> > Independent Open Source consultant
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by PJ Fanning <fa...@apache.org>.
I created https://github.com/matsluni/aws-spi-akka-http/discussions/238 to see if Matthias Lüneberg is willing to grant the code to us.
On 2024/02/05 08:50:07 Arnout Engelen wrote:
> On Mon, Feb 5, 2024 at 1:52 AM Matthew de Detrich
> <ma...@aiven.io.invalid> wrote:
>
> > So now that Pekko Connectors is at 1.1.x I think it's time to revive the
> > discussion for integrating aws-spi-pekko-http within Pekko Connectors
> > itself.
> >
>
> In general, I think it shouldn't be a goal to include 'everything' into
> Pekko Connectors - having an active ecosystem of connectors outside of
> Apache Pekko itself would be a sign of health, and we should only have
> connectors in the projects that we're prepared to maintain long-term. Also,
> now that the first Pekko releases are out, the 'bootstrapping' problems
> might be less urgent because of compatibility.
>
> That said...
>
>
> > it makes sense to include aws-spi-pekko-http[1] within
> > pekko itself because its critical dependency to build many projects within
> > pekko connectors (AwsLambda, DynamoDb, EventBridge, Kinesis, Sns, Sqs) and
> > it also has no real use outside of pekko-connectors considering its an SPI
> > between AWS SDK and akka/pekko http
>
>
> This seems like a strong reason to indeed pull the functionality provided
> by aws-spi-pekko-http into Pekko Connectors.
>
>
> Kind regards,
>
> Arnout
>
> , i.e. same deal with akka-http-cors
> > (which is now official part of Pekko Http). Given critical time constraints
> > at the time it made sense to fork aws-spi-akka-http into aws-spi-pekko-http
> > but seeing as we are now working on Pekko Connectors 1.1.x now is the
> > perfect opportunity to revisit this.
> >
> > Another thing to note is that due to
> > https://github.com/pjfanning/aws-spi-pekko-http not being contained within
> > Pekko Connectors we had to duplicate code that exposes implementation
> > details[2] which would ordinarily not be required if contained within the
> > pekko-connectors repository.
> >
> > Some of the obvious questions apply i.e. shall we do this officially like
> > we did with akka-http-cors i.e. create an SGA and reach out to the official
> > author? Another thing to note is that the project itself is not that big,
> > i.e. the entire implementation is 3 files[3] with the largest one being
> > ~200 lines long and the sources appear to be predominantly written by a
> > single author so if we go ahead with an SGA, if accepted by the author the
> > licensing/code origin should be quite trivial.
> >
> > 1: https://github.com/pjfanning/aws-spi-pekko-http
> > 2:
> >
> > https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-2.12/com/github/pjfanning/pekkohttpspi
> > ,
> >
> > https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-2.13/com/github/pjfanning/pekkohttpspi
> > and
> >
> > https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-3/com/github/pjfanning/pekkohttpspi
> > 3:
> >
> > https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala/com/github/pjfanning/pekkohttpspi
> >
> > On Sun, Jun 25, 2023 at 7:06 PM Justin Mclean <ju...@classsoftware.com>
> > wrote:
> >
> > > Hi,
> > >
> > > Regarding ICLAs for software grants, it may depend on how the software is
> > > licensed. It is nice to have an ICLA for every major contributor, and if
> > > the software was under an OS license, then it is needed. However, in this
> > > case, it’s under ALv2, so ICLAs are just nice to have but not required.
> > >
> > > Kind Regards,
> > > Justin
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
> >
> > --
> >
> > Matthew de Detrich
> >
> > *Aiven Deutschland GmbH*
> >
> > Immanuelkirchstraße 26, 10405 Berlin
> >
> > Alexanderufer 3-7, 10117 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >
> > *m:* +491603708037
> >
> > *w:* aiven.io *e:* matthew.dedetrich@aiven.io
> >
>
>
> --
> Arnout Engelen
> ASF Security Response
> Committer on Apache Pekko
> Committer on NixOS
> Independent Open Source consultant
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by Arnout Engelen <en...@apache.org>.
On Mon, Feb 5, 2024 at 1:52 AM Matthew de Detrich
<ma...@aiven.io.invalid> wrote:
> So now that Pekko Connectors is at 1.1.x I think it's time to revive the
> discussion for integrating aws-spi-pekko-http within Pekko Connectors
> itself.
>
In general, I think it shouldn't be a goal to include 'everything' into
Pekko Connectors - having an active ecosystem of connectors outside of
Apache Pekko itself would be a sign of health, and we should only have
connectors in the projects that we're prepared to maintain long-term. Also,
now that the first Pekko releases are out, the 'bootstrapping' problems
might be less urgent because of compatibility.
That said...
> it makes sense to include aws-spi-pekko-http[1] within
> pekko itself because its critical dependency to build many projects within
> pekko connectors (AwsLambda, DynamoDb, EventBridge, Kinesis, Sns, Sqs) and
> it also has no real use outside of pekko-connectors considering its an SPI
> between AWS SDK and akka/pekko http
This seems like a strong reason to indeed pull the functionality provided
by aws-spi-pekko-http into Pekko Connectors.
Kind regards,
Arnout
, i.e. same deal with akka-http-cors
> (which is now official part of Pekko Http). Given critical time constraints
> at the time it made sense to fork aws-spi-akka-http into aws-spi-pekko-http
> but seeing as we are now working on Pekko Connectors 1.1.x now is the
> perfect opportunity to revisit this.
>
> Another thing to note is that due to
> https://github.com/pjfanning/aws-spi-pekko-http not being contained within
> Pekko Connectors we had to duplicate code that exposes implementation
> details[2] which would ordinarily not be required if contained within the
> pekko-connectors repository.
>
> Some of the obvious questions apply i.e. shall we do this officially like
> we did with akka-http-cors i.e. create an SGA and reach out to the official
> author? Another thing to note is that the project itself is not that big,
> i.e. the entire implementation is 3 files[3] with the largest one being
> ~200 lines long and the sources appear to be predominantly written by a
> single author so if we go ahead with an SGA, if accepted by the author the
> licensing/code origin should be quite trivial.
>
> 1: https://github.com/pjfanning/aws-spi-pekko-http
> 2:
>
> https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-2.12/com/github/pjfanning/pekkohttpspi
> ,
>
> https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-2.13/com/github/pjfanning/pekkohttpspi
> and
>
> https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-3/com/github/pjfanning/pekkohttpspi
> 3:
>
> https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala/com/github/pjfanning/pekkohttpspi
>
> On Sun, Jun 25, 2023 at 7:06 PM Justin Mclean <ju...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > Regarding ICLAs for software grants, it may depend on how the software is
> > licensed. It is nice to have an ICLA for every major contributor, and if
> > the software was under an OS license, then it is needed. However, in this
> > case, it’s under ALv2, so ICLAs are just nice to have but not required.
> >
> > Kind Regards,
> > Justin
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
>
> --
>
> Matthew de Detrich
>
> *Aiven Deutschland GmbH*
>
> Immanuelkirchstraße 26, 10405 Berlin
>
> Alexanderufer 3-7, 10117 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> *m:* +491603708037
>
> *w:* aiven.io *e:* matthew.dedetrich@aiven.io
>
--
Arnout Engelen
ASF Security Response
Committer on Apache Pekko
Committer on NixOS
Independent Open Source consultant
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by Matthew de Detrich <ma...@aiven.io.INVALID>.
So now that Pekko Connectors is at 1.1.x I think it's time to revive the
discussion for integrating aws-spi-pekko-http within Pekko Connectors
itself.
As stated before it makes sense to include aws-spi-pekko-http[1] within
pekko itself because its critical dependency to build many projects within
pekko connectors (AwsLambda, DynamoDb, EventBridge, Kinesis, Sns, Sqs) and
it also has no real use outside of pekko-connectors considering its an SPI
between AWS SDK and akka/pekko http, i.e. same deal with akka-http-cors
(which is now official part of Pekko Http). Given critical time constraints
at the time it made sense to fork aws-spi-akka-http into aws-spi-pekko-http
but seeing as we are now working on Pekko Connectors 1.1.x now is the
perfect opportunity to revisit this.
Another thing to note is that due to
https://github.com/pjfanning/aws-spi-pekko-http not being contained within
Pekko Connectors we had to duplicate code that exposes implementation
details[2] which would ordinarily not be required if contained within the
pekko-connectors repository.
Some of the obvious questions apply i.e. shall we do this officially like
we did with akka-http-cors i.e. create an SGA and reach out to the official
author? Another thing to note is that the project itself is not that big,
i.e. the entire implementation is 3 files[3] with the largest one being
~200 lines long and the sources appear to be predominantly written by a
single author so if we go ahead with an SGA, if accepted by the author the
licensing/code origin should be quite trivial.
1: https://github.com/pjfanning/aws-spi-pekko-http
2:
https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-2.12/com/github/pjfanning/pekkohttpspi
,
https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-2.13/com/github/pjfanning/pekkohttpspi
and
https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala-3/com/github/pjfanning/pekkohttpspi
3:
https://github.com/pjfanning/aws-spi-pekko-http/tree/main/src/main/scala/com/github/pjfanning/pekkohttpspi
On Sun, Jun 25, 2023 at 7:06 PM Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> Regarding ICLAs for software grants, it may depend on how the software is
> licensed. It is nice to have an ICLA for every major contributor, and if
> the software was under an OS license, then it is needed. However, in this
> case, it’s under ALv2, so ICLAs are just nice to have but not required.
>
> Kind Regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Alexanderufer 3-7, 10117 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
*m:* +491603708037
*w:* aiven.io *e:* matthew.dedetrich@aiven.io
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Regarding ICLAs for software grants, it may depend on how the software is licensed. It is nice to have an ICLA for every major contributor, and if the software was under an OS license, then it is needed. However, in this case, it’s under ALv2, so ICLAs are just nice to have but not required.
Kind Regards,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by Matthew Benedict de Detrich <ma...@aiven.io.INVALID>.
@Justin McLean
Is an ICLA necessary (see
https://github.com/lomigmegard/pekko-http-cors/issues/33#issuecomment-1605429653
)?
On Tue, 20 June 2023, 22:22 Justin Mclean, <ju...@classsoftware.com> wrote:
> Hi,
>
> It would be a good idea to discuss it on the list, but I don’t think a
> vote is required other than if you want to record consensus in a single
> place. No vote by the IPMC is needed.
>
> Kind Regards,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.apache.org
>
>
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
It would be a good idea to discuss it on the list, but I don’t think a vote is required other than if you want to record consensus in a single place. No vote by the IPMC is needed.
Kind Regards,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by PJ Fanning <fa...@gmail.com>.
It needs to be double checked but I think we will need a vote in Pekko
dev list and then a vote in Incubator PMC. I'm sure it's a formality.
On Tue, 20 Jun 2023 at 13:27, Matthew Benedict de Detrich
<ma...@aiven.io.invalid> wrote:
>
> Just letting everyone know that Lomig Mégard has agreed to donate the code
> to pekko-http, see
> https://github.com/lomigmegard/pekko-http-cors/issues/33#issuecomment-1598601691
> . I have also notified him of the SGA (Software Agreement Grant)
>
> Regards
>
> On Tue, Jun 6, 2023 at 9:05 AM Matthew Benedict de Detrich <
> matthew.dedetrich@aiven.io> wrote:
>
> > I will get to this at the EOD
> >
> > Regard
> >
> > On Fri, Jun 2, 2023 at 10:29 AM Matthew Benedict de Detrich <
> > matthew.dedetrich@aiven.io> wrote:
> >
> >> > https://github.com/aiven/guardian-for-apache-kafka/security/dependabot
> >>
> >> I was under the impression that one is the general concept of donating
> >> code and the other is the form to fill out in order to make it official.
> >>
> >> Anyways since no one else has commented for now and it also seems that
> >> it's not a big deal (in terms of PPMC/legal/license) I will leave this open
> >> till early
> >> next week and if there no objections I will then proceed to creating a
> >> cordial message to the https://github.com/lomigmegard/pekko-http-cors
> >> <https://github.com/lomigmegard/pekko-http-cors/pull/19> since
> >> it's the most time sensitive project (and I also think it's highly likely
> >> the author wouldn't have an issue with it).
> >>
> >> On Thu, Jun 1, 2023 at 11:32 AM PJ Fanning <fa...@gmail.com> wrote:
> >>
> >>> Donate Code == Code Grant - 2 terms meaning the same thing.
> >>>
> >>> https://www.apache.org/licenses/contributor-agreements.html#grants
> >>>
> >>> On Thu, 1 Jun 2023 at 09:47, Matthew Benedict de Detrich
> >>> <ma...@aiven.io.invalid> wrote:
> >>> >
> >>> > If they are happy to donate the code is the code grant necessary?
> >>> >
> >>> > On Thu, 1 June 2023, 00:36 Justin Mclean, <ju...@classsoftware.com>
> >>> wrote:
> >>> >
> >>> > > Hi,
> >>> > >
> >>> > > If they (and the community/committers behind it) want to donate it
> >>> to the
> >>> > > ASF then that’s fine, but it’s also OK if it remains a 3rd party as
> >>> it
> >>> > > licensed under the ALv2. I’m not seeing any issues here.
> >>> > >
> >>> > > Kind Regards,
> >>> > > Justin
> >>> > > ---------------------------------------------------------------------
> >>> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> >>> > > For additional commands, e-mail: dev-help@pekko.apache.org
> >>> > >
> >>> > >
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> >>> For additional commands, e-mail: dev-help@pekko.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.dedetrich@aiven.io
> >>
> >
> >
> > --
> >
> > 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.dedetrich@aiven.io
> >
>
>
> --
>
> 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.dedetrich@aiven.io
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by Matthew Benedict de Detrich <ma...@aiven.io.INVALID>.
Just letting everyone know that Lomig Mégard has agreed to donate the code
to pekko-http, see
https://github.com/lomigmegard/pekko-http-cors/issues/33#issuecomment-1598601691
. I have also notified him of the SGA (Software Agreement Grant)
Regards
On Tue, Jun 6, 2023 at 9:05 AM Matthew Benedict de Detrich <
matthew.dedetrich@aiven.io> wrote:
> I will get to this at the EOD
>
> Regard
>
> On Fri, Jun 2, 2023 at 10:29 AM Matthew Benedict de Detrich <
> matthew.dedetrich@aiven.io> wrote:
>
>> > https://github.com/aiven/guardian-for-apache-kafka/security/dependabot
>>
>> I was under the impression that one is the general concept of donating
>> code and the other is the form to fill out in order to make it official.
>>
>> Anyways since no one else has commented for now and it also seems that
>> it's not a big deal (in terms of PPMC/legal/license) I will leave this open
>> till early
>> next week and if there no objections I will then proceed to creating a
>> cordial message to the https://github.com/lomigmegard/pekko-http-cors
>> <https://github.com/lomigmegard/pekko-http-cors/pull/19> since
>> it's the most time sensitive project (and I also think it's highly likely
>> the author wouldn't have an issue with it).
>>
>> On Thu, Jun 1, 2023 at 11:32 AM PJ Fanning <fa...@gmail.com> wrote:
>>
>>> Donate Code == Code Grant - 2 terms meaning the same thing.
>>>
>>> https://www.apache.org/licenses/contributor-agreements.html#grants
>>>
>>> On Thu, 1 Jun 2023 at 09:47, Matthew Benedict de Detrich
>>> <ma...@aiven.io.invalid> wrote:
>>> >
>>> > If they are happy to donate the code is the code grant necessary?
>>> >
>>> > On Thu, 1 June 2023, 00:36 Justin Mclean, <ju...@classsoftware.com>
>>> wrote:
>>> >
>>> > > Hi,
>>> > >
>>> > > If they (and the community/committers behind it) want to donate it
>>> to the
>>> > > ASF then that’s fine, but it’s also OK if it remains a 3rd party as
>>> it
>>> > > licensed under the ALv2. I’m not seeing any issues here.
>>> > >
>>> > > Kind Regards,
>>> > > Justin
>>> > > ---------------------------------------------------------------------
>>> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
>>> > > For additional commands, e-mail: dev-help@pekko.apache.org
>>> > >
>>> > >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
>>> For additional commands, e-mail: dev-help@pekko.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.dedetrich@aiven.io
>>
>
>
> --
>
> 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.dedetrich@aiven.io
>
--
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.dedetrich@aiven.io
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by Matthew Benedict de Detrich <ma...@aiven.io.INVALID>.
I will get to this at the EOD
Regard
On Fri, Jun 2, 2023 at 10:29 AM Matthew Benedict de Detrich <
matthew.dedetrich@aiven.io> wrote:
> > https://github.com/aiven/guardian-for-apache-kafka/security/dependabot
>
> I was under the impression that one is the general concept of donating
> code and the other is the form to fill out in order to make it official.
>
> Anyways since no one else has commented for now and it also seems that
> it's not a big deal (in terms of PPMC/legal/license) I will leave this open
> till early
> next week and if there no objections I will then proceed to creating a
> cordial message to the https://github.com/lomigmegard/pekko-http-cors
> <https://github.com/lomigmegard/pekko-http-cors/pull/19> since
> it's the most time sensitive project (and I also think it's highly likely
> the author wouldn't have an issue with it).
>
> On Thu, Jun 1, 2023 at 11:32 AM PJ Fanning <fa...@gmail.com> wrote:
>
>> Donate Code == Code Grant - 2 terms meaning the same thing.
>>
>> https://www.apache.org/licenses/contributor-agreements.html#grants
>>
>> On Thu, 1 Jun 2023 at 09:47, Matthew Benedict de Detrich
>> <ma...@aiven.io.invalid> wrote:
>> >
>> > If they are happy to donate the code is the code grant necessary?
>> >
>> > On Thu, 1 June 2023, 00:36 Justin Mclean, <ju...@classsoftware.com>
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > If they (and the community/committers behind it) want to donate it to
>> the
>> > > ASF then that’s fine, but it’s also OK if it remains a 3rd party as it
>> > > licensed under the ALv2. I’m not seeing any issues here.
>> > >
>> > > Kind Regards,
>> > > Justin
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
>> > > For additional commands, e-mail: dev-help@pekko.apache.org
>> > >
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
>> For additional commands, e-mail: dev-help@pekko.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.dedetrich@aiven.io
>
--
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.dedetrich@aiven.io
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by Matthew Benedict de Detrich <ma...@aiven.io.INVALID>.
> https://github.com/aiven/guardian-for-apache-kafka/security/dependabot
I was under the impression that one is the general concept of donating code
and the other is the form to fill out in order to make it official.
Anyways since no one else has commented for now and it also seems that it's
not a big deal (in terms of PPMC/legal/license) I will leave this open till
early
next week and if there no objections I will then proceed to creating a
cordial message to the https://github.com/lomigmegard/pekko-http-cors
<https://github.com/lomigmegard/pekko-http-cors/pull/19> since
it's the most time sensitive project (and I also think it's highly likely
the author wouldn't have an issue with it).
On Thu, Jun 1, 2023 at 11:32 AM PJ Fanning <fa...@gmail.com> wrote:
> Donate Code == Code Grant - 2 terms meaning the same thing.
>
> https://www.apache.org/licenses/contributor-agreements.html#grants
>
> On Thu, 1 Jun 2023 at 09:47, Matthew Benedict de Detrich
> <ma...@aiven.io.invalid> wrote:
> >
> > If they are happy to donate the code is the code grant necessary?
> >
> > On Thu, 1 June 2023, 00:36 Justin Mclean, <ju...@classsoftware.com>
> wrote:
> >
> > > Hi,
> > >
> > > If they (and the community/committers behind it) want to donate it to
> the
> > > ASF then that’s fine, but it’s also OK if it remains a 3rd party as it
> > > licensed under the ALv2. I’m not seeing any issues here.
> > >
> > > Kind Regards,
> > > Justin
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > > For additional commands, e-mail: dev-help@pekko.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> For additional commands, e-mail: dev-help@pekko.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.dedetrich@aiven.io
Re: Consider placing dependencies of Pekko modules that use Pekko into Pekko officially
Posted by PJ Fanning <fa...@gmail.com>.
Donate Code == Code Grant - 2 terms meaning the same thing.
https://www.apache.org/licenses/contributor-agreements.html#grants
On Thu, 1 Jun 2023 at 09:47, Matthew Benedict de Detrich
<ma...@aiven.io.invalid> wrote:
>
> If they are happy to donate the code is the code grant necessary?
>
> On Thu, 1 June 2023, 00:36 Justin Mclean, <ju...@classsoftware.com> wrote:
>
> > Hi,
> >
> > If they (and the community/committers behind it) want to donate it to the
> > ASF then that’s fine, but it’s also OK if it remains a 3rd party as it
> > licensed under the ALv2. I’m not seeing any issues here.
> >
> > Kind Regards,
> > Justin
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
> > For additional commands, e-mail: dev-help@pekko.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pekko.apache.org
For additional commands, e-mail: dev-help@pekko.apache.org