[openbeos] Re: The Wiki

On 9/28/06, ar1000@xxxxxxx <ar1000@xxxxxxx> wrote: 
It was written on the wiki that it is a place for draft content only. I want
to have this clarified, expanded, and possibly tweaked. Our main website
cannot and should not be a complete compendium of data elating to Haiku. It
should not be drupal.org or even spreadfirefox.com. haiku-os.org is the
company, product, and everything starting point, it isn't "The home of Haiku
community marketing".


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.

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.

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


We do have an API, but Haiku is not *primarily* a developer-oriented
system like Rails. We target end-users and we don't need such a huge
pile of code snippets and examples (the most important ones could be
part of the Haiku Developer Book).

Don't get me wrong. I think that the wiki (or a community site?) can
be a good place for community work and short tutorials, but important
content should never be part of the wiki. It must be on our official
site. 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.

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).

Bye,
Waldemar Kornewald

Other related posts: