mapbox / mapbox/mapbox-gl-js

[react] Please sit around a table and talk

Open
#6,090 16 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs discussion :speech_balloon:
Dominant language
TypeScript
Stars
12.4k
Forks
2.4k
PR merge metrics
No merged PRs in 30d

Description

Hey :)

Basically reposting here to invite mapbox contributors at the table, as suggested
by @alex3165, and @ibgreen here...

- https://github.com/uber/react-map-gl/issues/451
- https://github.com/AlpacaTravel/react-map-gl-alt/issues/16
- https://github.com/alex3165/react-mapbox-gl/issues/511

-------

I think if that kind of discussion happen, we could keep this issue open here as a main, and close others.

-------

- https://github.com/AlpacaTravel/react-map-gl-alt
- https://github.com/uber/react-map-gl
- https://github.com/alex3165/react-mapbox-gl

Both MapboxGL.js and React are kinda 4 years old. There are currently 3 different, active and maintained, libraries out there trying to implement a React friendly API for Mapbox. While each of them is pretty great and hard work, each of them lack features. When coming from a raw MapboxGL.js background, new to react, this is pretty critical and hard to make a reliable choice. I guess coming from a React background and discovering MapboxGL and making the same choice is also hard.

This seems pretty much complicated, as governance, paradygms, workflows and many stuff are different in each of the repos. But it also feels like there is so much relevant and valuable thing to do with all that hard work, than 3 different and incompatible libraries..

The beauty of opensourcing is that everything is possible, isn't it ? So hey, what about sitting around a table and talking ?

Related :
- https://github.com/uber/react-map-gl/issues/87
- https://github.com/uber/react-map-gl/issues/176
- https://github.com/alex3165/react-mapbox-gl/issues/97
- https://github.com/mapbox/mapbox-gl-js/issues/4762

Cheers :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No project files or tests are named. Start by reading the linked discussions in uber/react-map-gl, AlpacaTravel/react-map-gl-alt, and alex3165/react-mapbox-gl, then compare the three libraries' goals and governance; done would require an agreed direction among their contributors, which this issue does not define.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.