Sent from my iPhone
> On Nov 6, 2022, at 2:24 PM, Jean-Luc Deprez wrote:
>
> Hi,
>
> So this discussion is currently revived on Pekko dev. But it's seems the
> cards are held by IPMC.
>
> So a very concrete question.
>
> Would someone here vote -1, for a Pekko release or Pekko
Hi,
So this discussion is currently revived on Pekko dev. But it's seems the
cards are held by IPMC.
So a very concrete question.
Would someone here vote -1, for a Pekko release or Pekko graduation, for
the sole reason of the package name being 'pekko.*' instead of
org.apache.pekko.* ?
Noting
On Wed, 12 Oct 2022 at 16:46, John D. Ament wrote:
>
> We should keep in mind that the trademarks requirements and the release
> requirements are two different sets of requirements. They're often
> conflated. The main thing to remember with trademarks and naming is that
> the first time a
We should keep in mind that the trademarks requirements and the release
requirements are two different sets of requirements. They're often
conflated. The main thing to remember with trademarks and naming is that
the first time a project is referenced in documentation, websites, etc, it
must be
I can’t speak for maven but since Akka works with sbt its more likely to use
sbt-assembly to perform any shading which handles cases like this (i.e. see
https://github.com/sbt/sbt-assembly#merge-strategy and
https://github.com/sbt/sbt-assembly#shading).
--
Matthew de Detrich
Aiven Deutschland
In Groovy's case was the trademark handed over? For Pekkos case I suspect
it may be different because Akka trademark is currently owned by another
company which is directly "competing" (Pekko is a fork).
On Tue, 11 Oct 2022, 10:51 Matt Sicker, wrote:
> Based on how Groovy joined Apache, it
Based on how Groovy joined Apache, it seems as though you can keep the
same package name and work on renaming it in a major version if
there's already binary compatibility concerns.
On Tue, Oct 11, 2022 at 7:14 AM PJ Fanning wrote:
>
> Hi everyone,
>
> I'm creating a new thread to avoid filling
Just to clarify wrt to Kafka, its only Kafka core which uses only kafka as a
package name, all of the other modules (talking about maven/gradle modules
here) use org.apache.kafka.
--
Matthew de Detrich
Aiven Deutschland GmbH
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB
One point from the technical perspective:
I remember that akka's config use akka. prefix and it causes several issues
prevent you shaded it. That is, Maven Shaded Plugin cannot distinguish a
string literal starts with akka. a config key or package name.
>From this perspective, if possible, I
Hi
I am not sure about Kafka and Netbeans cases, as I was not working
inside the foundation back there.
For the recent years' new podlings, `org.apache.*` is preferred by the
incubator.
Sheng Wu 吴晟
Twitter, wusheng1108
PJ Fanning 于2022年10月11日周二 20:14写道：
>
> Hi everyone,
>
> I'm creating a new
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
11 matches
Mail list logo
