...
The timing of when we go live with a new region will also be highly dependent on finding the right people (2-3 leaders for each region) to take on this role, so the list above is a starting point for thinking about where we will create regions.
...
How to support these Regional Coordinators is the big question. Finding coordinators doesn't seem to be the challenge – we're thinking through this process because we have people in different regions (India, South America, Africa, etc) who are approaching us and expressing interest in this type of contribution.
Ideally, our oversight over 100's of Meetup cities would be delegated to overseeing the work of a few dozen regional coordinators for all the major regions.
...
Some ways we can support the Regional Coordinators include:
- Infrastructure: We can create a mailing list and chat channel (following the community-NAME convention) and space on the
...
Budget:
Staff time: travel, etc.
...
- wiki for each region. Without this infrastructure the only way we've been connecting people in a region is through emails I send to people in the same region with the subject 'Building the Hyperledger community in NAME'
- Budget: We could allocate a portion of the Marketing budget towards funding things that would help these regional and local coordinators pull something together.
add note on naming
--------------------
what is happening today
simply adding new organizers to an email thread. for instead with perth and bolivia meetups...
have a template email for "Building the Hyperledger community in X" that i send to connect the organizers in a country or region
- Staff time: We can make ourselves available to Regional Coordinators when we travel so that they can organize a tour with staff members. We can involve Regional Coordinators in other aspects of our work as appropriate – for instance, would it make sense to have language representatives in the Marketing Committee call to help us bring our marketing efforts to non-English speakers?
- Other ideas for support...
Naming
I personally think that 'Regional Coordinator' as a name is uninspiring and dull and I recommend considering other options.
To me, this is one of several ways that a community member can act as an official Hyperledger representative. My recommendation is to broaden the current Ambassador concept and recognize that we currently have selected for just one specific type of representative, a Technical Ambassador.
We could add the concept of a Hyperledger Regional Ambassador to that list. I could also see us having other types, such as a Hyperledger Industry Ambassador to recognize the work our SIGs are doing to represent Hyperledger within the many different fields where our technology is being adopted.
This builds on a well defined concept of Ambassadors that has been established across many different open source projects. For instance, the Fedora Ambassador program defines Ambassadors as the representatives of Fedora.--------------------