Mapbox-gl-js: Create a project roadmap

Created on 7 Nov 2016  路  10Comments  路  Source: mapbox/mapbox-gl-js

I recently stumbled across the GitHub Platform Roadmap.

In few words, this page communicates the GitHub platform team's priorities.

I imagine it is effective at managing external users' expectations and focusing internal engineers' attention.

We should build something similar for GL JS / the GL ecosystem.

Most helpful comment

Adding a new page to the docs, here's a quick example:

screen shot 2016-11-10 at 10 33 48 am

there is interest on other teams

It appears we are beginning to use projects for things other than roadmap-specific work, which is totally fine. Even coming up with a re-usable jekyll template is a good start, then content is added manually.

All 10 comments

I agree! I see this lives on GitHub's developer pages. Could the GL JS equivalent live on mapbox.com/mapbox-gl-js?

I'd be happy to take this on but first would like to think about how it is kept up to date (programmatically or something manual?)

A linear roadmap may be a more useful system for us than release milestones. (Though we'll still release every 2 weeks)

Here are a couple rough requirements for whatever system we build:

  • store all roadmap state within Github issues / projects / pull requests
  • give us a framework to determine what the top n highest priority tasks are (perhaps sort first by priority label then second by issue creation date?)
  • don't show projects so far into the future that they are likely to be bumped out by higher priority projects before we get around to the
  • inform external users what we're working on next
  • help GL JS engineers figure out what they should work on next

linear roadmap may be a more useful system for us than release milestones

Yeah, I think starting simple is the way to go. No need to overcomplicate it right away.

I think we could add a new page to the mapbox.com docs at mapbox.com/mapbox-gl-js/roadmap (or an equivalent). This will give us an easy spot to point people to, plus we can link to it easily from within the docs.

A brainstorm of ways to organize roadmap content:

  1. By issue labels: we can create new labels, roadmap priority 1/roadmap priority 2/etc to query with the GitHub search API
  2. Use github projects exclusively for the roadmap, anything created as a project is on our roadmap. Some negatives here: there's no way to label projects, so we wouldn't be able to show priority in anything other than date
  3. Create a single "roadmap" project, which has columns based on priority. This could remove the need for adding issue labels, as well as even a need for mapbox.com integration.
  4. full manual on mapbox.com, just to get something out quick

cc @isiyu, who is interested in building something similar for another project. If we end up writing any code for this that could be shared, there is interest on other teams at Mapbox.

Adding a new page to the docs, here's a quick example:

screen shot 2016-11-10 at 10 33 48 am

there is interest on other teams

It appears we are beginning to use projects for things other than roadmap-specific work, which is totally fine. Even coming up with a re-usable jekyll template is a good start, then content is added manually.

Another layout option:

image

Let's plan on updating this manually on a weekly basis (I'll plan on doing this) for now, this will give us some time to figure out our real needs, then we can iterate.

Roadmap is live! Closing this now, we can iterate on it as we use it more.

https://www.mapbox.com/mapbox-gl-js/roadmap/

That link is now dead.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

iamdenny picture iamdenny  路  3Comments

rigoneri picture rigoneri  路  3Comments

shotor picture shotor  路  3Comments

stevage picture stevage  路  3Comments

aderaaij picture aderaaij  路  3Comments