From: "Jan Krüger" <jk@jk.gs>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Jakub Narebski <jnareb@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Avery Pennarun <apenwarr@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: Proposal for new Git Wiki admin
Date: Thu, 12 Aug 2010 16:56:47 +0200 [thread overview]
Message-ID: <20100812165647.38ee2809@jk.gs> (raw)
In-Reply-To: <AANLkTimQsNj-3M=y7Dop4brB8U-8vVPqgD0+zBX5R6FG@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> wrote:
> IMO having more than one admin is only part o the solution, see:
> https://git.wiki.kernel.org/index.php/WikiIdeas
Here are my comments on that. For the sake of archive-friendliness, I'm
referring to this version of it:
https://git.wiki.kernel.org/index.php?title=WikiIdeas&oldid=8996
(Why am I commenting here instead of on the wiki? Because I think there
are few things worse than a wiki for discussing something.)
| Currently there's only one admin (Johannes Schindelin), it would be
| healthy to have more than one.
I agree. Few sites work with one admin; not least because most sites
are too much work for one single person to handle.
| Up to now, good faithed users have been blocked immediately, and
| permanently, without a warning. Instead of doing that, a policy like
| wikipedia's one should be followed:
I'd like to point out that this drastically increases the
administration effort. For example, issued warnings have to be tracked.
Also, this is serious overhead for obvious spammers, and different
people will have different perspectives on what constitutes an obvious
spammer. To the best of anyone's knowledge, only one false positive has
ever occurred until now. I think this approach is overkill. I would
suggest, if technically possible, automatically showing banned users a
notice that asks them to contact admins via some channel or another if
they believe that they have been wrongly blocked.
| Some people might have been wrongly blocked. By changing the blocking
| policy the old blocks might not apply and warnings should be issued instead.
Same reasoning. Also, the deletion logs look very much like only
obvious spammers got blocked.
| Allow users to see deleted pages
| This would allow transparency into the action of the admins.
I don't oppose that, but it raises technical issues. Deleted pages
should not be indexed by search engines, because doing so would defeat
the purpose of removing spammy links. I don't know whether MediaWiki
implements that; I do know that it tells robots not to index old
versions of pages.
| Up to now, good faithed users have been blocked immediately, and
| permanently, without a warning. Instead of doing that, a policy like
| wikipedia's one should be followed:
Yes, but why use a wiki for communication if you can simply use e-mail
instead? To me, all this "using wiki pages for communication and
discussions" is a classic case of "when you have a hammer"...
Also, the proposal about patrol groups seems to be about solving the
same problem, though I don't know how well it works for dealing with
problematic edits in real time. Okay, I guess we'd need a *lot* more
admins for that anyway.
All in all, I think it would be completely sufficient to find a way to
let users help with reporting spam, and to add a couple of admins...
and perhaps notify users when blocking them. I don't think anything
else is necessary or useful.
> > [...] Personally, I don't think
> > you should work with Johannes, atleast in the state in which you're
> > in right now. Please disagree only if you feel that Jakub or I will
> > do a bad job.
>
> It's not Johannes' wiki; it's the community's. And I'm certain that I
> can work just fine with Jakub as I've done it in the past.
Nobody claimed that you wouldn't be able to work with Jakub, there was
only doubt that you might have difficulty working with Johannes (in a
way that leaves both of you in a healthy state of mind).
Also, for the record, I'm fine with Jakub and Ram doing the job. I
would volunteer myself for additional help but I don't really care
about it very strongly, and three people are probably enough for now
anyway.
(As a public service, I have cut away the rest of what I was going to
write. The discussion is long enough as it is already.)
-Jan
next prev parent reply other threads:[~2010-08-12 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 16:26 Proposal for new Git Wiki admin Ramkumar Ramachandra
2010-08-10 17:03 ` Felipe Contreras
2010-08-10 22:06 ` Jakub Narebski
2010-08-10 22:19 ` Sverre Rabbelier
2010-08-10 22:39 ` Felipe Contreras
2010-08-11 5:00 ` Ramkumar Ramachandra
2010-08-11 6:55 ` Michael J Gruber
2010-08-11 12:06 ` Felipe Contreras
2010-08-11 12:51 ` Miles Bader
2010-08-11 13:46 ` Ramkumar Ramachandra
2010-08-11 14:24 ` Ramkumar Ramachandra
2010-08-20 11:12 ` Felipe Contreras
2010-08-20 12:28 ` Ramkumar Ramachandra
2010-08-21 12:26 ` Felipe Contreras
2010-08-11 14:49 ` Felipe Contreras
2010-08-11 15:34 ` Felipe Contreras
2010-08-12 14:56 ` Jan Krüger [this message]
2010-08-12 16:15 ` Felipe Contreras
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=20100812165647.38ee2809@jk.gs \
--to=jk@jk.gs \
--cc=Johannes.Schindelin@gmx.de \
--cc=apenwarr@gmail.com \
--cc=artagnon@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=srabbelier@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).