Thanks PJ. I want to note that you're making an assumption there that supporting a Java package name for compatibility might/would be a trademark infringement.
Fuller context - I was raising this after seeing a JIRA issue on license-discuss about org.apache.pekko vs pekko, and I hadn't seen any discussion on supporting existing users with the akka namespacing. Apache-wise, it's unusual to have a situation where we are supporting an existing user community with a fork. Presumably not unique, because we've been around a while, but a comparable situation isn't jumping to mind. IIUC the EOL for Akka Open Source is September 2023? From the JIRA issue I saw that one plan is for them to migrate by search/replace of akka->org.apache.pekko. Is the space pretty shallow dependency wise that that will work? Or will folk find there are many other open source projects they depend on, that subsequently depend on Akka, and migrating is going to be interesting to say the least? Thanks again, Hen On Tue, Nov 8, 2022 at 1:59 PM PJ Fanning <[email protected]> wrote: > Lightbend continue to publish akka jars - so Pekko will not publish > any akka jars. We do not want to infringe on any Lightbend trademarks. > > The first Pekko release will have `org.apache.pekko` instead of `akka` > in package names. Likewise, all jars will have `pekko` in the names > instead of `akka`. > > On Tue, 8 Nov 2022 at 22:50, Hen <[email protected]> wrote: > > > > I see conversation on moving to a new Apache java package name. > > > > Are there plans to also publish under the old Java package name? > > > > Given the context that this project is (iiuc) being created to support a > > community who were abandoned by a switch from open source to $proprietary > > licensing, it feels like in the short term (1-2 years) there will be a > > dependency tree that will take time to work itself over to Pekko and any > > urgent fixes will be difficult to use. Forking under the old package name > > for critical urgent fixes is what I believe initial users will want. > > > > Thanks, > > > > Hen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
