Skip to content
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

database: Licensing information coming soon #1282

Open
ghost opened this issue Jan 10, 2022 · 7 comments
Open

database: Licensing information coming soon #1282

ghost opened this issue Jan 10, 2022 · 7 comments

Comments

@ghost
Copy link

ghost commented Jan 10, 2022

Is your feature request related to a problem? Please describe.
Licensing

Licensing information coming soon

Describe the solution you'd like
I guess it's obvious but in case not, a specific license for the database contents especially for the user contributions.

Ideally with an up-to-date downloadable snapshot of the entire contents.

Describe alternatives you've considered
Anything else would be duplicating your efforts.

Additional context

@marxian
Copy link
Collaborator

marxian commented Jan 10, 2022

Hi @electronoob,

I don't think we'll ever be making a database snapshot available, since it contains PII in the form of contributor names, which we'd not be able redistribute.

Please let us know your use-case! If it is for public good, academic research or journalistic purposes we can probably find a way to help.

@ghost
Copy link
Author

ghost commented Jan 10, 2022

Thanks for the prompt reply @marxian,

Can I backup data from the public API and make that available on my github with attribution? Since it's already being offered publically anyway, so there's no good reason to hide it, as you would have already done the appropriate PII redaction on it.

@ghost
Copy link
Author

ghost commented Jan 10, 2022

Please let us know your use-case! If it is for public good, academic research or journalistic purposes we can probably find a way to help.

I would immediately make the data publically available on github and happily remove any names etc.

@marxian
Copy link
Collaborator

marxian commented Jan 10, 2022

I'm still trying to figure out the benefit of publishing a backup of the dataset. Is there a use-case for which the api is not sufficient? If so we'd like to figure out how to serve folk better.

Please don't think us truculent - part of the reason is that we're currently taking advice on the appropriate open data licence under which to publish. We currently encourage use by public bodies and researchers, but don't allow commercial use of the dataset. When you say you'd make it "publicly available" do you mean you'd republish it under a permissive licence?

@ob6160
Copy link
Member

ob6160 commented Sep 10, 2022

I'm closing this issue as it's been inactive for a while

@ob6160 ob6160 closed this as completed Sep 10, 2022
@ghost
Copy link
Author

ghost commented Sep 11, 2022

this shouldnt be closed, as it serves as a reminder that it needs addressing.

@ob6160 ob6160 reopened this Sep 11, 2022
@ob6160
Copy link
Member

ob6160 commented Sep 11, 2022

this shouldnt be closed, as it serves as a reminder that it needs addressing.

good point - reopened

@ob6160 ob6160 closed this as completed Sep 11, 2022
@ob6160 ob6160 reopened this Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants