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 1Ny4Mt-0003lQ-Vm for garchives@archives.gentoo.org; Sat, 03 Apr 2010 14:30:36 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BFFA1E066B; Sat, 3 Apr 2010 14:30:29 +0000 (UTC) Received: from mail.a3li.li (stingray.a3li.info [78.46.109.74]) by pigeon.gentoo.org (Postfix) with ESMTP id AB8FDE0BF7 for ; Sat, 3 Apr 2010 14:30:23 +0000 (UTC) Received: from localhost (stingray.a3li.info [127.0.0.1]) by mail.a3li.li (Postfix) with ESMTP id ED38312314C6 for ; Sat, 3 Apr 2010 16:30:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at a3li.li Received: from mail.a3li.li (p5081916A.dip0.t-ipconnect.de [80.129.145.106]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mail.a3li.li (Postfix) with ESMTPSA id DFDAE12314BD for ; Sat, 3 Apr 2010 16:30:19 +0200 (CEST) Date: Sat, 3 Apr 2010 16:30:10 +0200 From: Alex Legler To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [Gentoo Phoenix] an official Gentoo wiki Message-ID: <20100403163010.1897d663@mail.a3li.li> In-Reply-To: References: X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; x86_64-pc-linux-gnu) 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 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/W9xmrvCCYBe+knzbm4gBUSp"; protocol="application/pgp-signature" X-Archives-Salt: f4dae999-1c15-4826-ae95-b340541a0c56 X-Archives-Hash: 111df223ac34588ea9d09b71e0741ffe --Sig_/W9xmrvCCYBe+knzbm4gBUSp Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 3 Apr 2010 15:19:20 +0200, Ben de Groot wrote: > 1 - requirements > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > 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? >=20 > [...] >=20 > - active upstream (bug fixes, security updates) > - free open source software > - ACLs > - spam prevention measures > - attachments (to upload screenshots for example) > - feeds >=20 I propose to use MediaWiki. It fulfills all of your points above. Plus the software is proven in large scale deployments and the security track record is alright. >=20 >=20 > 2 - maintainers > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > 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'd be interested in helping out with the backend part, i.e. setting up and maintaining the Wiki software and the needed extensions, user management and support. >=20 >=20 > 3 - edit access > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > 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. >=20 Here's another idea: The German Wikipedia uses a concept called "sighted revisions". If you visit an article without logging in you will see the latest sighted revision, as an identified user you can also view the latest revision. For the editing part: Some users have the privilege to mark revisions as "sighted". In Wikipedia, you gain that privilege automatically after 300 or so edits. We could of course set that bit manually or use another threshold. If a "regular" user makes a contribution, one of the editors would go and check the changes and mark the revision as sighted. >=20 > Is there anything else we should consider before getting started? >=20 Maybe we should discuss what goals we want to reach with a Wiki. One thing is offering user-contributed documentation, of course. But do we also want a developer wiki? Or offer per-project realms in our wiki? Or $something_else? Alex --Sig_/W9xmrvCCYBe+knzbm4gBUSp Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAku3UPoACgkQk+oqhfPAZGl/7wCffAOQNeXWAv6WZ6YDnQP+Qefy c9IAn0amnQvIozwstLJ5oCR3JiiNCpWI =TNcP -----END PGP SIGNATURE----- --Sig_/W9xmrvCCYBe+knzbm4gBUSp--