Licensing and Contribution guidelines

[Zeitsperre]

I would like to start contributing fixes where I can, and I'm wondering what license this project falls into, as well as how best to follow development conventions.

Both Synda and ESGPull are listed with a Public license, but this does not mean anything. Given that this project fetches climate data that could be used for planning purposes, something that at the very least has a "No Liability" clause would be good. Would the maintainers be friendly to a PR contributing a License here?

Are there any existing policies for this project concerning public contributions?

[svenrdz]

You are right, the Public license was a placeholder that means nothing.
I merged #20 so that the project does not stay without a license, but I am open to discuss further on whether a strong (or weak) copyleft should be used instead.
Having worked primarily on closed source projects in the past, I must admit I don't know much about licensing.

To answer your other question, contributions are very much welcome, I have started to write guidelines in a very generic CONTRIBUTING.md template, that should land here some time in the future.