On 02/02/2016 09:29 AM, Bryan Richter wrote:
> On Tue, Feb 02, 2016 at 09:00:10AM -0600, Jason Harrer wrote:
>>
>> 2) As I'm reviewing and investigating more about what OpenProject
>> can do and how we can organize things, I think it would be
>> beneficial to take the time to try and establish the groups and
>> roles and figuring out the workflow for OpenProject.
>>
>> ... I'm going to jot down my thoughts here for discussion purposes.
>> ... Here are the thoughts on circles and who I think the leads would
>> be:
>>
>> *Circles*
>> Design (Robert)
>> Development (Bryan)
>> Legal (?)
>> Project Management (me)
>> Public Relations/Community (William)  (not sure if these should be two
>> different circles)
>> Requirements (Aaron)
> 
> This is valuable. It will always be a tradeoff between synchronization
> and bureaucracy, but I think clarifying these roles will just give us
> some peace of mind even if we continue to wear all the hats, all the
> time.
> 
> Here's some thoughts I have on the matter.
> 
> 1. What is "design"? Is it visual design or product design? Those two
> are related, but visual design is also related to development. I think
> it might be good to keep all three distinct. Robert, you probably have
> more experience here. Any feedback?
> 

Design is larger scope. It's one element of the overall product. It is
part of product design and everything. We can split up things to specify
these roles and tasks.

The whole Holacracy concept for governance involves doing the work of
specifying the precise responsibilities and authorities of each area. We
need to finalize these things.

> 2. I am unclear on William's role. I don't think "community manager"
> is the right title. That is usually a euphemism for "public
> relations", which is (obviously) less about actual relations and more
> about image and marketing.
> 

William went with "Community Director" and please just drop your
preconceptions about this. It is not anything like PR. In fact, in the
wide FLO world, the term "Community Manager" is 95% of the time used to
refer to the person who does all the stuff with the part of some
commercial FLO project that isn't the paying customers. E.g. the Puppet
Labs Community Manager handles user forums, contacts, outreach,
volunteers, and basically everything involved in keeping the healthy
"Open Source" community going and participating and helping the project,
whereas other stuff at Puppet focuses on their Enterprise customers.
That is the prototypical "Community Manager" and even Jono Bacon's
entire book "The Art of Community" is about this whole issue and his
position when he was Ubuntu "Community Manager" which was not general
public PR and almost entirely about engaging with all the Ubuntu
volunteers around the world.


> Wikipedia says that community managers have responibilities like
> social media management, marketing, PR, and customer support. However,
> Aaron told me that he's also the one in charge of making relationships
> with potential client projects. That does not sound like community
> management.
> 

I am not sure that client projects necessarily fall under Community
Director, but given that right *now* project relations is largely just
outreach to community, it sorta fits. I think it probably makes sense to
have a different role that communicates with Community Director that is
for project recruitment etc.

The primary Community Director stuff that William is doing is the
volunteer outreach, general social networking, managing contacts,
CiviCRM, building and sustaining the overall community of people and
supporters around the project.

> 3. Until it's settled, we should have a task force (temporary circle?)
> focused on co-op structure and governance. Let's become official.
> 

Yes, the co-op side is high priority. I have various co-op contacts, and
ideally we really need to recruit more of them to actively help.


> 4. Another area that needs immediate work is money transfer
> partnerships. That one will need ongoing maintenance, as well.
> 

Yes, and overall, the https://snowdrift.coop/p/snowdrift/w/en/teams/
page describes what we've already worked out. Let's work from there and
not reinvent things from scratch. All this is work-in-progress though.
_______________________________________________
Discuss mailing list
[email protected]
https://lists.snowdrift.coop/mailman/listinfo/discuss

Reply via email to