State of the Chop

I was reading the CoC for Cugos and ran across this section quoted below.

Step down considerately. Members of every project come and go. When somebody leaves or disengages from the project they should tell people they are leaving and take the proper steps to ensure that others can pick up where they left off. In doing so, they should remain respectful of those who continue to participate in the project and should not misrepresent the project’s goals or achievements. Likewise, community members should respect any individual’s choice to leave the project.

It’s been a while since anyone has committed any changes to Dropchop so I just wanted to start a discussion on the project as I see it. This is a volunteer run project and continued development requires a lot of dedicated time from the volunteers. That’s time not many of us have.

I want to say first that I have no intentions of stepping down from this project. In December, I spoke at the Cugos meeting to demo how we could possibly refactor DC to render much larger GeoJSON files using Mapbox-GL. Unfortunately, I am not able to configure the rendering how I want to and decided to wait until Mapbox-GL had data-driven styles. I know the folks at Mapbox are working hard on this and I completely understand how long the process can take. Once data driven styles are available in Mapbox-GL, I will happily take up development again. Until then, I’ve left my unfinished work in the mapbox-gl branch.

[nickpeihl]

Oh holy Hannah! I just now saw that data driven styles dropped today. https://www.mapbox.com/blog/data-driven-styling/

[mapsam]

I started cleaning out some open PRs today, getting me excited about dropchop again. Moving slowly, and trying to remember how this all works makes me realize that the gulp/grunt/etc. build ecosystem makes this really hard for beginners (including myself x number of months later). I’d propose a mini-sprint trying to harness browserify and require() as much as possible whilst reducing dependencies.

cc @nickpeihl