Remove myself from CODEOWNERS

[mbuechse]

I don't feel I as a code owner have the necessary control
(for instance, I can be blocked by arbitrary change requests,
which has been draining my energy lately)
-- so I reject this label.

[fkr]

Maybe it makes sense to discuss what "CODEOWNERS" actually means in the sense of complete control. There are other repositories (hardware-landscape for example) where the merge protections aren't set up as strict as the default for the other repositories. Just a thought.
Pinging @SovereignCloudStack/project-board into the discussion.

[jklare]

I think mental health is a critical topic and if @mbuechse does not want to be mentioned or labled as code owner here any more, we should merge this without further discussion.

@fkr On a separate note, we should definitely discuss and write down what exactly is expected from CODEOWNERS to avoid confusion in the future.

[fkr]

I think mental health is a critical topic and if @mbuechse does not want to be mentioned or labled as code owner here any more, we should merge this without further discussion.

I absolutely agree - I just didn't understand @mbuechse 's comment in that sense.

[mbuechse]

Without going into detail too much, I think both of you are correct. I would be grateful for an opportunity to discuss this matter further in a synchronous manner, if possible.

[jklare]

Sounds good. I am going to merge this for now to remove the pressure it might create. In the end, it is as easy to add someone as it is to remove.

Edit: Just saw that it is still marked as draft, so I can't merge it. If this should be merged, please mark it as ready whenever you are @mbuechse

[mbuechse]

@jklare Yes, I actually changed it to draft because I had gotten the impression that other ways could be possible, and that helped to lighten the pressure.