Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index

Hi Benjamin,

great collection :-)

Am Dienstag, den 05.10.2010, 07:38 -0400 schrieb Benjamin Horst:
I agree that overthinking and overburdening a wiki with rigid process is harmful, but some 
upfront organization and planning is still necessary.

Yes, rigid processes are harmful for a wiki - even if they want to
achieve something good. But as you already point out, I'd like to guide
some people initially, to not get lost. If one doesn't find information,
then it is like nobody ever published it :-\

Some major sections that could be defined in the wiki:

- Site Home (why not use the wiki for the main part of the site, including the homepage and 
download page?)
- Documentation (bring this dynamic and enthusiastic group back home to the main site)
- Development (public planning and release schedule)
- Community Council (private section, if desired)
- News

Just a question: Do you expect news to be in the Wiki, or on the rather
website? Or both?

- Events
- Marketing and Advocacy
- Design and Artwork 
- Teams and Projects

By the way, I really like the idea of Special Interest Groups at Fedora.

- More?

Most presumably yes :-) So thanks for the great start!

Adding to Christoph's list of other project wikis:

* Mozilla

* Ubuntu

Interesting, Ubuntu seems to separate the official Documentation (Wiki)
and the "do the work" wiki.

* Foswiki

Mmh, din't knew that. Thanks!

Benjamin, thanks for the comments ... most appreciated!



just my 2 Cents:

On Monday 04 October 2010 23:54, Christoph Noack wrote:

Step forward, and share your thoughts,
too, please! But how to get started ... I mean ... without a wiki to
document the statements.

A wiki is a wiki is a wiki - so just set one up and let it 
self-organize. Do not define too much contstraints in advance. 

Do not define too special rules in beforehead but rather let them 

People in free projects tend to be very constructive, so let them do 
their work.

The final decision which wiki engine to take should be made by the 
prospective core admins (as they will have to handle it). A bad engine 
with a good admin is far better than a good engine with a poor admin.

Rules should be made only _after_ a certain period of experience. And 
they should be defined by the users of the wiki. 

All that said, I'd prefere to have a wiki farm for different languages 
and not one multilanguage wiki - just to enhance usability (mainly the 
search function). 

To unsubscribe, send an empty e-mail to
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at

Benjamin Horst
646-464-2314 (Eastern)

To unsubscribe, send an empty e-mail to
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.