All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: restart wiki from scratch
Date: Tue, 27 May 2008 07:09:04 -0400	[thread overview]
Message-ID: <483BEBD0.4070707@balister.org> (raw)
In-Reply-To: <200805270944.04922.openembedded@haerwu.biz>

[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]

Marcin Juszkiewicz wrote:
> Dnia Monday 26 of May 2008, Rolf Leggewie napisał:
> 
>> the openembedded website is in rather bad shape lately.  This includes
>> the wiki which has both technical and content problems.  I suggest to
>> start anew.
>>
>> I'd like to go with mediawiki instead this time for the simple reason
>> that there are more of us who are actually familiar with this software
>> both from an admin and a user perspective.  Mediawiki was the software
>> for the OZ wiki which at its time wasn't doing too badly.
>>
>> Whatever we do, I think we should not allow the current state to exist
>> much longer.
> 
> Agree - what we have now is hard to maintain and require Drupal experience 
> which many people lack (I am one of them). Every time when I have to edit 
> current OE wiki I feel that this is too complicated and too many options 
> are present. Also there is always a problem with creating new pages as 
> current situation looks like only registered users can create new pages 
> but anyone can edit them.
> 
> Will it be MediaWiki or ikiwiki does not matter too much for me. We need 
> system which has:
> 
> - spam protection
> - protecting pages (so only admins can edit)
> - registering users (I would prefer to not have anonymous edits)
> - blocking users (spammers)
> - sane syntax for content
> 
> We have to decide which way we will go. One wiki for website and 
> documentation or website (drupal, wordpress) + documentation in wiki.

Rather than worry about what wiki software to use, shouldn't we identify 
the people who will maintain the website, then let them decide what 
software will work best for the people maintaining it? It would be 
really nice spread the workload of maintaining the OE website beyond 
just the core developers.

Philip



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2008-05-27 11:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 18:14 RFC: restart wiki from scratch Rolf Leggewie
2008-05-26 22:23 ` Koen Kooi
2008-05-26 22:46   ` Rolf Leggewie
2008-05-27  0:43 ` Cliff Brake
2008-05-27  7:44 ` Marcin Juszkiewicz
2008-05-27 11:09   ` Philip Balister [this message]
2008-06-01 16:07     ` Florian Boor
2008-06-01 22:56       ` Leon Woestenberg
2008-06-02  9:43         ` Florian Boor
2008-06-02 11:20         ` Philip Balister
2008-06-04 13:38           ` Rolf Leggewie
2008-06-04 13:52             ` Jacob Thebault-Spieker
2008-06-04 14:03               ` Rolf Leggewie
2008-06-04 14:15                 ` Jacob Thebault-Spieker
2008-06-04 14:08             ` Graeme Gregory
2008-06-04 14:22               ` Richard Purdie
2008-06-04 16:33               ` Rolf Leggewie
2008-06-05 10:58                 ` Rolf Leggewie

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=483BEBD0.4070707@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.