This is a good point, thank you :)
I was thinking along the lines of not restricting myself from using my own work in the future, but I hadn’t thought about third parties being able to use it too. I’m not concerned about other people using the code behind the website, for example. I’m still learning, so it’s probably more spaghetti than anything decent, but @[email protected] pointed out in their reply, I wouldn’t be able to stop anyone from using graphics etc.
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