You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "J-L (Jira)" <ji...@apache.org> on 2022/11/07 08:04:00 UTC
[jira] [Updated] (LEGAL-625) Java/Scala package names in ASF context
[ https://issues.apache.org/jira/browse/LEGAL-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
J-L updated LEGAL-625:
----------------------
Description:
As per threads:
# [https://lists.apache.org/thread/cjo86gdwvqlqslq68gd0c8hxq6ds6yrz]
# [https://lists.apache.org/thread/5vw58s7x9gzkt9h627xv705j32fxljc9]
We're discussing within the Apache Pekko community, which Java/Scala packages names to use.
The discussion is between:
# _pekko_ short and aligns with the project's previous package name style
# _org.apache.pekko_ longer, but in line with the ASF conventions.
Note: Maven org/group ID is not at discussion, so will be _org.apache.pekko_
Part of the discussion ends up wondering whether using option 1 will cause trouble later down the road, for intermediate incubator releases or even graduation. We certainly don't want to land in a situation where we need a rename 2 years from now.
During the discussion it was brought up that there might be legal or trademark hurdles, which leads to raising the issue here.
If there's a risk at veto's there's not much point in discussing it further.
was:
As per threads:
# [https://lists.apache.org/thread/cjo86gdwvqlqslq68gd0c8hxq6ds6yrz]
# [https://lists.apache.org/thread/5vw58s7x9gzkt9h627xv705j32fxljc9]
We're discussing within the Apache Pekko community, which Java/Scala packages names to use.
The discussion is between:
# _pekko_ short and aligns with the projects previous package name style
# _org.apache.pekko_ longer, but in line with the ASF conventions.
Note: Maven org/group ID is not at discussion, so will be _org.apache.pekko_
Part of the discussion ends up wondering whether using option 1 will cause trouble later down the road, for intermediate incubator releases or even graduation. We certainly don't want to land in a situation where we need a rename 2 years from now.
During the discussion it was brought up that there might be legal or trademark hurdles, which leads to raising the issue here.
If there's a risk at veto's there's not much point in discussing it further.
> Java/Scala package names in ASF context
> ---------------------------------------
>
> Key: LEGAL-625
> URL: https://issues.apache.org/jira/browse/LEGAL-625
> Project: Legal Discuss
> Issue Type: Question
> Reporter: J-L
> Priority: Major
>
> As per threads:
> # [https://lists.apache.org/thread/cjo86gdwvqlqslq68gd0c8hxq6ds6yrz]
> # [https://lists.apache.org/thread/5vw58s7x9gzkt9h627xv705j32fxljc9]
> We're discussing within the Apache Pekko community, which Java/Scala packages names to use.
> The discussion is between:
> # _pekko_ short and aligns with the project's previous package name style
> # _org.apache.pekko_ longer, but in line with the ASF conventions.
> Note: Maven org/group ID is not at discussion, so will be _org.apache.pekko_
> Part of the discussion ends up wondering whether using option 1 will cause trouble later down the road, for intermediate incubator releases or even graduation. We certainly don't want to land in a situation where we need a rename 2 years from now.
> During the discussion it was brought up that there might be legal or trademark hurdles, which leads to raising the issue here.
> If there's a risk at veto's there's not much point in discussing it further.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org