After thinking about it some more I really believe strongly that our developers should have an easy time adding more integration tests. It's really critical to our project in the longer term. Manually editing XML files to copy/paste an ASF header in there can not be part of that experience. It's simply out of the question. I don't see the same requirement for other Apache projects that have .avro or .parquet files as part of their test-suites. The obvious reason being that folks are not really opening up these file formats with a text editor... just like we never do this with .hpl/.hwf files. So we're just being punished for having chosen an XML format.
Since we've exhausted all other possibilities I'll start the discussion on dev to move to a different file format for our metadata. All the best, Matt 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 -- Neo4j Chief Solutions Architect *✉ *matt.cast...@neo4j.com ☎ +32486972937
