Meeting Notes 05 10 2015

How to get people contributing

• what does it do? / what doesn't it do?
• how does it work?
• how can I set it up?
• too much language about why, should add it as a blog post or something

Some things:

• Start semantic versioning of the application, http://semver.org/
• Changelog! Make it a file so every time someone changes something it gets recorded. https://github.com/mapbox/mapbox.js/blob/mb-pages/CHANGELOG.md
• Contributing. Here's a good example of very explicit contribution notes from Maki https://github.com/mapbox/maki/blob/mb-pages/CONTRIBUTING.md. Another from mapbox.js for adding examples: https://github.com/mapbox/mapbox.js/blob/mb-pages/DOCUMENTING.md

"What can I contribute?"

• how do I add an operator?
• change layer order
• icon set for GIS things
• branding
• UI design
• remove layers
• download & save file
• upload other file types
• create a view for geoprocessing (input parameters)
• write good descriptions for turf operations
• style geometry (either custom or programmatically)
• determine which operations are available for selected geometry
• rewrite readme
• save your work
• user stories / user cases
• write all the tests (@daguar agrees)
• research (i.e. what is already out there?)

Some other ideas:

• build a quick one-page index file for testing how to work with turf operations (will allow people to write small amounts of code for putting into DNC

On-boarding sub-track

• what are all of the things I have to install? install (git, npm, grunt)
• what is terminal
• what am I doing?
• what if someone has a PC? what if they are running Linux? EFFFFFF.