I agree with Matthew that all our current proposed changes should probably be considered "minor". So it sounds like for the time being we should: 1. Keep all Lightbend headers on existing files as-is and avoid adding new headers. 2. For new files whose code is developed at the ASF, use the ASF notice. 3. For new files with significant portions taken from Lightbend code, use the Lightbend notice.
Presumably most of the planned work will (or can) be done as modifications to existing files, so we shouldn't need to be concerned much about cases 2 and 3. Then sometime in the future we will need some clearer guidance from legal on how to evolve the project forward without placing too much burden on developers to judge whether or not a change is "major". On Thu, Nov 17, 2022 at 3:51 PM Justin Mclean <[email protected]> wrote: > Hi, > > > The thing I don't understand, then, is why there is a distinction between > > new and existing files. > > Short answer is ASF header policy. [1] If you were moving old Akka code > into a new file, then that’s probably not a candidate for an ASF header as > that header is only for code created at the ASF. > > Kind Regards, > Justin > > 1. https://www.apache.org/legal/src-headers.html#headers > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
