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é 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"
+1
Easier to filter ;))
Regards
JB
On Thu, Nov 3, 2022 at 9:25 AM Claude Warren, Jr
wrote:
>
> Currently the commits from git are getting added to the dev email list
> creating a lot of noise.
> This proposal is to create a comm...@pekko.apache.org email list and have
> all git messages go ther
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
Hi,
> I tried to poke the related incubator general thread once more asking if
> anyone would vote -1 for graduation or release for the short package name,
> but I guess mails from non subscribers are refused.
Your email would have ended up in moderation so it may take a day or two to
show up.
I am in favor of "org.apache.pekko" mainly as it explicitly highlights that
this is an apache project.
On 2022/11/03 21:41:25 PJ Fanning 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.
>
> Th
pjfanning merged PR #25:
URL: https://github.com/apache/incubator-pekko/pull/25
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@pekko.ap
I tried to poke the related incubator general thread once more asking if
anyone would vote -1 for graduation or release for the short package name,
but I guess mails from non subscribers are refused.
Anyhow, IMHO, if the long name is used, I'd feel it has to be done
consistently, so also in HCON,
In my opinion I think people are really under-estimating the criticality of
this point. I did some research on this a few weeks ago and as far as I can
tell there isn’t a hard rule saying that you must use the org.apache prefix
however for Pekko to become a top level project it needs to get vote
mdedetrich commented on issue #24:
URL: https://github.com/apache/incubator-pekko/issues/24#issuecomment-1304774533
So one of the underlying motivations for making this issue is that I
actually want to delete (not just archive) the old repos to avoid confusion and
also help in things like S
mdedetrich commented on issue #23:
URL: https://github.com/apache/incubator-pekko/issues/23#issuecomment-1304773976
> This is something we will want to implement. I'm not yet sure that we have
enough stability in the dev pipelines though.
So we don't have to enable all of the status c
Hi all,
I want to express my opinion on this topic. Pekko is and will be a project that
will have several non technical problems:
- Legal: copyrighted code, possible infringements of licenses, trademarks...
- Showcase independence: why this won't go there same route as the project is
forking?
A
spangaer commented on issue #23:
URL: https://github.com/apache/incubator-pekko/issues/23#issuecomment-1304766692
Explicitly having to name the status checks for that feature to do anything
meaningful, is an additional complication.
--
This is an automated message from the Apache Git Serv
pjfanning commented on issue #23:
URL: https://github.com/apache/incubator-pekko/issues/23#issuecomment-1304762548
This is something we will want to implement. I'm not yet sure that we have
enough stability in the dev pipelines though.
In the end of the day, we are months away from an
Hi
> The difference between may or will is what is this hinges on.
I can not predict how the IPMC would vote on this. If the project comes up with
a good reason why they need to use a short name, it would most likely be
accepted, but as far as I know, no other project has gone down this path. I
pjfanning commented on issue #24:
URL: https://github.com/apache/incubator-pekko/issues/24#issuecomment-1304762150
ASF is still discouraging us from using Github Discussions for Pekko team
business - that Discussions is meant more for user forums.
https://issues.apache.org/jira/browse
mdedetrich opened a new issue, #23:
URL: https://github.com/apache/incubator-pekko/issues/23
Currently its possible to merge a PR even if the status checks fail or even
in the small span of time before they get triggered. Now that we have CI
running properly, we should update the `Require s
> An initial incubator release probably not, but it may block later
releases or graduation.
For question at hand, this should be 'a package rename for life' so
graduation should be the assumption.
The difference between may or will is what is this hinges on.
> so using org.apache.pekko may give
pjfanning opened a new pull request, #25:
URL: https://github.com/apache/incubator-pekko/pull/25
https://lists.apache.org/thread/jrqjdshp9vll8o75drdrynzk4b670vtn
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
Hi,
> If the other option is chosen, would that cause that much trouble that it
> blocks a release?
An initial incubator release probably not, but it may block later releases or
graduation.
> When it comes to branding, I'm assuming the general brand not existing in
> software should be some for
mdedetrich opened a new issue, #24:
URL: https://github.com/apache/incubator-pekko/issues/24
Now that we have github discussions enabled in incubator pekko, we should
try to see if its possible to migrate relevant discussions from
https://github.com/mdedetrich/akka-apache-project/discussion
Of course I was too fast in writing that last paragraph, you said ASF
branding.
Anyhow, surely there will be enough Apache writen all over the place to
leave little doubt on that front.
On Sun, Nov 6, 2022, 07:51 Jean-Luc Deprez wrote:
> Hi Justin,
>
> Thanks for the response, but that's the an
21 matches
Mail list logo
