Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Maintain Source Map standard under whatwg

132 views
Skip to first unread message

Krinkle

unread,
Aug 28, 2015, 10:06:51 AM8/28/15
to dev-js-s...@lists.mozilla.org
Hi,

I'm wondering if the current contributors (especially John Lenz) are
interested in maintaining the Source Map standard under the WHATWG umbrella.

The https://github.com/whatwg/sourcemap has been reserved and I'd love to
start work on converting the Google doc[1] into a more standard standard.
We could use the bikeshed framework for the formatting (content based in
Markdown).

See https://dom.spec.whatwg.org/ and https://github.com/whatwg/dom for what
this could look like.

I'm hoping this will make the specification more accessible, and make it
easier to propose and merge contributions.

-- Krinkle
Timo Tijhof

[1]
https://docs.google.com/document/d/1U1RGAehQwRypUTovF1KRlpiOFze0b-_2gc6fAH0KY0k/edit?usp=sharing

Nick Fitzgerald

unread,
Aug 28, 2015, 12:44:11 PM8/28/15
to Krinkle, dev-js-sourcemap (dev-js-sourcemap@lists.mozilla.org)
What advantages would this bring? Why is this better than collaborating on
the source-map-RFC github repo and this mailing list?
> _______________________________________________
> dev-js-sourcemap mailing list
> dev-js-s...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-js-sourcemap
>

krink...@gmail.com

unread,
Sep 4, 2015, 11:55:16 AM9/4/15
to mozilla-dev-...@lists.mozilla.org
I wasn't aware of that repo[1][2], thanks.

I suppose if the spec ends up there (and easy to contribute via pull requests), and it's published as an easy-to-link-to html document, it'll effectively be the same.

Hosting the repo under whatwg may still be beneficial though. It increases exposure and discoverability. And may result more contributors, faster triaging of issue reports, responding to pull requests, etc. In any event, it won't change who the editors are. Access can controlled at a repository level.

Tools like bikeshed (or respec) are generic and work outside the org as well (if source-maps is interested in using that format).

-- Timo

[1] https://github.com/source-map/source-map-rfc
[2] https://github.com/source-map/source-map.github.io

On Friday, August 28, 2015 at 5:44:11 PM UTC+1, Nick Fitzgerald wrote:
> What advantages would this bring? Why is this better than collaborating on
> the source-map-RFC github repo and this mailing list?
>
> On Fri, Aug 28, 2015 at 7:06 AM, Krinkle wrote:
>
> > I'm wondering if the current contributors (especially John Lenz) are
> > interested in maintaining the Source Map standard under the WHATWG
> > umbrella.[..]
> >
0 new messages