On Fri, 2007-08-24 at 17:47 +0800, Jeremy Malcolm wrote:
> Hi,
> 
> This is probably off-topic for this list, but of all the OOo mailing 
> lists it was closest I could find.
> 
> I'm writing a PhD thesis which contains a section analysing various open 
> source projects, including OpenOffice.org.  I include references to case 
> studies about the other projects, including Apache and Mozilla, but I 
> haven't been able to find one for OpenOffice.org.
> 
> The kind of study I'm interested in is one which looks not at the 
> *software* but the *community*: how it is structured, how it is 
> governed, its strengths and weaknesses, that sort of thing.
> 
> Does anyone know of any paper, article, or even just Web site, that 
> analyses the OOo development community in these terms?

http://www.openoffice.org/dev_docs/guidelines.html

The link above gives general structural info.

If you went through the archives of the discussion on this list you
would get quite a lot of empirical data on how the community operates in
terms of the views of volunteers in the marketing project. Also look at
the Community conference archives. Don't forget there are many native
language projects that are fairly autonomous so might be quite different
in terms of community culture from the main project. 

I don't know of any single pulling together of all this - maybe someone
needs to do a PhD on it :-)

You could of course pick a random sample of the project members on the
web site and ask their views.

A key difference with the OOo project and other large OSS projects is
the dominant role of Sun, particularly in the engineering effort and
overall community management.

Hope this helps
-- 
New QCA Accredited IT Qualifications
www.theINGOTs.org

You have received this email from the following company: The Learning
Machine Limited, Reg Office, 36 Ashby Road, Tamworth, Staffordshire, B79
8AQ. Reg No: 05560797, Registered in England and Wales. 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to