-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 of perma-id/w3id.org repository #2602
Comments
Seems like an oversight that we don't have a licensing policy setup here. I would imagine code and text for the service itself would be some permissive mix of bsd, mit, apache, and creative commons. But we'll have to figure that out. Nothing here currently is complex. It's effectively an apache server. As far as the user submitted content, I'm not sure how that should work. I suspect most people would find it odd if their rules were being used directly at some different domain. But that seems harmless? In mostly every case the user rules are straightforward, so copying and modifying them for new uses doesn't seem like a big deal to me. The update hook is still in use. Requires some github settings to work. The link checks were disabled because it didn't work well. There are ways we could make that way better and more useful, but just doing nothing works pretty good too! One thing missing from the repo is an example apache config to make a simple clone. Setting up a simple clone is pretty easy, just disable mostly everything and point at a checkout. We should probably include a sample so people can easily see how to setup local test servers. |
@davidlehn, |
For a practical reason, attributions of thousands of ID maintainers can be a burden. CC-0 or public domain may be better. |
I would like to setup an organisational permanent-id service based on this service, and was wondering what the license is? While we will have own own redirect rules there is still some code/content that would be of use (git update hook, linkchecker, content from index page).
The text was updated successfully, but these errors were encountered: