Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upMove the README to respec? #15
Comments
This comment has been minimized.
This comment has been minimized.
If we went to respec, would our spec look like https://fedora.info/2018/06/25/spec/ ? If so, where would we publish it? |
This comment has been minimized.
This comment has been minimized.
You could create a Github Pages site for the organization 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. |
This comment has been minimized.
This comment has been minimized.
I'm cool with Bikeshed. I'll start a branch later today or tomorrow, and we can start hacking away at it there. |
This comment has been minimized.
This comment has been minimized.
@mjordan yeah, it'd be what @kba said: https://bagit-profiles.github.io// |
ruebot commentedNov 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.