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

Refactor the specs into separate repositories? #750

Closed
ndw opened this Issue Feb 7, 2019 · 5 comments

Comments

Projects
None yet
3 participants
@ndw
Copy link
Contributor

ndw commented Feb 7, 2019

There's value in keeping the specs in a single repository because they share a bunch of common prose and link to each other. But there would be value in putting the steps specification into the steps repository because that's where step issues are raised.

I suppose with a little more build magic, we could have the steps specification in a different repository, but still pull them all together in the build for the language spec.

Thoughts?

@gimsieke

This comment has been minimized.

Copy link
Contributor

gimsieke commented Feb 7, 2019

A drawback could also be that whenever we reorganize the specs, we’ll have to move the issues, too (and also update references to issues). I wouldn’t oppose though.

When the subspecs reside in separate repos, we can use Git submodules to tie them together. This requires less magic. Note that submodules are fixed to a certain commit; you’ll have to get used to updating them to the latest commit and commit the containing overarching spec.

@ndw

This comment has been minimized.

Copy link
Contributor Author

ndw commented Feb 7, 2019

I'm not proposing a separate repo for each step spec, just moving all the step specs to the steps repo. Because that's where the issues are.

And yes, submodules is one way forward. I'll investigate what the build process would be like.

@xml-project

This comment has been minimized.

Copy link
Contributor

xml-project commented Feb 8, 2019

This sounds like a good idea to me. Currently I have to switch repo between reading the issue and looking at the actual text. This is (somewhat) annoying.

@xml-project

This comment has been minimized.

Copy link
Contributor

xml-project commented Feb 16, 2019

@ndw I think this is done. Close?

@ndw

This comment has been minimized.

Copy link
Contributor Author

ndw commented Feb 16, 2019

Yup

@ndw ndw closed this Feb 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment