public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>,
	Frysk Hackers <frysk@sourceware.org>,
	        "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Frysk Wiki
Date: Wed, 05 Mar 2008 17:39:00 -0000	[thread overview]
Message-ID: <47CEDA92.2080908@redhat.com> (raw)
In-Reply-To: <47CED88C.9010907@redhat.com>

Sami Wagiaalla wrote:
>
> I have been looking into this a little bit. What we need is a content 
> management system with perhaps a wiki component. Asking around I was 
> given the following suggestions:
>
> - Joomla
> - Drupal
> - MediaWiki
> - whatever gnome and fedoraproject use cant remember
>
> I personally think Joomla is our best option

Right, but as we as a project do not manage sourceware.org there is a 
limiting factor there. Frank offered to get the moinmoin wiki going and 
because there is an existing project using it (systemap), it might be 
easier that way.

In any case, I don't want us to spend Frank's goodwill onto something 
more "expensive" without asking him first ;) My hunch would be settling 
on an installed system/wiki already there, so the overseers do not have 
to play the security upgrade game.

However, from a pragmatic point of view: I'd like a wiki. How that is 
parceled and delivered is of no interest to me. If it is part of a CMS, 
so be it. Or just a dedicated wiki , so be it.

Regards

Phil

  reply	other threads:[~2008-03-05 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  9:27 Phil Muldoon
2008-03-05 10:38 ` Mark Wielaard
2008-03-05 17:30   ` Sami Wagiaalla
2008-03-05 17:39     ` Phil Muldoon [this message]
2008-03-06  9:05     ` Mark Wielaard
2008-03-18 14:34       ` Phil Muldoon
2008-03-19  9:05         ` Mark Wielaard

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=47CEDA92.2080908@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=fche@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=mark@klomp.org \
    --cc=swagiaal@redhat.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).