[Arm-netbook] policy for wiki and mailing list

[lkcl luke]

On Mon, May 21, 2012 at 6:19 PM, Simon Kenyon <simon at koala.ie> wrote:
> On 05/19/12 01:41, lkcl luke wrote:
>> so the rules that i am forced to reluctantly set are as follows:
>>
>> 1) you put information that is useful to other people - no matter how
>> patchy, scant, incorrect, incomplete, in the wrong place, and no
>> matter how much you are "afraid it might be criticised" - on the wiki.
>>   nobody's going to criticise you - personally - for doing so.  they
>> might even improve the information.
>>
>> 2) you make an announcement on the list referring people to the page.
>>
>> 3) i will give each individual two and only two publicly-announced
>> opportunities to conform to 1) and 2).
>>
>> 4) on the 3rd violation of rules 1) and 2) i will simply unsubscribe
>> them from the list.
>
> fair enough.
> but would you consider outlining a wiki structure?

 it's sort-of coming together - i'm keeping an eye on things, every
day.  people commit stuff in the wrong place (usually preorders), and
i regularly sort things out.

> un unstructured wiki can be a bit of a nightmare.

 *lol* yes they can.  i'm keeping an eye on the situation.  i'm
already considering splitting down the mele a1000 hacking page into
its own sub-structure, for example.  i've done this before simon :)

> perhaps have two areas where unverified stuff goes in one area and
> verified in another?
>
> people could add to the unverified or "work in progress" area until such
> time as it is reasonably solid and then copy to the verified area.
>
> and for the record, i don't think my question and the hopefully ensuing
> debate belongs in the wiki. but i put it on the discussion area of the
> root page.

 :)

> and could be please move to mediawiki?

 *cackle*.  now hum don't be offended if i lump mediawiki in the same
category as "phpbb" ok?  the fact that mediawiki is php *instantly*
puts it into the "wark wark spectacular fail" box.  but let's do a
more serious analysis.

 first let's have a look at the "depends" from "apt-cache show mediawiki":

Depends: apache2 | httpd, php5, php5-mysql | php5-pgsql | php5-sqlite,
mime-support, debconf (>= 0.5) | debconf-2.0
Recommends: php5-cli
Suggests: mediawiki-math, imagemagick | php5-gd, memcached, clamav,
librsvg-bin, postgresql-contrib | mysql-server

so... php5 (which i know phil will *instantly* object to), sqlite
mysql or postgres i.e. it's database-orientated and, although phil's
running postgresql on the server that's hosting rhombus-tech.net...
you see the issue?

 ikiwiki was picked because a) it's running on phil's server, so he
gets top choice, and i know he thinks ikiwiki is the dog's bollocks
and i agree b) joey hess is a sodding genius c) this is a
programmer-related community (i.e. not a user "helpdesk" one...) d)
ikiwiki uses git as the back-end which means it can be cloned,
available offline, modified by "git commit" etc. etc. (
http://git.hands.com/?p=rhombus.git )

 so there are lots of advantages to using ikiwiki, all of which are
completely gone, for no real good benefit in return.

 l.