Call for co-maintainers

I want to scale work on GitUI better. Over the years I have been a driver of this project but also a single point of contention. This can be improved.

Calling for co-maintainers is open to everyone who contributed before but also to everyone willing to join.

# The three levels/ranks of roles

1. become a **contributor**, there is plenty of simple topics to jump on marked as [good-first-issue](https://github.com/extrawurst/gitui/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22), join the `gitui` channel on [discord](https://discord.gg/rQNeEnMhus)
3. become a **reviewer** and join the internal discord channel
4. become a **co-maintainer** with merge rights

# How to become a reviewer?

* have at least one PR contributed/merged
* have at least one PR of someone reviewed and coached to the point of mergability

Aside from that just ask me and show interest to gain this status. I will invite you to my discord and invite you to the project as reviewer.

# How to become Co-Maintainer?

That one is less clear defined but basically means repeated contribution via code and/or reviews. But mostly requires good communication in between, dependability and continuity.

# FAQ

## Do I need to be great at Rust?

No I am sponsoring beginners work via Draft-PRs and feedback, reviews. Just show the dedication and I will help where I can.

## I have not a lot of time but would like to help?

Thats alright, any help counts, see above: As long as communication is good and I know when and when not to depend on you we can make it work. We all have a life :)

## I don't have time to code at all or to review code, can I still support?

Absolutely - spread the word!
* Post on the various channels that you use GitUI
* Share our release messaging
* Jump officially into the role of the GitUI release PR: #1728

Lets drive GitUI to 1.0 and beyond! ❤️

Si tratta più di un invito a reclutare un co-maintainer e a definire la governance del progetto che di un’attività di codice definita. Leggi i criteri del ruolo, l’elenco collegato di good-first-issue e la release PR #1728 per individuare un percorso di contribuzione; questa issue non specifica alcuna modifica concreta né una condizione di completamento.

Scritto dal modello di indicizzazione a partire dal testo della issue.