Feature request/proposal: maintainers/authors optional infos in easybuild files

[APN-Pucky]

I saw several eb's where the first line comment was who created it. E.g.

• https://github.com/easybuilders/easybuild-easyconfigs/blob/da36e3ba4e5d1db770272b59e5e3e2f5159e4b0f/easybuild/easyconfigs/o/OMA/OMA-2.1.1.eb#L4
• https://github.com/easybuilders/easybuild-easyconfigs/blob/da36e3ba4e5d1db770272b59e5e3e2f5159e4b0f/easybuild/easyconfigs/b/BEDTools/BEDTools-2.30.0-GCC-11.2.0.eb#L4

I think that could also be helpful with directing issues to the original creator if they arise and later the eb's could be credited in repology (cf. repology/repology-updater#705 #4152).
I saw something like that mentioned in https://hackmd.io/tZtz6vMmRfGL6N9Rf__OEA#2023-11-13-sprint-1000-CET.

I'd suggest something like the pyproject.toml standard

authors = ["Alexander Puck Neuwirth <alexander@neuwirth-informatik.de>"]

allowing for multiple maintainers and optionally their email.

[Micket]

So, to be clear I'm definitely not speaking with any special authority, but I really hope we don't start doing this in the easyconfigs repo.

I do wish people would stop adding those comments, and I wish instead everyone just did nothing.
Fortunately, i think all maintainers and most frequent contributors all always ignore those contribution-comments completely and never add ourselves. Otherwise the comment fields would be insane (and so would an author list of everyone whoever bumped a version)

One-off easyconfigs like we have aren't really "maintained" by anyone.
Most contributions the author is less of a maintainer and more of a "whoever-last-decided-to-update-the-version-number-string-and-submit-a-pr".
I certainly do not want questions from the several hundreds easyconfigs I've made/updated directed to me.
If a question actually does arise where one needs into why something was done a certain way, one should not look at some author list of anyone who ever touched the version string, or even who touched it last, but the PR it stemmed from, who reviewed and merged that, a git blame. Maybe. It's not like that person has taken up the mantle of maintainer.

We do push for credits on patches and easyblocks, where there certainly is more choices made, and, of course, there is the git history.