There is a need for an OpenStreetMap community building playbook, that would act as a guide for anyone trying to build a community either at the national or sub-national level. To answer questions around volunteers engagement, governance, data quality, organizing events, resource mobilization, diversity and inclusion, tools, partnerships, fundraising, etc
We will be discussing this at State of the Map 2022 and we would like to get your ideas here and also keep the conversation going. What would be the best approach to take to create an OpenStreetMap community building playbook, for the community, by the community? What topics would be the most important to include? How should it be structured, and where should it be hosted? What good examples of playbooks are out there from open communities that we can copy a leaf from? Please join the discussion by sharing your thoughts hereâŚ
Remember to make it openly licensed - using one of standard licenses. With editable format being public and available to anyone. Not necessarily making it editable to anyone, that would be different. Preferably using some standard place to cooperate. Make it easy to contribute.
Try to build on existing work rather than start from scratch. Has anyone tried to make such guide already?
Do you think that an OSM community would include not only mappers but also OSM technology enthusiasts and developers? Should the playbook include topics for that type of engagement as well?
Just as a starting point, I have tried to come up with a chapter structure for the Playbook I want.
This is just âwhat I wantâ, so Iâm sure it doesnât cover all your needs
What do you think?
What is community?
Kickstart the community
Make a Core
Identifying local community issues and outcome
Small start
Communication inside
Stock and flow of information (OSM wiki page and chats)
Build capacity
Training
Accompany the newbies
Localization
Tech and gadgets
Ethics and securities (OSM ways (copyrights and having fun!) and field activities)
Expand the community and the fringe
Making `Allies` (Identifying stakeholders. e.g. locals, students, companies and so on)
Approaching Open Source (nice) guys
Encourage voluntary / fostering their motivation
Visualize and promote the map outcome/results
Events and workshops
Expand the core
Iteration or Management (sustainability?)
Resolving conflicts
Organize a corporative body (chapter or something)
Fundraising
Tools
OSM tools, communication tools, management tools and so on.
Fantastic initiative! One of my reflections after State of the Map taps into @dkbenjamin question: it is my impression that quite a few of the community members seem to have more than one skillset or knowledge (sometimes including a technical skills of some sort, incl. data science or software development), but perhaps more importantly, the interest in, and knowledge of, the various (HOT)OSM tools and products are impressive! It would therefore be very interesting to better understand how we can better facilitate for these âhacktivistsâ to take part in the enhancement (and future) of the tools that enables the community to make an impact. Here, I am also including identifying problems or issues and/or bringing forward ideas as important part of this line of work.
cc: @Petya_Kangalova
On a practical note: one approach to consolidate reflections, learnings, mindsets, methodologies, approaches and tools that I personally keep going back to in whatever project or job I have worked on/in is IDEOs toolkit: www.designkit.org/methods. Perhaps this approach could be of inspiration? If not directly using the website as an inspiration, I can highly recommend using their methods on how to stay human-centered in the co-creation of a Community Playbook:)
Let me share one important point (at least based on my experience):
From the beginning there shall be a definitive amount of energy spent on keeping the community friendly and encompassing, in mood and nature. This sounds trivial, I know. Small communities are often donât even see why this is important.
As a community starts to grow some typical problems arise: senior members start to feel superior to newbies, they start to keep quality by reacting more and more harshly to the mistakes and inexperience of new members, the community may go in a direction where the ârulesâ are more important than talking about the problems and (preferably proactively) resolve them.
Keeping healthy mood requires some dedicated people to keep giving feedback to people diverging from the expected open attitude, to prevent escalating it to âmoderationâ and âbansâ. Sometimes it requires lot more time expaining the problems and trying to find a resolution than to âblockâ the problem (administratively or technically). It worths noting that spelling out positive core values in the beginning helps remindig community members that they really shall spend energy on staying positive.
I do not want to cite bad examples, I am sure many people could think of some. For me OSM community is a good example, and I hope it stays that way. It needs work to keep it that way.
I gave an OSM US Mappy Hour talk about âbuilding and growing an open source communityâ. You can watch it here:
That was about starting a technical project, but there are many parallels to building an organization. Creating a positive environment that people want to be a part of is no accident â you have to work at it.
That also should be included are ideas for events, like a regularsâ table or a mapathon vor workshops for example. Just a quick outliner on what should be included and common pitfalls and so on.
@nyampire
Did you expand your chapter structure? The whole playbook sounds like it should be in the wiki - it can be edited by anyone.
