Societies have written regulations, which you MUST follow: it is what participants expect and what defends your actions in case of court cases. There never, ever is self-elected elite which will be able to solve conflicts.
Expressions and behaviour of participants is either lawful (so must be accepted), or unlawful (not for "normal" people to decide about punishment). Regulation is different for open and closed meetings, and media.
Those American Style Code of Conduct must be banned from our events: they damage us. FOSDEM, CCC and many more, show us how to do it: how to stay sane.
To solve this: ditch all rules which violate freedom of speech. For each event, assign a team of mediators in case of conflicts. Harassment claims and such are police business.
]]>But forbidding people to say unpleasant things beforehand is not allowed in the EU. Kicking people out solely because a few non-elected others do not like your expression is not acceptable. But it has been done a few times now. Giving your own interpretation on very sensitive terms as harassment is really wrong.
Event organize MUST mediate when there are problems. As resolution, the MAY kick-out someone for that event. They can be asked in court for their reasons, and will often loose. (That's why you should get an organizers insurance)
Organizers can impose a bit stricter rules when the event is for members of an association, where the rules have passed a vote on the members meeting. We lack all of that in the Perl community, so end-up in horrible fights and a self-elected elite.
]]>TPF should offer a boilerplate set of community guidelines which perl affiliated projects may elect to adopt.
Beyond that, perhaps a mediation service should be offered to assist in resolving complaints. Projects may then wish to opt-in to the outcome of these resolutions.
This is not the first time this has happened, it is however the first time the perl community didnt pile on to someone. That's something *everyone* should think about.
https://blogs.perl.org/users/lets_code_perl/2019/07/tpf-perl-deserves-better-please-do-better.html
There was
A truth-seeking process that was haphazard at best, in ways that are obvious to anyone with the slightest bit of knowledge of what happened
An expeditionary power-grab despite explicit requests not to do so
A punishment that was clearly not proportional to the incidents described
A willingness to cherry pick people from one side of a conflict where both sides have behaved in ways they really shouldn't have.
An apparent willingness to punish people who associate with Subject
Some would argue that you've described the House of Representatives hearing about the Jan. 6 capitol incursion.
Perhaps politics is politics, sigh.
]]>MooseX::Extended
does not encourage loose and sloppy by default. You, as a developer, have to make a conscious choice to open your object attributes to being set via the constructor rather than having this be the default.
Further, MooseX::Extended
retains the has
function, completely unchanged (e.g., it still requires is => 'rw|ro|bare'
), for those who prefer it.