From: Dale <rdalek1967@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] ComRel / disciplinary action reform proposal
Date: Sun, 15 Jan 2017 15:59:46 -0600 [thread overview]
Message-ID: <44e25740-6b88-43b9-e63b-aea93eff5caf@gmail.com> (raw)
In-Reply-To: <20170115195209.70d3a748.mgorny@gentoo.org>
Michał Górny wrote:
> Hello, everyone.
>
> Since the things around ComRel seem to have cooled down a bit, I think
> we can now start a serious discussion on how disciplinary action
> handling could be improved. While the recent complaints were focused on
> ComRel, I would like to take a more generic approach since ComRel is
> not the only body in Gentoo capable of disciplinary action.
>
> Therefore, I'd like my proposal to concern all cases of disciplinary
> action, involving but not limited to: ComRel, QA, Forum moderators, IRC
> moderators, Wiki admins and any other entity capable of enforcing
> a disciplinary action against developers and users.
>
> Note: throughout the mail 'users' include all people involved on
> the Gentoo communication channels, developers, users, bystanders
> and bots alike.
> <<< SNIPPAGE >>>
>
>
> What do you think?
>
I help moderate/admin a social site. I sometimes have to remove
content, restrict and ban members. I don't know how much of this can
apply because I don't know if some or any of this is possible on Gentoo
sites including B.G.O., IRC etc etc.
As a example of how we do things. If I remove content, I take
screenshots of it and then document it in a private staff only area. It
doesn't matter if it is text, images or what. If the site owner gets a
complaint or question, or another staff member wants to see what the
member did, they can look and see what it was for even if I'm not
online. If it is severe enough to require restriction of posting
privileges, then I go do that as well. When the member comes back
online, they get a notice that the account is restricted and to provide
further notice to the member, plus anyone else wondering, the word
Restricted is shown next to their name publicly. It's a
yellowish/orange color but that may not matter here. Also, the member
can see who did the restriction, how long it will last and the reason
for it. I enter that in during the restriction process. Other members
can see that the member is restricted but not what for or how long or by
who. Only the member is question can see that part.
If the post/content is severe enough to require a ban, then the member
when they return is shown that their account has been banned, the reason
for it and who did it. Also, next to the members name, it shows in red
the word Banned. Again, other members know the ban occurred but not who
did it or why. The member that is banned tho does see who did it and
why. Again, it provides privacy but also lets other members know not
to expect future communication.
With that system, the person that action was taken on knows who did it,
why and for how long or if they are banned. At the same time, other
members can not see anything but that they are restricted or banned.
That allows some privacy which you seem to want maintained but also
gives enough info in public as to why they are no longer active.
This is the good thing about this system. Let's say ComRel John gets a
complaint and suspends posting privileges for one week for member xyz.
The member that is suspended can see that they can no longer post, that
it was either done by John or ComRel, your choice on that, plus others
can see why they are no longer participating in whatever activity was
going on. Also, if John did something he shouldn't have, other ComRel
members can see it but you may can set it so that the council members
can see it as well. This way the people that need to know the details
have it available but it is not public. Also, you may or may not want
to set it up so that another person, team lead or council, can reverse
the action of John.
Again, this may not be possible for Gentoo. However, it may give some
out of the Gentoo box thinking. One thing about it, the person may not
even have to appeal what John did. If it is set so that the ComRel lead
or council can see what happened and why, and they disagree, it could be
corrected fairly quickly. It all depends on just how you can set this
up on Gentoo. The private staff area may be bugzilla or something
else. On mailing lists, I'm not sure how this would work unless a email
is sent to the mailing list the person is subscribed to that says member
xyz is restricted. Maybe some automatic method that is scripted or
something.
Just throwing out ideas. I hope it makes sense. ;-) Putting it into
text isn't so easy.
Dale
:-) :-)
next prev parent reply other threads:[~2017-01-15 21:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 19:23 [gentoo-project] ComRel / disciplinary action reform proposal Michał Górny
2017-01-15 19:38 ` Raymond Jennings
2017-01-15 20:06 ` Rich Freeman
2017-01-15 20:02 ` Rich Freeman
2017-01-15 20:13 ` Kent Fredric
2017-01-15 23:05 ` M. J. Everitt
2017-01-16 17:54 ` Alec Warner
2017-01-15 21:59 ` Dale [this message]
2017-01-16 5:00 ` Dean Stephens
2017-01-15 22:55 ` M. J. Everitt
2017-01-16 0:25 ` Jorge Manuel B. S. Vicetto
2017-01-16 0:44 ` Raymond Jennings
2017-01-16 0:55 ` Rich Freeman
2017-01-16 11:16 ` Jeroen Roovers
2017-01-16 19:35 ` Jorge Manuel B. S. Vicetto
2017-01-17 17:38 ` Michał Górny
2017-01-16 4:56 ` Dean Stephens
2017-01-16 13:22 ` Paweł Hajdan, Jr.
2017-01-16 13:40 ` Kristian Fiskerstrand
2017-01-17 4:30 ` Dean Stephens
2017-01-17 4:29 ` Dean Stephens
2017-01-17 17:41 ` Michał Górny
2017-01-20 5:02 ` Dean Stephens
2017-01-16 20:57 ` William L. Thomson Jr.
2017-01-17 17:49 ` Michał Górny
2017-01-17 18:54 ` William L. Thomson Jr.
2017-01-17 19:03 ` Rich Freeman
2017-01-17 19:40 ` William L. Thomson Jr.
2017-01-17 20:20 ` Rich Freeman
2017-01-18 5:33 ` Raymond Jennings
2017-01-18 17:07 ` William L. Thomson Jr.
2017-01-17 14:38 ` Daniel Campbell
2017-01-17 15:26 ` Rich Freeman
2017-01-17 18:05 ` Michał Górny
2017-01-17 18:13 ` Kristian Fiskerstrand
2017-01-18 17:31 ` William L. Thomson Jr.
2017-01-18 18:25 ` Michał Górny
2017-01-18 18:31 ` William L. Thomson Jr.
2017-01-18 19:05 ` Rich Freeman
2017-01-18 19:13 ` William L. Thomson Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44e25740-6b88-43b9-e63b-aea93eff5caf@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox