From: Doug Evans <dje@google.com>
To: Stan Shebs <stanshebs@earthlink.net>
Cc: gdb <gdb@sourceware.org>
Subject: Re: [GDB Wiki] Add editor privilege control
Date: Fri, 14 Feb 2014 20:58:00 -0000 [thread overview]
Message-ID: <CADPb22RtgA7BN0yac1rrneC1FSzhF9c5qKmOo0u_CYQoH8NO5Q@mail.gmail.com> (raw)
In-Reply-To: <52FE61DD.6010000@earthlink.net>
On Fri, Feb 14, 2014 at 10:35 AM, Stan Shebs <stanshebs@earthlink.net> wrote:
> On 2/13/14 7:07 PM, Joel Brobecker wrote:
>> Hello,
>>
>> I'd like to protect our wiki from spammers who regularly use it
>> for their own purposes by adding read,write,delete,revert privileges
>> to only known members of the GDB community. The model I'd like
>> to follow is the model used in the GDB Wiki. See:
>>
>> http://gcc.gnu.org/wiki/EditorGroup
>>
>> The idea is that we start with a list of people who are allowed
>> to edit. If anyone who's a legitimate contributor wants to edit
>> the wiki as well, one of the users already in the group simply adds
>> their name to the list.
>
> I considered that a while back, when learning enough about MoinMoin
> to suck in the old internals manual, but decided against it; we
> don't have very many spammers to begin with, and the antispam
> subsystem forestalls most of those, with the net effect that we've
> had to do only two manual reverts in the past three months.
>
> If we were getting multiple spams per day, limiting to registered
> members would make sense, but right now it doesn't seem necessary.
Yeah, I guess it's a question of what threshold of spam needs to be
crossed before we take this step.
I'm ok with taking the step. I don't have a strong opinion on whether
now is the time.
next prev parent reply other threads:[~2014-02-14 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 3:08 Joel Brobecker
2014-02-14 7:12 ` Eli Zaretskii
2014-02-14 7:26 ` Joel Brobecker
2014-02-14 18:35 ` Stan Shebs
2014-02-14 20:58 ` Doug Evans [this message]
2014-02-15 2:52 ` Joel Brobecker
2014-03-02 15:35 ` Frank Ch. Eigler
2014-03-03 16:12 ` Joel Brobecker
2014-04-09 12:53 ` Joel Brobecker
2014-04-09 13:12 ` Jonas Maebe
2014-04-09 13:34 ` Frank Ch. Eigler
2014-04-09 18:24 ` Joel Brobecker
2014-04-09 17:44 ` Stan Shebs
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=CADPb22RtgA7BN0yac1rrneC1FSzhF9c5qKmOo0u_CYQoH8NO5Q@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
/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