Split style-spec to a different repo

[HarelM]

Motivation

The style spec is a whole subject that deserves its own repo.
This new repo should facilitate for documentation and the style validation code.
It should also include the typescript definitions in that package (in npm).
This way, this repo can consume this package no matter how it is implemented internally.
As a starting point I would advise to simply move parts of this repo as is (without any code changes) and make sure everything works as expected, once this is done we can discuss the next step for this new repo, either creating a similar package for the native repo to use, refresh technology, change to json-scheme or whatever.
But the first step is to split this apart and define a proper interface.

Design Alternatives

Keep everything together in a single repo.

Design

Describe above - split to a different package, define an interface/API and use it

Acceptance criteria for the bounty:

1. Style spec definition, validation, documentation are in a new repo, including CI of tests and publishing of package and docs.
2. The code is removed from this repo, and this repo only depends on packages produced by the other repo

Link to bounty:
maplibre/maplibre#191

[HarelM]

Cc: @birkskyum @wipfli @louwers @ovivoda

[birkskyum]

These four issues contain quite a lot of gotchas and pitfalls. I'd be able to plan and resolve them all, but it would likely take me a full week, which I unfortunately can't carve out for a bounty this size ~25$/h. Let's see if someone else wants to give it a go.

• (blocking for issues below) Setup of development environment locally fails maplibre-gl-js-docs#384
• (blocking for issues below) Can't update style-spec because missing rollup folder maplibre-gl-js-docs#389
• Bring in the docs repo #2150
• Use @maplibre/maplibre-gl-style-spec in MapLibre GL JS #2194

[HarelM]

Thanks for the summary of this. The current state is worse than I thought. I'll see what can be done.

[krishnaglodha]

Hi @HarelM , please let me know if the task is available, I'd like to contribute to it

[HarelM]

Please coordinate with @birkskyum as he has started looking into it and started working on it.
This issue is dependant on different issues and it's probably the last one to be finished.

[birkskyum]

I Guess this can be closed now then - unless the expression test conundrum also is included here.

[HarelM]

Resolved by maplibre/maplibre-style-spec#88

[wipfli]

@birkskyum let's add a link to the bounty payment in opencollective here. So you could write something like:

"Expense on open collective: https://opencollective.com/maplibre/expenses/132832"

And then @HarelM can comment something like "The work has been completed and the bounty can be paid out"

[wipfli]

https://maplibre.org/roadmap/step-by-step-bounties-guide/#3-claiming-a-bounty instructions are here

The doubly-linking might look like too much work, but I have seen a lot of expense requests on opencollective in other projects from people that did not do any work. So let us avoid scams and false payments by doing this doubly linking...