> 2. Standardizing around a single (or small number of) workflows will make
> some people unhappy. But that is an acceptable price to pay because of the
> general benefit to the project *as long as the correct solution is
> adopted*. Unity is more important than minority opinions on this
> particular issue.
Keep in mind that unhappy people quit.
I don't think that unity is so important that we're willing to sacrifice
project members.
What exact issue are we trying to fix?
At the bottom, is it ok for a package to have a single maintainer or not?
Perhaps we should start with a vote on this. So far it has been completely ok.
If as a project this has to change, I think a vote is warranted.
If that should pass, we can decide which specific tools impose on people.
Best
--
Salvo Tomaselli
"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei
https://ltworf.codeberg.page/Attachment:
signature.asc
Description: This is a digitally signed message part.