Lars Aronsson wrote:
Tim Starling wrote:
People underestimate the cost involved in setting
up a wiki.
Could you provide an estimate in the number of work hours? Either
more could be done in automating parts of the task, or the required
work on your behalf could be paid for with money that has to be
collected by the community (of Klingon speakers, say) before the new
wiki can be set up.
I suggest you read my post again. I'll quote it here in part.
Tim Starling wrote:
People underestimate the cost involved in setting up a
wiki. Most of
the tech support I do seems to be supporting new or small wikis.
Adding the wiki isn't hard, the bulk of the work is in authoring the
language file, mucking around with namespaces and fixing interwiki
links. From establishment to maturity, there's probably an hour of
^^^^^^^^^^^^^^^^
developer work involved.
That's just a very rough guess. Some wikis take a lot more than that. I
just finished writing a new feature specifically for the Finnish
Wikipedia which probably took 6 hours alone, although you wouldn't see
me giving that level of service to Gothic or Klingon.
The task of creating a wiki is already automated. As I explained above,
the problem is in ongoing tech support and system administration, not
creation. There are ways to reduce that too, but there's always going to
be someone who doesn't bother reading the manual.
That's why I suggested that if anyone is interested in providing ongoing
support for this wiki, they should offer themselves as a point of
contact. They should do their best to fix any problems, but *never* pass
the problem on to the rest of the community.
-- Tim Starling