Trademark policy

In short: use the code freely, say truthfully that you tested with gpconf™, and give a fork a name of its own.

gpconf™ is a trademark of NEOGY LLC. The Apache-2.0 licence covers the corpus’s code and data and, in its section 6, grants no right to the name; this page says how the name may be used.

The licence lets you use, change and share the code and data. The name is different: it tells people that a result came from gpconf as NEOGY LLC publishes it, and that only works if the name stays with that project.

You may, without asking

• Say that your software was tested with gpconf, or that it passes gpconf, when an unmodified release produced the result. Name the version: “passes gpconf 0.7.0”.
• Write about gpconf, link to it, cite it (the corpus’s CITATION.cff has the DOI) and show its reports.
• Run it in your own tests and pipelines, including the GitHub Action.
• Fork it, and say in the fork’s description that it is a fork of gpconf.

You may not

• Call a fork, a changed version or another product gpconf, or a name easily taken for it, such as gpconf2 or gpconf-pro.
• Publish a package under such a name on PyPI, npm or any other registry.
• Report a result as gpconf’s when it came from a changed runner, cases or expected values. Such a result is your fork’s; say so under the fork’s name.
• Suggest that NEOGY LLC endorses, certifies or works with you, unless it does.

Anything else

If a use is not covered here, ask first: open an issue on the corpus repository. Nothing on this page limits what the Apache-2.0 licence lets you do with the code and data.