search

simonpoole / old-osm-layer-index

Usable fork of editor-imagery-index
http://simonpoole.github.io/osm-layer-index/
Other
1 stars 0 forks source link

Why? #1

Open tyrasd opened 8 years ago

tyrasd commented 8 years ago

Usable fork of editor-imagery-index

Can you please explain the reason behind this fork and what you mean by usable?

I assume https://github.com/osmlab/editor-imagery-index/pull/124 is the main reason behind this repo, right? I don't see why we couldn't have got get something like https://github.com/simonpoole/osm-layer-index/commit/1c537523e5049db93298268682a2a63967fdd251 & https://github.com/simonpoole/osm-layer-index/commit/5472443667f64b80444f055243baf2d536df24e1 into the original repo to fulfill Vespucci's needs or are we now really back at the point where every osm-based editor needs to maintain their own set of imagery layers? :cry:

PS: I've just invited you to join @osmlab.

simonpoole commented 8 years ago

If you look back over history you will see that I have been one of the major supporters of the editor-imagery-index from the start, further I'm the main contributor to one of three editors that actually use it.

But the above naturally depends on it actually being useful and stable for the/my intended purpose and not being subject to major changes for puristic reasons at least not when it is trivial to work around the issue (which I'm still not quite sure what it is).