Shawn Walker wrote:
> On 20/11/2007, Stephen Lau <stevel at opensolaris.org> wrote:
>
> {stuff deleted}
> Well, I think the key thing is to have a generic role to describe
> these. Otherwise, you're going to end up with lots of different
> possible roles and make the application process a little more
> difficult.
>
> I'll use the (inevitable) example Ubuntu page here:
>
> http://www.ubuntu.com/community/participate
>
> They've split up getting involved into four categories:
>
> * Development
> * Documentation
> * Design
> * Support
>
> I've run a little wild with my own artistic license and come up with this
> list:
>
> * Builder ( sys admin, etc. )
>
> * Designer ( art, ui, system architecture, etc. )
>
> * Developer ( code )
>
> * Herald ( advocacy, announcements, etc. )
>
> * Scholar ( governance, documentation, web pages, translation, general
> knowledge, etc. )
>
> * Support ( qa, mailing list moderator, etc. )
>
I like this list, though I'm not sure Support and QA necessarily belong
together but I agree there is quite a lot of overlap of those roles. I
suspect real world contributions will span several of these categories
for one particular community, others will contribute in one roll across
several communities (e.g. support) and others will contribute in several
roles in several communities.
