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
Add use guidelines #166
Add use guidelines #166
Conversation
Good idea to have some "expectation setting" in the Readme/Docs! My 2-cent: AGPL is not a "permissive" license in the usual usage in the OS community but a "copyleft" license i think (and MIT/BSD are permissive). I strongly dislike co-authorships suggestions in other projects so would refrain here, too (though i haven't been much involved recently i probably should count much on this issue) - i'd think it's fine to notice that you're open to collaboration, but the license allows anyone to use it according to the license. In OpenSCM's case it's also the case that it builds on other people's work heavily, so it's even more difficult whom to include. For PRIMAP-hist we went with
So something like this might be appropriate for the SCMs shipping with OpenSCM in the future. I dislike lots of things about IIASA's SSP databases but i think them providing clear citation instructions and downloadable citation data is pretty great! |
I'm also not too much a fan of such notices. Maybe a short notice suffices that "we are open about collaboration"? I suppose, a nice |
Ok. So how about we go for:
? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be awesome ;)
c5160a5
to
30219f9
Compare
Sorry, I missed your understanding of the |
... I like the new encouraging colaboration paragraph! Can you sort the maintainers alphabetically again, please? |
Should we also provide a file which has all the citations in one (pulling citations from all over the place is one of the things I hate most when writing papers)? |
Done |
Maybe a function that collects all |
Just feels unnecessarily complex, why not just have a file? |
I think R has some standards to get a |
Ok, then maybe rename |
Like so? Given we don't have a citation yet this is the best we can do right? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Just two minor suggestions
Co-Authored-By: Sven Willner <sven.willner@gmail.com>
Adds usage guidelines to OpenSCM
CHANGELOG.rst
added (single line such as:(`#XX <https://github.com/openclimatedata/openscm/pull/XX>`_) Added feature which does something
)