Suggestion: use labels sparingly

Look at other popular and widely-used projects on GitHub, such as https://github.com/openssl/OpenSSL.git and https://github.com/OpenSC/OpenSC.git

Both have tons of issues to process, but an issue would have maybe one, at most two labels. Here I see it rare for an issue to have less than *four* labels, usually five or six.

Please reconsider, and stop throwing every possibly-remotely-applicable label at an issue - it's both confusing and annoying to the viewer. Pick one that's the closest, and stay with it.

My $0.02.

Esamina l’uso attuale delle etichette delle issue nel repository e confrontalo con gli esempi di OpenSSL e OpenSC collegati nell’issue. Il lavoro è completato quando si concorda una policy di labeling più ridotta e la si applica in modo coerente, ma non sono stati identificati file di implementazione né test.

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