mesa-resources: Basic stuff, scripts, and so on used when hacking on mesa
A brief description of what it contains:
* jhbuild: a custom moduleset, and a template jhbuildrc file for mesa
and piglit building
* deqp: basic stuff for deqp.
* piglit: basic stuff for piglit.
* testing: tools and scripts to use while testing.
* gnome-session: tools to run GNOME with your desired GL driver
Scripts written assisted by AI is allowed, although we discourage
script fully written by AI.
We follow the AI guidelines set by Mesa, so quoting the more relevant
parts from mesa docs/submittingpatches:
"The submitter is responsible for the code change, regardless of where
that code change came from, whether they wrote it themselves, used an
"AI" or other tool, or got it from someone else. That responsibility
includes making sure that the code change can be submitted under the
MIT license that Mesa uses."
Disclosure is always required when "AI" was involved in the creative
process of coming up with the code, except in the following cases:
- Trivial or small changes that wouldn't be copyrightable regardless of
"AI" involvement. For example something like a "min" function fit this
category.
- Mechanical changes where the expected result is obvious and not up to
interpretation, ie. when it would be the same regardless of what
tooling was used. For example, autocomplete, refactoring the name of a
variable and similar activities fit this category. In these cases it is
still recommended (but not required) to disclose the tool used,
eg. "AI", "sed", "cocinelle", etc. in order to ease the review process.
We suggest the following scheme to disclose the level "AI" tooling was
involved:
- ``Assisted-by: TOOL (OPTIONAL: MODEL)`` for when "AI" was involved in making
decisions or also generated parts of the code.
- ``Generated-by: TOOL (OPTIONAL: MODEL)`` for when almost all the code was
generated through "AI".
Do not use the ``Co-authored-by`` tag as this one is reserved for human
co-authors."