[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: (was "Open question...)
From:       "Friedrich W. H. Kossebau" <kossebau () kde ! org>
Date:       2008-06-27 16:21:56
Message-ID: 200806271821.57619.kossebau () kde ! org
[Download RAW message or body]

Am Freitag, 27. Juni 2008, um 17:33 Uhr, schrieb AnneWilson:
> I think that, if we want this to be taken seriously, we can't have it open
> to all users to edit.  The Mandrake user wiki that I helped start had a lot
> of very good information, but it becomes difficult to sort the wheat from
> the chaff if you get a lot of contributors.  I think it would be more
> helpful if the necessary info pages were edited by a small group - not
> discounting granting write privs to others later if required.  Part of our
> remit as acting go-betweens would be to publicise the existence of the
> pages as a resource on various mailing lists and through local LUGs.

What about an approach which would somehow resemble what seems to have worked 
for code, art, and offline docs:
* a central team coordinating structuring and all
* one or more coordinators for each module/section
* one or more maintainers of submodules/pages
* contributors with write privs
* big invititations all over the place to send in "patches", with easy to 
find, dedicated contact addresses for this which can ensure a quick reaction.
* Public lists for all discussions in the different teams and sections, so 
newcomers could come and just watch for the beginning until they feel 
confident enough to get active, too.
* And being very fast with giving write privs and thus making new people 
better bound to it "because there are in now".

In the end documentation is code, too, just executed by humans, not 
machines ;) So the development of it should not be the different, perhaps.

My 2 cents
Friedrich

-- 
Okteta - KDE Hex Editor, coming to you with KDE 4.1
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic