From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: "Václav Zeman" <vhaisman@gmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
overseers@gcc.gnu.org
Subject: Re: Vandalised wiki page
Date: Fri, 23 Aug 2013 15:06:00 -0000 [thread overview]
Message-ID: <CAH6eHdQAXdNyTFqUjVEkiN6djB7fqG2U6qmFCm6DPS_NAY_WbA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRZAoA1914q16k41A=DZYDJtH7nqPf2e_eRRz62zgNQvA@mail.gmail.com>
On 23 August 2013 16:04, Jonathan Wakely wrote:
> On 23 August 2013 15:44, Frank Ch. Eigler wrote:
>> Hi -
>>
>>> > Looking at http://gcc.gnu.org/wiki/RecentChanges shows that the GCC wiki
>>> > is being spammed a lot. Somebody should employ some kind of spam protection.
>>
>> Several other sourceware-hosted moin wikis have adopted a group-ACL-based
>> protection, which has eliminated the problem. This involves maintaining
>> a special wiki page that lists approved editors (and is editable by those
>> editors). If you're interested in trying this, please send me an initial
>> list of editor WikiNames.
>
> I suggest starting with these known-good names who've been recently active:
>
> JanusWeil
> DodjiSeketeli
> IanLanceTaylor
> TobiasBurnus
> JonathanWakely
> ManuelLópezIbáñez
(Assuming we want to go down the ACL route.)
> Is there an easy way to revert a spam change to a page? I don't see one.
Doh, found it in the "more actions" dropdown.
next prev parent reply other threads:[~2013-08-23 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52168CDC.2070808@warwick.ac.uk>
[not found] ` <521708D8.2070902@gmail.com>
2013-08-23 9:29 ` Jonathan Wakely
2013-08-23 14:38 ` Janus Weil
2013-08-23 14:44 ` Frank Ch. Eigler
2013-08-23 15:05 ` Jonathan Wakely
2013-08-23 15:06 ` Jonathan Wakely [this message]
2013-08-23 15:25 ` Frank Ch. Eigler
2013-08-23 15:59 ` Jonathan Wakely
2013-08-25 16:24 ` David Brown
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=CAH6eHdQAXdNyTFqUjVEkiN6djB7fqG2U6qmFCm6DPS_NAY_WbA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.gnu.org \
--cc=vhaisman@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 read-only IMAP folder(s) and NNTP newsgroup(s).