-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub-based development process #9
Comments
I don't object to moving it to GitHub, but I don't really see the advantage
of using Bikeshed over just making it a Markdown document.
Regarding, PRs, what change did you have in mind?
…On Mon, Mar 5, 2018 at 7:37 AM, Daniel Ehrenberg ***@***.***> wrote:
It looks like the current source-maps specification is in a Google Doc.
This makes it a bit difficult to follow normal GitHub-based development
processes, such as making PRs to change the specification. Has this group
considered moving the specification checked into a repository to enable
this workflow? For example, Bikeshed
<https://github.com/tabatkins/bikeshed> could be used for the
specification document itself.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/ABMDKrQR56C89ne5TywT4XMwQHUd6837ks5tbVuigaJpZM4Scfe3>
.
|
Specifically for #8 . It seems like the source-maps spec is the right place for this, rather than the WebAssembly spec (by analogy to JS and CSS which also don't explain source map integration). |
About why Bikeshed over Markdown: Bikeshed does use Markdown, but it also has some nice tools for cross-referencing other specs, and a pretty template that makes everything look like a Real Spec (TM). |
I went ahead and drafted up a version in bikeshed: #24 That said I have neither permissions here, not do I know who calls the shots here. Can someone help me figure this out? |
The spec is now landed at https://source-map.github.io/source-map-spec/ so I think we can close this as fixed :) |
It looks like the current source-maps specification is in a Google Doc. This makes it a bit difficult to follow normal GitHub-based development processes, such as making PRs to change the specification. Has this group considered moving the specification checked into a repository to enable this workflow? For example, Bikeshed could be used for the specification document itself.
The text was updated successfully, but these errors were encountered: