this post was submitted on 14 Oct 2024
27 points (90.9% liked)
Open Source
31020 readers
669 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I second this @OP / @[email protected], you’ll want to think carefully about if this is a situation where an open source/copyleft license is what you want to use. A couple concerns:
There are great reasons to use open source/copyleft licenses, but I don’t think they can or should be used in every situation. In this case they could be bad for both your and the festival’s interests. Ideally you’d be able to talk to a lawyer who specializes in contract and copyright law; the festival clearly has similar issues with other volunteer suppliers so perhaps they can find a lawyer willing to donate some time to provide them with a template that can be used for all their suppliers. Or if you’re doing a lot of freelance work yourself it’s probably worth finding your own attorney.
Otherwise I’d try searching online for “example content license,” “example image license,” “example development license,” or similar along with your state/province/country and try to come up with at least something basic to cover you and the festival.
Of course, if none of the concerns I raised are actually issues, Creative Commons has some great licenses.
This is all very helpful, thank you :)
I didn't know about that. I thought they might have to credit me, but didn't know that it would need to be on the work itself. I definitely don't want that. I hadn't thought about third parties either. I doubt that anyone would try to rip us off, but I don't want to leave that door open either, just in case.
I'm not overly concerned with future clients, as I'm medically retired and just doing this as a learning exercise. There's a tiny chance that I might get future work from this, but I'm more concerned with not cutting myself off from using the website / app template if I was to fall out with the festival at some point. As you say though, I don't want to leave either me or the festival open to having the content stolen either.
I've just realised that I need to double check how to handle third party images too. We have some local businesses who support the festival, so we use their logos as links on the site. If I include them in the repository, I don't want to accidentally give them away.
I've got some reading to do! :D