-
Notifications
You must be signed in to change notification settings - Fork 293
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
This repo needs LICENSE/COPYING, also README #63
Comments
Just came here to leave this and suggest CC-BY :) |
I'm down to markdownify and add this stuff to the repo if anyone would like to write up what should go in where. |
This can now be closed @skade |
@alexbowers I can't close issues on this repos. @edunham can. :) |
We have a license now, but we don't yet have a README file. So not quite there yet. |
@Mark-Simulacrum @skade yes, we have a README #209 |
can be closed now? |
Yes, thank you! |
I assume it's some combination of CC-BY and copyright by respective authors, but we should make that clear.
Additionally, a README needs to document the purpose of the blog, the contribution process and guidelines (if community contributions are permitted, which is unclear), and the deployment process (GitHub pages).
The text was updated successfully, but these errors were encountered: