>Artistic (volatile) temperament” is just a euphemistic way of saying “engages in unchecked abusive behaviour toward their peers”, and no member of the community should be expected to bend over backwards to >tolerate this or to turn a blind eye to it.
You completely, utterly and totally misread the meaning and spirit of what I said.
To reiterate, if the maintainer is responsive, my opinion is that is a courtesy to notify him/her.
That's all. Some people are more attached and involved with their code and would appreciate
the gesture.
No need to imagine that the maintainer is demonstrating "unchecked abusive behavior."
For Pete's sake.
On Tuesday, December 12, 2017 7:09 AM, Graham Leggett <minfrin@xxxxxxxx> wrote:
On 09 Dec 2017, at 8:21 PM, Philip Kovacs <pkdevel@xxxxxxxxx> wrote:
I am opposed to allowing PP unfettered access to projects in which the maintainer(s)are responsive. It's common for developers to have artistic (volatile) temperaments ,like a painter who paints on canvas owned by someone else.
We need to nip this kind of thing in the bud.
“Artistic (volatile) temperament” is just a euphemistic way of saying “engages in unchecked abusive behaviour toward their peers”, and no member of the community should be expected to bend over backwards to tolerate this or to turn a blind eye to it.
Even more specifically nobody at Fedora should be forced to ask special permission from or give special notification to specific individuals over and above the established procedures before doing their work. Their commit privileges / karma / following the established procedure give them that permission.
If someone makes a change to your code, start with the premise that the person who made the change did so in good faith, and respond appropriately from there.
Regards,
Graham
—
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
