proposal: add maintainer file

[git-bruh]

A seperate maintainer file is useful as it isn't tied to git history. Most people will be cloning with --depth=1 and the author of the last commit shows up as the maintainer for all packages until another commit is pushed for them.

It also allows running bulk operations like changing sources to use/not use VERSION and possibly auto updating packages

[dilyn-corner]

Would rather add a line to the build files.

While we're at it, enforcing SPDX license identifiers would be a nice to have.

[sdsddsd1]

Would rather add a line to the build files.

While we're at it, enforcing SPDX license identifiers would be a nice to have.

I second an additional line at the build file. Idk how others feel about the 2nd line being preserved blank. I think it would fit the purpose here. Should be easily parse able.
Adding another file to the package format feels meh, as its violating the format and opens the door for other additional stuff 2.

[illiliti]

We have README. I think it's fine place to leave maintainer contacts there.

[dilyn-corner]

Does this mean we enforce README files for all community packages? Sep 1, 2022, 4:35 PM by ***@***.***:

…

We have > README> . I think it's fine place to leave maintainer contacts there. — Reply to this email directly, > view it on GitHub <#96 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AEVM3SKED4345SBUSMDTFTLV4EHSVANCNFSM6AAAAAAQCU3F5M>> . You are receiving this because you commented.> Message ID: > <kiss-community/repo/issues/96/1234752477> @> github> .> com>

[illiliti]

Unless a package has been contributed via a diff(not a patch) file, no. Anyway, we can always fallback to git.

[apprehensions]

miscellanous question: since kiss-maintainer gets the maintainer via the package's version file, and say a package was broken and needed a simple fix in the build file and someone submitted a PR, wouldn't the package need its revision bumped? if thats the case then the person who submitted the PR/patch would 'become' the maintainer

[illiliti]

That's actually why kiss has policy of maintainer-only updates. Only maintainer can mess with its own packages. I'm not sure if this policy still stands, but that's how things worked before.

[git-bruh]

https://codeberg.org/kiss-community/repo/issues/96