From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Moving project pages to wiki.gentoo.org
Date: Sun, 16 Jun 2013 19:40:50 +0000 [thread overview]
Message-ID: <robbat2-20130616T193956-925579588Z@orbis-terrarum.net> (raw)
In-Reply-To: <51BD991C.4040500@gentoo.org>
On Sun, Jun 16, 2013 at 12:53:16PM +0200, Alex Legler wrote:
> > 2. How will the staffing needs page be updated after dropping gorg?
> You create a subpage for each staffing need, filling in information
> using a form. Semantic magic aggregates these, and you'll get a template
> to include for your project page to list the ones for your project
> specifically.
This should probably also feed back to the qa-reports site.
> > 3. How secure is the wiki? Do we have regular backups and security
> > updates procedures in place? I know you're member of the security team
> > and infra team is doing its job well, but I just wanted to check.
> > Dynamic web applications arguably have bigger attack surface than
> > effectively a bunch of static files only editable after you gain server
> > access.
> It's part of the usual infra backup, and I follow upstream release
> announcements and update accordingly.
A somewhat crazy idea, but could the git-mediawiki extension be used to
create a downloadable archive of every revision as well?
--
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail : robbat2@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
next prev parent reply other threads:[~2013-06-16 19:40 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 14:22 [gentoo-dev] RFC: Moving project pages to wiki.gentoo.org Alex Legler
2013-06-09 15:44 ` Ulrich Mueller
2013-06-09 16:01 ` Alex Legler
2013-06-09 15:57 ` Andreas K. Huettel
2013-06-09 16:03 ` Alex Legler
2013-06-10 6:48 ` Dirkjan Ochtman
2013-06-10 12:36 ` Sergey Popov
2013-06-10 13:29 ` Diego Elio Pettenò
2013-06-10 14:31 ` Michał Górny
2013-06-10 15:15 ` Alex Legler
2013-06-10 15:47 ` Hans de Graaff
2013-06-10 20:38 ` Ultrabug
2013-06-11 10:49 ` Sergey Popov
2013-06-10 23:06 ` Jason A. Donenfeld
2013-06-11 10:20 ` Sven Vermeulen
2013-06-11 11:05 ` Theo Chatzimichos
2013-06-11 12:15 ` Alex Legler
2013-06-13 16:33 ` Sven Vermeulen
2013-06-16 0:28 ` [gentoo-dev] [1/3] Automatic *XML->Wiki wiki.gentoo.org Robin H. Johnson
2013-06-26 13:54 ` Alex Legler
2013-07-08 20:02 ` Sven Vermeulen
2013-07-09 15:46 ` [gentoo-dev] " Steven J. Long
[not found] ` <51DB41CA.8090707@yahoo.ca>
2013-07-09 23:53 ` [gentoo-dev] " Alex Xu
2013-07-10 0:29 ` Alex Legler
2013-07-10 0:45 ` Alex Xu
2013-07-10 6:58 ` Tom Wijsman
2013-07-10 9:10 ` Michael Weber
2013-07-10 9:26 ` Tom Wijsman
2013-07-10 8:23 ` Sven Vermeulen
2013-06-16 1:21 ` [gentoo-dev] [2&3]/3 API & files Robin H. Johnson
2013-06-16 12:08 ` Alex Legler
2013-06-16 19:44 ` Robin H. Johnson
2013-06-16 22:12 ` Alex Legler
2013-06-16 22:56 ` Alex Xu
2013-06-18 18:06 ` Robin H. Johnson
2013-06-22 9:20 ` Markos Chandras
2013-06-22 10:14 ` Alex Legler
2013-06-16 4:01 ` [gentoo-dev] RFC: Moving project pages to wiki.gentoo.org "Paweł Hajdan, Jr."
2013-06-16 9:01 ` Tom Wijsman
2013-06-16 10:53 ` Alex Legler
2013-06-16 19:40 ` Robin H. Johnson [this message]
2013-06-16 20:12 ` Kent Fredric
2013-06-16 20:36 ` Andreas K. Huettel
2013-06-16 23:17 ` Alex Xu
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=robbat2-20130616T193956-925579588Z@orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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