Hi, What Matt was pointing at is to include a <license> (or <copyright>, but let's forget about that for now) element in the XML documents that the hpl and hwf files are.
We could do this by including an option in Hop Gui (our visual IDE that generates the hpl and hwf files) to include the ASF header for the integration test and sample hpl and hwf files. Outside of our code repository, users could use that functionality to include their own header or copyright to the hpl and hwf files they create. Those files would never end up in our repository, so that is out of scope for this discussion. Regards, Bart On Sat, Jun 12, 2021 at 2:09 PM Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > I'm a little confused, and I may be missing some context here. If the work > a part of an ASF project, why do you need to include a copyright statements > anywhere? If the code is not part of the project then we do need to know > the license and copyright owner. While this might be a good place to > include it, it would still also need to go in the LICENSE file, so that a > duplication of work and something that could easily get out of sync. > > IMO (and there may be there ways of dealing with this) just get the > contributors to sign ICLAs so there no issue with their contributions and > there’s no issues with the contents of the LICENSE file or indeed licensing. > > Kind Regards, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
