Hi! > Here is an RFC to "Prevent disruptions of conversations" > https://wiki.php.net/rfc/prevent_disruptions_of_conversations?do=edit
I am not sure what is the purpose of this. Teaching other adults how to behave? Its usually a futile task. The RFC is expressed in extremely vague terms, like: they are not allowed to use their voice to try to prevent other people's conversation. What's "preventing other people's conversation"? How could I, not having access to admin interface of the list to unsubscribe/block people, prevent anybody from conversing with anybody else on the list? Sending many more emails than other contributors. What's "many more"? Who decides it? Why sending more emails is bad - maybe it's RFC author answering questions? Maybe it's somebody who knows a lot about the topic of the discussion? Repeatedly telling other contributors that they are not allowed to discuss You mean like this RFC which literally just told people they are not allowed to send "too many" emails and discuss RFC votes? Well, I guess it's not "repeatedly" but if this RFC is mentioned once more... Repeatedly asking people to hold off on proposing an RFC. Why not? If I think an RFC makes no sense, why won't I suggest the potential proposer to save themselves the effort and the negative feelings by not proposing something which is no good? However other behaviors that people find disruptive What people? Who chooses which people are allowed to ban people from discussions by declaring them "disruptive" and why do we need to give them such power? And why would we want to have such people? That looks like a recipe for disaster. It is very disruptive to have people say that they reject the result of an RFC vote So now people are not allowed to speak about their opinions that something wasn't done properly here. Not only we declare the RFC vote process sacred and the only possible way to decide anything forever and reject even trying to find any other ways - now we want to ban people that dare to speak about possible deficiencies and problems in our decisions from the community completely? What is going on here?! Being open to criticism and disagreement is the only way to maintain the quality of any community - software or otherwise. Once we start banning people for disagreeing with the holy RFC, there wouldn't be any reasonable discussion possible. It's only when a conversation is adversarial that the conversation should remain on list. Why should we police actions of people outside community? If you don't want to receive emails from a particular person, I could help you with setting up your email filters. There are other members of the community that I heard recently also are pretty proficient with those, so if you don't want to speak with someone, it is easy to achieve without starting to pretend to be Email World Police. I am sorry if somebody sent you a nasty email (I have no idea if somebody did, but looks like it) but that's not the reason to introduce martial law here. > * although the RFC would only be applicable to messages sent once it > might be approved, it would still be nice if people consider how their > messages affect other people before then. I have read this message, announcing this RFC, and it affected me very negatively. It looked to me as an attempt, under the guise of making discussion better, to stifle the expression, introduce arbitrary and vague rules, which would inevitably lead to rule lawyering and replacement of discussion on technical merits with discussion of who should not be allowed to talk at all - the very thing this RFC ostensibly tries to prevent it will inevitably produce. > * everyone should bear in mind this RFC might gain more attention from > people outside the PHP internals community than normal. If I wasn't convinced before that this is the thing we need the least of all I am completely convinced now. Nothing makes working through difficult issues better than a good twitter mob and a bunch of yellow journalism outlets quoting people out of context and trying to pull them into whatever campaign they are trying to wage at this time. Seriously, I don't see any single thing "more attention from people outside" would make better. Not one. > * I think this solution isn't going to be a great one I agree wholeheartedly. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
