Second the people point that @Mte90 and @skade raised.
Perhaps it’s one of our strategies that “Changes in Community Support in 2017”. We are losing many many Mozillianized-staff that had build great bridge between volunteers and MoCo/MoFo in past few years very quickly. Gen Kanai (was Asia communities wrangler), William Quiviger (was South-east Asia and South Asia and Europe wrangler), Guillermo Movia (LATAM wranger), Brian King (Europe wrangler) and TJ Lee (for Firefox Student Ambassador) as my quick example, many more names follow.
We’re not only losing the local volunteer because they will need to re-build relationship and sync their minds with new staff (or there is even NO new staff in place, like in my country or FSA for long time), and also local projects would be hard to continue due to lack of wrangler after the core community staff depart, and new staff has no enough background experience on those project.
Volunteer will be struggling finding building new relationship and finding new things to contribute, and they need great community-minded staff to keep care, or they will just stop contributing (only to Mozilla, perhaps). And we will leaving bad reputation on it.
When we kill projects and cease it’s staff position, we’re also eliminate related communities. For example, we’re losing a whole global community after we killed Webmaker and it’s localization project, and we’re losing also a global scale of communities around WebApp after we killed Firefox OS (Now we saw Google is taking the lead with PWA in here).
I know it’s common that people came and go in big project, but it’s very pain on community building. I have to trying build new relationship with different staff almost every year (even every few months). I had experience that failed to keep with latest re-org, and I lost the opportunity to be include, eg. not knowing there is new related-call to join. And it’s even more struggle if the new face has no community-like mind (we had deadly experience on that.)
Because local community are mostly lasting longer then current community wrangler staff and any Mozilla projects (besides Firefox), I and many Mozillians already start keeping our contributing not too dedicate and devoted to any single Mozilla project, in order to prevent hurt when it ceased. It’s not really positive, is it?
I know we want to enable volunteer to do the job, but in fact I don’t think it as a working solution. Volunteer has no enough resources, has no enough time. They already have many local growing projects (and they don’t want to lose it), and they now have other countries to work. In many country, there are multiple communities around different projects.
We’re end up with a very bad hierarchy structure, which we would like to avoid due to conflict we already saw many times in different regions (e.g., conflict that in the end killed whole community few years ago in Malaysia for example).
In my experience, to keep growing local community took me 100+ hours a month, and to help mentoring only ONE community in other country took me another 10+ hour a month. And I’m already missed other communities in the same country, not to mention other nearby countries. (In the mean time we have other Mozilla projects and calls to follow besides community growing.)
Volunteer will end up burn out, and local communities will feel even worst and un-confidence when people (who claim to be their coach) come and go more frequently then staff. Sorry, it is just not that realistic as a role for non-full-time people.
What do you think Mozilla should do to succeed that we are not doing right now?
Try to keep great community builders within Mozilla, and keep brining good builders in. There are many great volunteers working hard on building communities for many many years. We should give them resource, invite them in and make full use of their ability. A health and diverse global community need staffs who had local mind with resources to care and help, and it’s is always our core strength against any challenger.