Skip to content
Please note that GitHub no longer supports your web browser.

We recommend upgrading to the latest Google Chrome or Firefox.

Learn more
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

Move the README to respec? #15

Open
ruebot opened this issue Nov 14, 2018 · 5 comments

Comments

@ruebot
Copy link
Member

@ruebot ruebot commented Nov 14, 2018

I was looking through the spec again, and looking for SHOULD, MUST, and realized when we wrote this long ago, neither of us had any respec experience. I have that now from working on the Fedora spec. So, should we move the README to respec? If so, I'm happy to take it on, and setup GitHub pages for the repo to publish it there.

@mjordan

This comment has been minimized.

Copy link
Collaborator

@mjordan mjordan commented Nov 14, 2018

If we went to respec, would our spec look like https://fedora.info/2018/06/25/spec/ ? If so, where would we publish it?

@kba

This comment has been minimized.

Copy link
Contributor

@kba kba commented Nov 14, 2018

You could create a Github Pages site for the organization bagit-profiles, the spec could live at https://bagit-profiles.github.io/<version>/

I would appreciate a more formal spec and can also help with that (though I know bikeshed better than respec).

In addition to the contents of the README, I'd find it useful to have an informal "Implementation Report"-like section with samples used in the wild.

@ruebot

This comment has been minimized.

Copy link
Member Author

@ruebot ruebot commented Nov 14, 2018

I'm cool with Bikeshed. I'll start a branch later today or tomorrow, and we can start hacking away at it there.

@ruebot

This comment has been minimized.

Copy link
Member Author

@ruebot ruebot commented Nov 14, 2018

@mjordan yeah, it'd be what @kba said: https://bagit-profiles.github.io//

@ruebot

This comment has been minimized.

Copy link
Member Author

@ruebot ruebot commented Nov 19, 2019

Onec we sort out the current two PRs (#21 and #20), I'll incorporate their outcomes into the respec branch, merge that into master, and publish it with gh-pages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.