Hi! > 2) To the claim that "we're all equal now", that's hogwash. :-) PHP > Internals may not have a formal structure or hierarchy beyond Release > Managers, but because it's a group of more than 2 people there is of > course an implicit, informal power structure. The best writeup on that > front would be: > > http://www.jofreeman.com/joreen/tyranny.htm > > (It's talking about the feminist movement of the 60s, but the concept > applies to just about every OSS project ever created. And any other > volunteer group since forever.)
Of course, in any community there are people whose opinions have more weight or less weight, depending on factors peculiar to specific community. I hope for ours it is contribution to PHP that plays a significant role :) I would not deny it, but I would say that we do not have people that formally are allowed to take measures like RFC proposes, without talking to anyone but themselves, and everybody is supposed to think it's OK. The rights and the weight in the community are available to everyone, and not reserved exclusively for pre-selected few. > A specifically named community working group / CoC Response Team / > whatever you call it is a way to explicitly separate the addressing of > misbehavior issues from that informal power structure, so avoid (or at > least minimize) people with more "karma" (informal term here) getting an > implicit pass. That sort of implicit tolerance has been very toxic in I do not see how having a troika conferring in secret would avoid that. Wouldn't the members of the supposed power miscreant group influence both the elections of the members of the troika and the troika discussions themselves? But, I don't think we have such a group. At least if it exists, it hides well :) I agree that influential people misbehaving are bad for the whole community. But I think this should be handled by publicly and consensually figuring out the solution, not by throwing bans out of closed doors. > 3) Stas, you claim that such a Response Team and process would be rarely > used. I will not comment on its likely workload, however, I would > submit that having a process to handle misbehavior that rarely if ever > needs to be called upon is perhaps the best ringing endorsement of a > community there can be. That is, if we do setup a Response Team or > whatever, and they are incredibly bored in the job and never contacted, > that's something to be proud of, not upset at wasted time. To be frank, I fail to follow the logic here - if we are a good community (at least within the bounds of current discussion ;) then it doesn't change with having or not having the process, and having the process does not add or diminish that. We can be proud of absence of harassment without any Response Team, its existence is in no way necessary here and does not change anything. We could as well institute a Martian Invasion Task Force and be as proud. All that said, I agree that studying the example of Drupal would be very beneficial, and I am grateful for the suggestions and pointers provided. Indeed, the RFC would probably benefit a lot from including the experience of communities similar to ours. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
