From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: [GDB Wiki] Add editor privilege control
Date: Fri, 14 Feb 2014 07:12:00 -0000 [thread overview]
Message-ID: <83ppmqcgmx.fsf@gnu.org> (raw)
In-Reply-To: <20140214030759.GC5485@adacore.com>
> Date: Fri, 14 Feb 2014 07:07:59 +0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> 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.
Why does it make sense to have a wiki that doesn't behave like a wiki,
i.e. is not a community-provided content? IOW, how is what you
propose different from having this stuff on the GDB project web pages,
which are editable by only a few select people?
next prev parent reply other threads:[~2014-02-14 7:12 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 [this message]
2014-02-14 7:26 ` Joel Brobecker
2014-02-14 18:35 ` Stan Shebs
2014-02-14 20:58 ` Doug Evans
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=83ppmqcgmx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.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