[openbeos] Re: The Wiki

On 9/30/06, Jorge G. Mare (a.k.a. Koki) <koki@xxxxxxxxxxxxxx> wrote: 
I think there should be maintainers for each area that oversee the
informational pages and works/coordinates with the contributors to make
sure the content is accurate and up to date. The "go change it if you
don't like it" method will just open the door to constant changes with
no end in sight...


This may be the right method for end-user content, but I developers
should be able to just change stuff in RFCs, "implementation details",
and tutorials. You can't apply the same method to both. And I think
it's important for productivity to have incomplete development
content, too.

Also, don't think comments are necessary for anything other than RFCs
and blog entries.


If we don't need comments for news articles we should use the "page"
content type for end-user content, from now on. Developers should
stick with "article".

> With "our official documentation system" I didn't mean that it's the
> "official documentation". The documentation system should have two
> sections for "finished content" and "draft content". The old BeOS
> documentation could stay in the draft section and slowly get
> transformed into real documentation.

And what are the benefits of having draft content in the website? 

I was talking about the wiki.

(I do think that putting that disclaimer
on top of every RFC is redundant and a waste of space).


Others were saying that without the disclaimer they had the impression
that the RFCs will actually be implemented in future Haiku releases.

It is the other
articles that are not finished that I am referring to.


Our website is obviously not finished, yet. Would you like to become
responsible for finishing at least the articles which are
marcom-related?

Bye,
Waldemar Kornewald

Other related posts: