From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ny4t9-0008QH-Dg for garchives@archives.gentoo.org; Sat, 03 Apr 2010 15:03:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2E1C3E0BFB; Sat, 3 Apr 2010 15:03:54 +0000 (UTC) Received: from themis.wsgurus.com (themis.wsgurus.com [65.98.70.26]) by pigeon.gentoo.org (Postfix) with ESMTP id 42B0AE0B47 for ; Sat, 3 Apr 2010 15:03:49 +0000 (UTC) Received: from 75-132-6-220.dhcp.stls.mo.charter.com ([75.132.6.220] helo=[192.168.1.100]) by themis.wsgurus.com with esmtpa (Exim 4.69) (envelope-from ) id 1Ny4su-0000y7-NO for gentoo-dev@lists.gentoo.org; Sat, 03 Apr 2010 11:03:16 -0400 Message-ID: <4BB758C3.4040406@gentoo.org> Date: Sat, 03 Apr 2010 10:03:31 -0500 From: Nathan Zachary User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100322 Thunderbird/3.0.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [Gentoo Phoenix] an official Gentoo wiki References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------000206090505080503010905" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - themis.wsgurus.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gentoo.org X-Source: X-Source-Args: X-Source-Dir: X-Archives-Salt: c257213b-6e0d-48fb-a3b6-7b41ecbd20cc X-Archives-Hash: ab247178ed613e9417fe687e250958e8 This is a multi-part message in MIME format. --------------000206090505080503010905 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 03/04/10 08:40, Dror Levin wrote: > On Sat, Apr 3, 2010 at 16:19, Ben de Groot wrote: > >> 1 - requirements >> ================ >> >> In order to choose the best possible wiki implementation, we need to >> know our requirements. So what features do you think are essential or >> good to have? What syntax would we prefer to use? >> >> I myself am a big fan of reStructuredText, which is quite simple, >> easy to pick up, highly readable, and has a good featureset. Plus, it >> is also reusable in other contexts (it is for example widely used in >> documentation of Python libraries). MediaWiki, MoinMoin and Trac have >> support for rst. >> >> Some others: >> >> - active upstream (bug fixes, security updates) >> - free open source software >> - ACLs >> - spam prevention measures >> - attachments (to upload screenshots for example) >> - feeds >> > There is currently a wiki for gentoo at gentoo-wiki.com, which is > running MediaWiki, so it would be easiest to transfer the content if > we were to run the same software. Now, this doesn't mean we should be > limited by their actions, but it seems to me like the best choice for > other reasons as well. Its syntax is probably the most well known, > thanks to Wikipedia. Its upstream is active, it apparently scales and > performs pretty well, it's GPL, supports translations/localization, > feeds, attachments, etc. > I'm sure many other alternatives are as qualified, so this is most > likely a personal preference issue. As such, lets just agree on > something that works and is widespread and go with that and avoid all > the bikeshedding. > > >> 2 - maintainers >> =============== >> >> Who is volunteering for maintaining the wiki? We need editors and >> moderators, people who look out for quality control and take care of >> spam removal. So let's get together a team. I'm sure if we ask on the >> forums we'll get some users interested as well. >> > I volunteer. Spam shouldn't be that much of an issue if editing is > restricted to registered users, but it is a good idea to have a team > of moderators similar to the one that exists for the forums (of course > users can take part of it as well as developers). > > >> 3 - edit access >> =============== >> >> Do we keep to the original "free for all" model, with all the spam >> that includes, or do we go with registered users only? I think the >> latter is the smarter option. I also think we will want to mark >> certain pages "official" and lock down editing rights. >> > IMO it's best if only registered users can edit (but registering > should be easy, no bugs to file or anything, just sign up and use > immediately). This will probably prevent most kinds of spam and allow > for much better tracking of editing and history, allow for banning, > etc. without closing the wiki up too much. > Also, from what I could tell, this is how others are managing their > wiki as well (Arch and Amarok, for example). > > Dror Levin > > I would enjoy working on a wiki as well as the fora, so I'm volunteering as well. --Nathan Zachary --------------000206090505080503010905 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit On 03/04/10 08:40, Dror Levin wrote: 
On Sat, Apr 3, 2010 at 16:19, Ben de Groot <yngwin@gentoo.org> wrote:
  
1 - requirements
================

In order to choose the best possible wiki implementation, we need to
know our requirements. So what features do you think are essential or
good to have? What syntax would we prefer to use?

I myself am a big fan of reStructuredText, which is quite simple,
easy to pick up, highly readable, and has a good featureset. Plus, it
is also reusable in other contexts (it is for example widely used in
documentation of Python libraries). MediaWiki, MoinMoin and Trac have
support for rst.

Some others:

- active upstream (bug fixes, security updates)
- free open source software
- ACLs
- spam prevention measures
- attachments (to upload screenshots for example)
- feeds
    
There is currently a wiki for gentoo at gentoo-wiki.com, which is
running MediaWiki, so it would be easiest to transfer the content if
we were to run the same software. Now, this doesn't mean we should be
limited by their actions, but it seems to me like the best choice for
other reasons as well. Its syntax is probably the most well known,
thanks to Wikipedia. Its upstream is active, it apparently scales and
performs pretty well, it's GPL, supports translations/localization,
feeds, attachments, etc.
I'm sure many other alternatives are as qualified, so this is most
likely a personal preference issue. As such, lets just agree on
something that works and is widespread and go with that and avoid all
the bikeshedding.

  
2 - maintainers
===============

Who is volunteering for maintaining the wiki? We need editors and
moderators, people who look out for quality control and take care of
spam removal. So let's get together a team. I'm sure if we ask on the
forums we'll get some users interested as well.
    
I volunteer. Spam shouldn't be that much of an issue if editing is
restricted to registered users, but it is a good idea to have a team
of moderators similar to the one that exists for the forums (of course
users can take part of it as well as developers).

  
3 - edit access
===============

Do we keep to the original "free for all" model, with all the spam
that includes, or do we go with registered users only? I think the
latter is the smarter option. I also think we will want to mark
certain pages "official" and lock down editing rights.
    
IMO it's best if only registered users can edit (but registering
should be easy, no bugs to file or anything, just sign up and use
immediately). This will probably prevent most kinds of spam and allow
for much better tracking of editing and history, allow for banning,
etc. without closing the wiki up too much.
Also, from what I could tell, this is how others are managing their
wiki as well (Arch and Amarok, for example).

Dror Levin
I would enjoy working on a wiki as well as the fora, so I'm volunteering as well.

--Nathan Zachary
 --------------000206090505080503010905--