From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: Wiki Migration Pending
Date: Fri, 18 Apr 2008 01:38:39 +0000 [thread overview]
Message-ID: <20080418013839.GC20637@parisc-linux.org> (raw)
In-Reply-To: <e5a3e9ac0804171429v402e5bbbqc94749b11d192bc2@mail.gmail.com>
On Thu, Apr 17, 2008 at 02:29:22PM -0700, Chris Miller wrote:
> I am thinking about not installing the wiki on the VPS system, since
> it seems to do a good job of collecting spam. I will, however, have a
> tool called GForge(1) on the site. I will be using it to track my own
> projects, though kernel janitors are perfectly welcome to use it if
> you want. It has a built-in wiki, though it also has a tracking
> system (for bug reports and to-do list items), which I would think
> would make it a better tool for the job. Unfortunately, I haven't
> been able to do hardly any kernel hacking, so I'm not very qualified
> at all to make that kind of a decision.
>
> If you're really adverse to the idea of using something other than
> MediaWiki I can try to install it on the new VPS system, that's no
> problem either. It's just a bit harder for me, since this is the
> first time I've really had to configure all this software from the
> ground up.
Since there's a mediawiki on kernel.org now, perhaps we should migrate
to using that instead. Any thoughts?
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-04-18 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 21:29 Wiki Migration Pending Chris Miller
2008-04-18 1:38 ` Matthew Wilcox [this message]
2008-04-18 3:20 ` Chris Miller
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=20080418013839.GC20637@parisc-linux.org \
--to=matthew@wil.cx \
--cc=kernel-janitors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.