I've actually made the sleeping bear analysis before executing and accepted
the risk of landing the wrath of the community, because the bears would get
some poking at some point and IMHO rather now then after 18 months of work.
I don't know much about gorilla's.

Anyhow, both on incubator general and in legal JIRA, there was just more
pushback.
https://lists.apache.org/thread/qvscwtxp6b8kz5105fxhrf8f215px4tg
https://issues.apache.org/jira/browse/LEGAL-625?focusedCommentId=17630097&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17630097

Noneone seems to want to state "it is THE LAW", but from within the
existing organization, I think it's safe to say ~ 9/10 are firmly
unfavorable and only one said it would be possible/not a dealbreaker.

So it's probably safe to state org.apache.pekko will have to be it.

So what about the even less popular idea:

HOCON, as that translates to system properties, both of which suffer from
the same namespace collision problems as packages.

And it is way cheaper in HOCON.

org.apache.pekko{
  ...
}





On Mon, Nov 7, 2022 at 2:05 PM Claude Warren, Jr
<[email protected]> wrote:

> Two lessons I have learned in all my years of software development.
> 1. Don't poke a sleeping bear.
> 2. Don't start dancing with a gorilla unless you are ready to dance until
> the gorilla is finished.
>
> My suggestion: use the org.apache.pekko name, there will be plenty of other
> bears and gorillas to play with later.
>
>
>
> On Mon, Nov 7, 2022 at 8:11 AM Jean-Luc Deprez <[email protected]>
> wrote:
>
> > I observed the legal list was mostly driven by Jira, so I posted it here
> > instead
> > https://issues.apache.org/jira/browse/LEGAL-625
> >
> > The trademark one seems to be a "classic inbox", so I just sent a mail.
> > 🤷‍♂️.
> >
> >
> >
> > On Mon, Nov 7, 2022 at 8:37 AM Jean-Luc Deprez <[email protected]
> >
> > wrote:
> >
> > > I'll reach out to both addresses provided by Justin, see if it can be
> > > settled "quickly".
> > >
> > > On Mon, Nov 7, 2022 at 8:30 AM Jean-Baptiste OnofrĂ© <[email protected]>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> As Pekko is now a ASF project, it would be good to use
> > >> org.apache.pekko (like most of other projects).
> > >>
> > >> However, there is no "strong" enforcement by Apache here, so if we
> > >> have a consensus to use pekko (short name), that's fine for me too.
> > >>
> > >> Regards
> > >> JB
> > >>
> > >> On Thu, Nov 3, 2022 at 10:41 PM PJ Fanning <[email protected]>
> > wrote:
> > >> >
> > >> > Hi everyone,
> > >> >
> > >> > This issue could be contentious but it would be good to get
> agreement
> > >> so we can start making changes in the new git repos.
> > >> >
> > >> > There is discussion about the new package name for Scala/Java
> classes
> > >> at:
> > >> >
> > >> >
> > >>
> >
> https://github.com/mdedetrich/akka-apache-project/discussions/8#discussioncomment-3755587
> > >> >
> > >> > A discussion among members of the Apache Incubator team can be found
> > at:
> > >> >
> > >> > https://lists.apache.org/thread/cjo86gdwvqlqslq68gd0c8hxq6ds6yrz
> > >> >
> > >> > I think it is fair to say that the vote is between 2 options:
> > >> > * pekko
> > >> > * org.apache.pekko
> > >> >
> > >> > I guess the aim would be to get people to vote for one or the other.
> > >> >
> > >> > If there are no objections to this approach, I can call a vote in a
> > few
> > >> days.
> > >> >
> > >> > Ideally people would express their opinions in this thread and when
> > the
> > >> vote is called, that mail email thread would just be for the votes.
> Even
> > >> while the vote thread is open, people can still add their voice to
> this
> > >> thread.
> > >> >
> > >> > Regards,
> > >> > PJ
> > >> >
> > >> >
> ---------------------------------------------------------------------
> > >> > To unsubscribe, e-mail: [email protected]
> > >> > For additional commands, e-mail: [email protected]
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: [email protected]
> > >> For additional commands, e-mail: [email protected]
> > >>
> > >>
> >
>

Reply via email to