[openbeos] Re: The Wiki

On Sep 28, 2006, at 6:34 PM, Waldemar Kornewald wrote:




I agree that we still need a nice community website and haiku-os.org
should not go too deeply into that section, but IMHO the website
should not become a mozilla.com where you basically only have a
"Download Me!" link and one single product description page.


Agreed, a happy medium is necessary.


We have all been to mozilla.com+mozilla.org. This, at least in my opinion,
is what Haiku-os.org/ should be. Mozilla also has a wiki, for secondary or
peripheral content. rubyonrails.org uses a similar model.



I really don't like the distinction between .com and .org. A subdomain
would do. Even a simple "Development" section would be better than
".com vs .org", but that was probably not what you were referring to.


I wan't referring to com and org, I just meant thier content. I agree that there should be one site. haiku-os.org./wiki is good enough (or we could make a move to /sandbox or something)

The Rails wiki is the sprawling, weird, and wonderful pot of user
contributions to the documentation and the Rails knowledge sphere. If you
can't find something in the books or official guides, there's a good chance
you can find it here


. . .  Otherwise people will start modifying the wiki page although we
already have a copy of it sitting in Drupal (as it happened a few days
ago). IMHO, the wiki should primarily be used for fleshing out new
content (tutorials, documentation, whatever). When it's finished it
should get moved to the official site.


Yes, but there is some content that should not be on the drupal site that we should retain in the wiki. Especially community-oriented information. I know you are against a mozilla.com, but we realy do need a sleek and attractive starting point more than a heap of everything ( a la drupal.org).


We just need to find a good balance between end-user and developer
content. I think that it won't be too disturbing if the website is
primarily used as a tool for our developers and marketing guys. If we
make the most important end-user information easily accessible it
should work well. IMHO, the site should focus on development,
marketing, collaborations with companies, and making clear what is
"official" (so people don't have to search through tons of Haiku
distributions, for example).


Development can be VERY VERY scary to end users. We need clear separation and all unnecessary content should be retained on the wiki. Official vs. unofficial is less relevant than good vs. not-so- good content. We should mark unofficial content with a disclaimer, but no to mark our wiki with red "ALL OF THIS IS UNOFFICIAL — CAUTION!!!!!!!" That is just silly.

Everything in moderation . . . especially moderation.

P.S. (It does need to look good too)

- Austin B



Other related posts: