Skip to content
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

Review whether new specs should be in Respec or Bikeshed #25

Open
toddreifsteck opened this issue Oct 25, 2018 · 3 comments
Open

Review whether new specs should be in Respec or Bikeshed #25

toddreifsteck opened this issue Oct 25, 2018 · 3 comments
Assignees
Labels

Comments

@toddreifsteck
Copy link
Member

Bikeshed has better link validation mechanics at built time.
Respec is the tool the group has been using.

We should evaluate whether we should change spec tools and what our process is for creating a new spec.

Possible additional issue to cover:

  • Snapshot of Last Known Good version of Respec if we stick with it
@tdresser
Copy link

@domenic

@annevk
Copy link
Member

annevk commented Feb 25, 2020

Not sure if this is too late, but please use Bikeshed. It makes it easier to move things between WHATWG and Web Performance documents as well as deal with cross-spec cross-references, and in general has a slightly better end user experience.

@marcoscaceres
Copy link
Member

as deal with cross-spec cross-references,

ReSpec and BikeShed use the same terms database.
http://respec.org/xref/

and in general has a slightly better end user experience.

That's open to debate ;)

But in all seriousness, you can find badly written specs using either tool - it's really a matter of how well people know the tooling and we are working on hopefully making the situation better for both ReSpec and BikeShed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants