PRINCIPALS.md and MAINTAINERS.md

[cimnine]

Related Issue: n/a

New Behavior

I tried to write down the principals with which we respond to feature requests and – as an extension of that – to pull requests.

Contrast to Current Behavior

The principles are just in the heads of the maintainers. There is no consensus on them and they can't be challenged easily.

Discussion: Benefits and Drawbacks

I hope that this makes it clearer what the guiding principles behind the project are. Also, I hope to make it clearer, who is a maintainer of the project at any given time, and to have a process of stepping down.

All this is up for discussion and I would welcome anyone to share their opinion. I also hope, that these principles will not be set in stone and that they can be changed when things change.

Changes to the Wiki

n/a

Proposed Release Note Entry

not relevant

Double Check

• [x] I have read the comments and followed the PR template.
• [x] I have explained my PR according to the information in the comments.
• [x] My PR targets the develop branch.

[cimnine]

I believe we should also add something about the container vs the scaffolding infrastructure like the compose file and build script.

[cimnine]

Also, we should probably somewhere state which runtime(s) we intend to support, and which versions of them (like LTS only or latest major, or something else). Historically, we focused on Docker and ignored other runtimes, such as Portainer, Podman, etc.