-
Notifications
You must be signed in to change notification settings - Fork 26
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
License #23
Comments
Thanks, important point. I'd agree with using CC-BY Intl 4.0 as default (but allow others (less restrictive) if requested by authors), and will try to ask all contributors of blog posts if they'd be okay with that. Should also include this in the footer (which doesn't yet exist), or similar. |
yeah good points, I fully agree! |
Emails sent, and first answers coming in. Tracking: How to set up intl RSE assoc
Intl RSE Leaders Workshop
Tools for managing RSE projects
2nd Workshop summary
Research Software Engineer's Toolkit
Single Entry Point & Marketplace
How do RSE groups work?
|
+1 to CC-BY Intl 4.0 by default - thanks for looking into this |
+1 for suggested License |
(An author just let me know that the posts were originally published under CC-BY on the UK RSE site, but when moving them, the badge/notice may have been lost.) |
Approval collected from authors & transferred (#23 (comment)), so I've now set up a footer & added a license file to the repo, and am closing this. |
Alejandra Gonzalez-Beltran asked if the blogposts on the website have a license, when I checked I noticed that the website doesn't have a license at all. I'd like to change that ASAP, and I think we should probably use a CC-BY license, what do you think? @sdruskat
The text was updated successfully, but these errors were encountered: