@bzg i agree
I think this topic starts with the acknowledgment that receiving a message is work
Reading, understanding, asking for clarification, rephrasing, sorting through what is meaningful for the project vs for the person is work: emotional and cognitive work
What i would love to see is interfaces that empowers individual and teams to accept this work at their own pace with fine-grain control
Github provides "issues" or "no issues", that's too coarse in my opinion
@bzg A friend we have in common told me about a rule they had in a an improv group
Whenever 2 people started arguing back and forth via email with everyone cc'ed, anyone could ask them to stop and they wouldn't be allowed to further reply unless they had met or spoken on the phone
This is replicable (and automatable and adaptable) for software issues
I designed "Woof" (see it e.g. at https://updates.orgmode.org for #orgmode) as a way to circumvent an issue I have with bug trackers: they inherit from a culture of "consumer support", turning issues into attention sink and maintainance burden; taking the opposite direction, Woof focuses on answering the question "How can I help?, in a "volunteers first" culture.
Woof is action-oriented: it relies on a mailing list and grabs from there what's really worth acting upon.
@davidbruant Of course, I should add that my attempt with Woof is really niche and modest, but it really is about fixing what's wrong with traditional bug trackers.
@bzg oh i had never seen this! Thanks for sharing! Where can i read more about Woof?
Or can we schedule a call? 🙂
Instance ouverte pour test - lire les CGU Elle est ouverte à tout agent possédant un compte email en ".gouv.fr" ou la liste disponible sur https://forum.etalab.gouv.fr/t/mastodon-le-reseau-social-libre-et-decentralise-en-plein-decollage/3538