From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: [GDB Wiki] Add editor privilege control
Date: Fri, 14 Feb 2014 07:26:00 -0000 [thread overview]
Message-ID: <20140214072628.GN30945@adacore.com> (raw)
In-Reply-To: <83ppmqcgmx.fsf@gnu.org>
> 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?
It would be editable by anybody, they would just have to show
that they are a real person without spamming intentions. The way
it would work is that anyone already in the edit group can add
anyone else by just editing a wiki page and adding the new user's
ID to the list, thereby vouching for them. It's still community-fed,
but just a little more controlled to make sure that only genuine
modifications are made.
As an example: I needed to make a change in the GCC wiki,
found that I cannot edit. Saw that there was a note about that
pointing me to the EditorGroup page. It told me that anyone
on that list can add someone else. So I contacted a couple of
people on the list I knew and they added me pronto.
If you haven't done so, I invite you to check out GCC's EditorGroup
page:
http://gcc.gnu.org/wiki/EditorGroup
It really shows how simple it is to maintain that list and add
new people. The list currently has 52 people, and no question
was ever asked when I got added.
I would also welcome anyone to participate in the maintenance
of the GDB web pages as well. I even recently wrote a small
wiki page explaining how to make updates to it.
https://sourceware.org/gdb/wiki/GDBWebsiteUpdateProcedure
--
Joel
next prev parent reply other threads:[~2014-02-14 7:26 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 [this message]
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=20140214072628.GN30945@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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