Hi there,
As you may know I'm one of the maintainers of the cpcsdk projects which hosts iDSK on github. It was raised to our attention that we never really specified a licence on it, making it difficult to package in Linux distros, for example.
I have now contacted all other people who contributed code and they agreed to release their work under the MIT licence. However, iDSK includes some parts of the original DSK management code from CPC-emu, which was not released under an open source licence. So I'm trying to contact Marco Vieth, the original author, to know if he would agree with this. I tried the contact form on CPC-emu website, but I have only little hope that this will actually work. If you have better ideas, let me know!
I know this is not the answer you're looking for but if you're certain of the parts he contributed to, you can rewrite them perhaps.
Then moving forward set a contributor policy. You can list the authors but keep the copyright to simplify licensing. I mean, there's no risk on you closing the project to make a lot of money with it :laugh:
Well... actually I'm not an user of iDSK myself, I have long ago replaced it in my toolchain using Ramlaid's cpcfs (also hosted on cpcsdk github in the cpctools repo). This one comes under an acceptable licence and the code is much cleaner. I have no future plans for iDSK and I certainly won't be the one trying to identify the parts of the code that comes from cpcemu and rewriting them.
I received a hint in private that Marco still has a website online with a contact address, so I tried that. But if it doesn't work, iDSK will just stay with its mixed freeware/MIT license.
I would have made the licence choice clearer from the start if it was one of my own projects, but I kind of adopted the sources as they were because it fitted my needs at some point and I never took the time to clarify this.
Well contacting Marco from the email on his website worked just fine. So you may now download iDSK 0.19 sourcecode and it is now packaged in NixOS. Thanks everyone :)
I'll see about providing official Windows binaries if I ever setup a development environment on my rarely used Windows machine...