do at this point is keep an eye... see that
things don't go south.
--
View this message in context:
http://n2.nabble.com/What-should-a-community-manager-do--tp1318997p1321791.html
Sent from the Openmoko Community mailing list archive at Nabble.com
Rod,
It seems that access was granted sometime between then and now
oh great, I'm happy to hear that.
Maybe we don't talk about it enough publicly: We have an 'admin trac'
issue tracker, that _EVERYBODY_ can use to send requests to the
Openmoko admins.
This is a public resource, same as
Wolfgang Spraul wrote:
Rod,
It seems that access was granted sometime between then and now
oh great, I'm happy to hear that.
Maybe we don't talk about it enough publicly: We have an 'admin trac'
issue tracker, that _EVERYBODY_ can use to send requests to the
Openmoko admins.
This is
Rod,
BTW, I can show you guys how to set up Trac so that you can issue all
the developers an SSL client certificate (which you can use in a lot
of
places instead of username and password) and it automatically logs
them
into trac using their email address so they automatically get emails
On Saturday 11 October 2008, 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.
Thank you Rod, you posted all the ideas (and more) about the OM dev
process, which were
Excellent point from Rod!
I'm sure actions like this would boost the development to a completely
new level! And having better software and rapid development means more
satisfied users in the community as well, as soon as some minimal
level (I'd say it's working phone in this case :) is reached.
Blimey! Rod makes some GREAT points here - this email should probably
be a standard reference document for OSS projects. When I got to the
bottom read his credentials they seemed entirely congruent with his
insights.
I just want to add one little thing, and that's DON'T OVERLOOK THE
/community
--
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.
___
Openmoko community mailing list
community
Excellent posting!! This is a very good job description for
someone like a community manager.
Norbert
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
On Sat, Oct 11, 2008 at 3:35 PM, Duv [EMAIL PROTECTED] wrote:
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
On Sat, 2008-10-11 at 05:35 -0700, Duv wrote:
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
Hi there,
I fully agree with Rod! I would even go so far as to consider having a
automatic registration system to get access to GIT, SVN, Wiki and all
mailing lists in order to capture even the smallest contribution,
regardless of if it is developer coding or correction of spelling
errors in the
Rod Whitby wrote:
(Wolfgang told the Openmoko admins
to give me svn and git access on the 22 Sept, and nothing has happened yet).
I want to make a public retraction and apology on this point. It seems
that access was granted sometime between then and now, but either I
wasn't informed of that
Risto H. Kurppa wrote:
I also want to remind that community is not limited to the developers.
It should also include all users that can be used to create marketing
events and material, generate new ideas and test software and report
bugs.
I like to think of the distinction between users and
Risto H. Kurppa wrote:
On Sat, Oct 11, 2008 at 3:35 PM, Duv [EMAIL PROTECTED] wrote:
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...
On Sun, 12 Oct 2008 07:35:12 +1030, Rod Whitby [EMAIL PROTECTED] wrote:
Anyone who has the mindset of this is broken, how can I fix it? is a
developer.
Anyone who has the mindset of this is broken, I expect it to be fixed
by someone else right now! is a user.
The community will have both
Rod Whitby wrote:
Risto H. Kurppa wrote:
On Sat, Oct 11, 2008 at 3:35 PM, Duv [EMAIL PROTECTED] wrote:
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,
Lorn Potter wrote:
Rod Whitby wrote:
I'm sorry, but I don't believe one single community manager can cross
the divide between the developer and user mindsets that I spoke
about in my reply to your earlier post.
I disagree. I have been doing exactly that for the last 5 years. Trying
to
Joel Newkirk wrote:
On Sun, 12 Oct 2008 07:35:12 +1030, Rod Whitby [EMAIL PROTECTED] wrote:
Anyone who has the mindset of this is broken, how can I fix it? is a
developer.
Anyone who has the mindset of this is broken, I expect it to be fixed
by someone else right now! is a user.
The
On Sun, 12 Oct 2008 13:18:31 +1030, Rod Whitby [EMAIL PROTECTED] wrote:
Joel Newkirk wrote:
WRT your final point, we already have the 'Support' mailinglist - my
impression is that the intent of that list (not necessarily the actual
usage though) is as a place for the 'user' to go when seeking
Steve Mosher said:
Sean asked me what I thought of having a community manager.
...
I have my ideas about what a community manager would do to organize
and mobilize, But before I put those ideas down, I'd like to throw it
open to the community.
Question: what functions do you see a community
21 matches
Mail list logo
