Luca Gibelli wrote:
Hello Obantec,
http://wiki.clamav.net/index.php/UpgradeInstructions is returning server
not found.
anyone else reach it? tracert finds the IP ok but server not responding for
me!
There are some RAM issues on that server. I'm already taking care of
it.
BTW the thread about packages has gone too far, so what about starting
another flame war on a different topic? :)
I understand that many people find the current wiki difficult to use and
this results in very little contributions.
We need something that is very easy to use and actively maintained.
I really like twiki (www.twiki.org), as it has got reasonable system
requirements and it's very easy to install, even if you don't want to know
*anything* about the internals <evil g>.
Another alternative is mediawiki (on which wikipedia is based), but TBH
I think it would be an overkill for our needs.
What do you think?
Wikis tend to suffer from lack of obvious structure at the top layers
and users often fail to leave a bread crumb trail back to the
referencing layer. The result is wikis become one-way mazes. Another
roadblock to wiki success is the wiki page language is odd. Not quite
HTML, not quite text. Certainly not drag/drop. Table creation and
absolute positioning of objects is daunting.
The Wiki I implemented where I work started with 5 major (static)
categories on the front page. These were clearly separated with
whitespace from the Wiki specific links (sandbox, etc). Page management
tools are also isolated within a control box (Edit, search, etc) Within
each category are several relevant non-static sub-categories. Structured
subject matter detail is at the lowest level. Each layer has back links
to the immediate layer up, and each detail page has an immediate back
link to it's parent page.
I placed actual content everywhere I could and used consistent style and
format so that these inaugural pages would serve both as source
information and examples of how to use the tool. I spent a lot of time
re-writing submitted pages for a time to enforce this idea of style and
format and it has paid off well.
An example of a structured wiki is http://SeattleWireless.net although
it was a bit of a snarl not that many years ago. It is quite clean now.
The wiki tool you have in place is as good as any, and though new wiki
packages come along all the time there's rarely enough reason to rewrite
a legacy wiki into a new product. Which is another wiki problem - they
all seem to have their own slant on how to create wikified objects.
There is a Perl 'rosetta stone' script available that attempts to
translate wiki content to other wiki formats. It is a worth while tool.
So - my recommendation to you as a wiki master is to make some decisions
about your wiki's front page and first layer structure and direction,
create some seed topics that others can populate, add boiler plate
content, and use the one bit of cunning that drags otherwise uninvolved
people out of the woodwork: Put content in place that is harmless but
obviously wrong. You will be amazed at how motivated people are to
correct your work.
dp
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
