What should a community manager do?
duvelle.jones at gmail.com
Sat Oct 11 14:35:37 CEST 2008
I think that we might be at a point where this should be our first concern.
How to lift the tide to all boats in the Moko pool. Management of the
community is a great start, since what we currently have would be best
described as disarray.
My only concern here is that there seems to be a separation between the
developer and the user... that in the community both seem to have there
little corner. Maybe I am reading that wrong, but if I am not... I am not
too sure that it's something that I would agree with, if only because the
current make-up of OpenMoko, Developer and user are one in the same.
Rod Whitby wrote:
> I'll answer this from the point of view of a "development community"
> manager. I think you already have a fine "end-user community" manager
> in Michael Shiloh.
> A development community manager must have the number one priority of
> embracing all the disparate developers working on the Openmoko platform,
> and being responsible for "bringing them into the fold":
> I say all this based on the experience of running the nslu2-linux.org
> project for the last four years, and building a community of over 100
> developers and over 10 thousand users all working in common repositories
> producing packages and images for four different distributions (targeted
> to four different use cases) using the same top-level build system and
> ending up in common official feeds on a single official download site.
> See the following documents for more details:
> -- Rod Whitby
> (No, I'm not looking for the job)
> Openmoko community mailing list
> community at lists.openmoko.org
View this message in context: http://n2.nabble.com/What-should-a-community-manager-do--tp1318997p1319758.html
Sent from the Openmoko Community mailing list archive at Nabble.com.
More information about the community