Skip to content
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

Attribuition and license #93

Open
fmiramar opened this issue Oct 14, 2020 · 4 comments
Open

Attribuition and license #93

fmiramar opened this issue Oct 14, 2020 · 4 comments

Comments

@fmiramar
Copy link

Hi! Congrats for this work, really good to see this!

I started the SynthDEFaults project few years ago using my AKA Zé Craum and I am wondering if it isn´t better to mention all the contributors with their respective AKA on the readme of this project, making a list of all of them. The main problem that I see is that SCcode does not have one explicit license, so basically people can claim some type of direct attribution. When I was gathering the SynthDefs from SCcode I decided to use GPL3, but this is also a problem because the nested code did not said explicit that they were under GPL3....

I am not a specialist on copyright and law, but I think it would be polite to quote everyone as a whole in a list. What do you think ?

@brunoruviaro
Copy link
Member

Hi, and thanks for the feedback! We have listed the other projects we pulled from at the bottom our readme https://github.com/SCLOrkHub/SCLOrkSynths but I see it could be more prominently displayed. I will make an edit in a couple minutes, let me know if you have any suggestions to make it better?

@brunoruviaro
Copy link
Member

New readme here: https://github.com/SCLOrkHub/SCLOrkSynths/blob/master/README.md -- let me know if this addresses your concern in part or as a whole. Re-reading your comment I wonder if you were suggesting to include all the names of every single author in the readme. That would be ideal, and it's something I can plan to do in the near future. Thanks!

@fmiramar
Copy link
Author

Hi, Bruno! Thanks! Indeed I am more worried about the amount of contributions made by other people on the SynthDEFaults project then by mine properly. GDPR and the GPL3 had been a long discussed on SC list, I could not follow it properly, but I could see that developers and users have different opinions about what should be done...

I am convinced that people that post their code on SCcode won´t complain about the integration here, about the differences between GPL2, GPL3 and SCcode´s "absence" of license, but I think that they would be pleased if they see their name listed on the front page.

Another thing: e.g. many SynthDefs that I collected were under the name "Nathan Ho" and other were under the name "Snapizz". I took me a while to understand that it was the same person, so i merged this into "Nathan Ho aka Snapizz". I am not sure if people wanted this, but for organization purposes I made it like this. In my case I prefer if you could credit both "Fellipe Martins aka Zé Craum", but this is my case. This was critical specially in email list, because sometimes only "encripted nicknames" or other non artistic nicknames were used.... What do you think is the best to do ?

Sorry if this can be an inconvenient detail, but I am worried because of the amount of discussion about this kind of thing on email list...

@nhthn
Copy link

nhthn commented Oct 29, 2020

I'm Nathan Ho. Flattered that people like my SynthDefs, and I'm cool with having all my work that has been added to this repo licensed as GPL3 (more permissive MIT also fine). For attribution, just use my full name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants