Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Specification Flow could be improved (but what do we work on next?) #1527

Open
@gregsdennis

Description

@jdesrosiers and I had some brief "in passing" discussion somewhere about how the specification flow could be improved.

  • definitions could be consolidated
  • some related sections could be brought together
  • etc.

We currently have a plan of things to do, and there are a lot of smaller things that could be done once #1510 (vocab extraction) goes through.

I'm less interested at this time about exactly what those edits entail, but more interested in the order in which we work on all of the open issues we already have relative to this big edit.

So how do we want to do this? (How do you want to review it?)

🚀 large edit up front, then the smaller things
🎉 (削除) smaller issues up front, then the big edit (削除ここまで)
😕 some smaller issues, the big edit in the middle, then finish with more smaller issues
😄 just do the smaller things to get the spec out, and do the big edit for the next release

I think 🎉 and 😕 will end up being the same thing. If we do all of the smaller things that we currently have, we'll inevitably have more smaller things crop up while we're doing the big edit.

I'm okay with all of these options, but I want to hear from the rest of the team. Emoji voting enabled.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      AltStyle によって変換されたページ (->オリジナル) /