- Find the singal in the noise, and respond clearly
- Take a contribution posture
- Provide evidence of our work and experience
- Ask for help from the team
- ...
- OSM has always been awful place to communicate. Open source software culture. Northern European Programming Dudes.
- Comms have not scaled.
- OSM is smart people who thrive on recognition over their smartness and contribution.
- Allow them to be heard
- Most "trolls" don't know how awful they come across online.
- Some do, and are not worth our time.
- OSM "Volunteers" but increasingly not.
- 6 of 7 OSMF Board Members involved in OSM in their job.
- Fear of commercial entity using the OSM community, but not giving back. ODbL. Mapbox scepticism.
- ...
http://wiki.openstreetmap.org/wiki/Contact_channels
- Mailing lists
- subscribe to talk@ and talk-in@
- some countries prefer Forums
- IRC
- http://wiki.openstreetmap.org/wiki/IRC
- jump in, bring a buddy
- Diary Posts
- Mapbox Blog Posts
- WeeklyOSM
- read it!
- ...
- https://vimeo.com/68093881
- http://brainoff.com/weblog/2012/03/30/1773 Other ways of finding communities (tools and analysis approaches)
Mapping Project Guide
- Clap threshhold for tweets.
- if you want, ask on Slack for review before posting.
- Diary posts
- these can be rough, translated in your local language
- tweet your own diary posts
- Blog posts
- Whenever you ship, does this need to be heard by a wider audience?
- Collaborations with Telenav and Mapzen on data QA https://github.com/mapbox/data/issues/1598
- Contribute to SysOps https://github.com/mapbox/data/issues/1595
** diary our notes approach after osm-comments is launched **
John Firebaugh talk fro SotMUS 2014
https://vimeo.com/91877574