-
Notifications
You must be signed in to change notification settings - Fork 22
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
What does "copyright the NHS Hack Day community" mean? #119
Comments
I have no idea. +1 for not having one at all. |
I mean, I do like the idea of having proper copyright assignment, but at that point you want an entity to assign things to (which is a very different discussion...) |
I remain happy with you being in charge of that :-) |
-10 to not having one. In practice we regularly ask people to not use the brand/photos/etc for their Not Nhs Hackday. Ohc is the natural legal entity unless someone volunteers to do the extra paperwork. |
I misread the double-negative and was just about to push a commit removing it :P In which case you'll probably want a CLA for contributions + copyright assignment for existing? Am happy to look at that (bwim probably "steal someone else's + build committer list") tomorrow night. (Longer term I'm happy to look at distinct organisation if that works, but not this month) |
@doismellburning et all -- can you reach a consensus on this? I'm in favour of having some licence-y thing as per David's comment above. We talked in the pub last night about having a Brand New Shiny And Unpartisan Organisation potentially, rather than continuing to use OHUK...hmmm |
I'm pro some licence-y thing (I think we all are). I'm anti "semi-meaningless licence-y thing of misdirection". So NHSHD as a Company Limited by Guarantee then? (I feel the scope of this issue might have just suddenly ballooned ;)) |
To contain scope (at least temporarily!) GPL? |
What about: (c) NHS Hack day @ Open Health Works 2018 |
Can we either have a proper copyright declaration / implementation, or just not have one at all?
The text was updated successfully, but these errors were encountered: