[haiku-web] Re: Community Documentation Collaboration (Was: Add Comunity Project)
- From: Matt Madia <mattmadia@xxxxxxxxx>
- To: haiku-web@xxxxxxxxxxxxx
- Date: Tue, 14 Apr 2009 22:20:05 +0000
On Tue, Apr 14, 2009 at 6:55 PM, Jorge G. Mare <koki@xxxxxxxxxxxxx> wrote:
> Howdy,
>
>> Instead, what we have now is a couple dozen websites/blogs where
>> people are posting their own content in whatever format they like
>> because they have no other outlet for that information. That would
>> normally be fine, except many times the information I find is
>> inaccurate or misleading - often because they either copied someone
>> else's inaccurate information, or some process has changed since the
>> content was written rendering it no longer accurate.
>>
>
> I would like to have a single place with all the accurate and up-to-date
> information about Haiku as much as you do. But this is open source, and
> you cannot force people to do one way or another. No matter what you do,
> there will always be those who prefer to do their thing, and that's a
> natural part of the ecosystem. I think you just gotta learn to live with
> that. :)
>
IMO, a proper implementation will serve to discourage people from
feeling the need to rely on (or create) 3rdparty sites.
>> Anyhow, I suppose I'm really just dreaming at this point - even if we
>> set something up, as you said, people still must contribute to it. It
>> doesn't matter what software solution we choose. But I strongly
>> suggest we keep it "separate" from the main website - inter-mingling
>> of community-generated content and news articles or developer blog
>> posts for example could become very very messy.
>>
>> The page that started this discussion, containing the community links
>> on it, on the other hand, would be a perfect candidate for something
>> that is community-maintained (and moderated).
>>
>
> The Editor role is exactly for that purpose; so if you want to give
> someone the ability to such edit pages, just assign him/her the Editor
> role, and you got what you wanted. :)
>
IMO, we should have several types of editors with varying levels of power.
As a loose example (note loose as in "possible" -- my brain's a bit
fried at the moment, so just consider the concept instead of the
details) :
-Blog pages should only be editable by high-level editors. My
rationale is that to an normal web visitor, the content appears to be
from the author -- as opposed to someone who edited the page. Haiku
Inc.'s contact information. would be another example.
-There should probably be an intermediate-level... possibly to reduce
access to API documentation, event calendars, and other similar
information that typically won't change frequently.
-low-level would include the howto guides, content specifically
created on the Druki , etc
-Current editors are grandfathered in to high-level editors. All new
editors start as low-level. After they've somehow displayed their
trustworthiness, they can request to additional editing levels.
--mmadia
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List
Other related posts:
