maplibre / maplibre/maplibre.github.io
Additional roadmap items
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 23
- Forks
- 47
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 41
Description
MLT.
One roadmap item does defintively not represent the level of effort that this is. @nyurik
- should we either split the MLT roadmap item into the project level (general, gl-js, native) or
- into the encoder/decoder level?
There are also a few refactorings, which I feel we could publicise in this way @louwers
- plugin system -> https://github.com/maplibre/maplibre-native/pull/3703
- long running tests
maplibre-core
on the gl-js side, I don't know which, but I am sure things are also going on which woulld be interesting marketing wise @HarelM
Maputnik does not currently have any items. There has been lots of progres in this area.. @HarelM should I summarize some of it and add roadmap items or would you rather this to stay as is.
[!TIP]
I can write up these roadmap items, but would like to have the "go ahead" from the maintainers for this.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the current roadmap items and the proposed MLT, plugin system, long-running tests, maplibre-core, gl-js, and Maputnik topics. First obtain maintainer approval on the proposed organization, then document the agreed roadmap items and confirm that the effort level and project coverage are represented accurately.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100