Kevin Matthes

This suggestion failed due to a new Clippy lint which was introduced by Rust 1.63.0 a few days ago. I am going to push a fix.

There had been a bugfix in the Haskell Tree-Sitter. Hence, I added it to this Pull Request, as well.

Internal consistency could be achieved by the definition of further guidelines in the list of contribution guidelines. For new tools, the original developers themselves should describe their tools in the...

As written in the description, this submission contains just one new form. In case this suggestion is accepted, please tell me if and which other issue templates shall be turned...

Due to the intention of the section "Implementation Suggestions", I marked this field optional. All other fields are mandatory. Shall I turn the sole optional field to mandatory, as well?

An option would be to move the YAML forms to a new directory within this repository, say `yaml-forms/` in the repository root. As soon as the beta phase of this...

I am going to remove the blank template as discussed. If my suggestion to prepare the YAML forms in a separate directory is accepted, I will also restore the replaced...

Does the second standard you mentioned provide the possibility to create a list of references for a repository? My usual use case for a CITATION.cff is to provide information where...

As I wrote in the description, the GitHub Actions might require further permissions than just reading access to the file contents. I consider it unlikely but it might happen that...

The advantages are: * The software is now citable in papers. * Utilised resources (other projects, books, papers, ...) are summarised centrally and transparently. * There is a central list...