Thanks everyone. I'll leave the license headers as they are. On 2023/06/27 00:49:07 Paul King wrote: > IANAL, but the advice I've been given informally by IP lawyer friends many > years ago is don't change the existing copyright. > > You could instead amend to something like: > > Original version: > > Copyright (C) since 2016 Lightbend Inc. > > Subsequent changes made by the Apache Pekko community: > > Copyright 2022 The Apache Software Foundation. > > > Also, at the time, it was commented by the same lawyer folks that in many > (but not all) jurisdictions, you can leave the year out of individual files > as long as you have a generic NOTICE file with the year range, e.g. > 2022-2023 for Pekko. The date specifics for any individual file/change can > be determined "Ex Post Facto" from the version control system. But I > presume the LEGAL folks will give you further up to date info. > > Cheers, Paul. > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Tue, Jun 27, 2023 at 12:40 AM PJ Fanning <fannin...@apache.org> wrote: > > > Hi everyone, > > > > The Pekko community is working on a release of our core repository. We > > have a number of other repositories that we will release later. > > > > In one of these downstream repositories, the source code has Lightbend > > copyrights that say (example [1]): > > > > Copyright (C) since 2016 Lightbend Inc. > > > > Since the Pekko forked this code at a point in September 2022, is it > > ok to change this copyright to this? > > > > Copyright (C) 2016-2022 Lightbend Inc. > > > > It doesn't seem right to leave the copyright claim open ended and > > effectively implying that any changes made this year by the Apache > > Pekko community are covered by Lightbend copyright. > > > > Generally, I wouldn't modify any headers like this but this one seems > > to require modification. > > > > Any insights would be appreciated. > > > > Regards, > > PJ > > > > [1] > > https://github.com/apache/incubator-pekko-connectors/blob/178795f6882e2d06524962f30359691889489fd5/s3/src/main/scala/org/apache/pekko/stream/connectors/s3/Utils.scala#L11 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
--------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
