Dominik Kundel I'd like to submit my projects with a copy-left license (preferably GNU GPLv3) this ensures that my projects or any of it's forks never get Closed-source.
Telling candidates to stick only with a Permissive Licenses is the same as rule (3), these licenses already make the project available to copy, distribute, sell, compile, revise and commercialize by any other person in the world.
I'm a developer, product manager and public speaker based in the SF Bay Area. I'm passionate for JavaScript, the web, hackathons, teaching, photography & cocktails.
I absolutely understand your concern. Our goal with Twilio CodeExchange is to enable as many developers with code as possible and allow the community to showcase their projects. Ultimately it is your call under what license you license your code but since this hackathon is celebrating the opening of community submissions for CodeExchange, we decided to limit it to permissive licenses only since that is the limitation for CodeExchange and every entry might be added there.
Again Twilio does not have any intention in selling your work and I know it's not necessarily blocking others from a licensing perspective. Ultimately it's your call what license you put your work under.
We'll make sure to revisit the policy for the next hackathon we run.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Dominik Kundel I'd like to submit my projects with a copy-left license (preferably GNU GPLv3) this ensures that my projects or any of it's forks never get Closed-source.
Telling candidates to stick only with a Permissive Licenses is the same as rule (3), these licenses already make the project available to copy, distribute, sell, compile, revise and commercialize by any other person in the world.
Hi Rohit,
I absolutely understand your concern. Our goal with Twilio CodeExchange is to enable as many developers with code as possible and allow the community to showcase their projects. Ultimately it is your call under what license you license your code but since this hackathon is celebrating the opening of community submissions for CodeExchange, we decided to limit it to permissive licenses only since that is the limitation for CodeExchange and every entry might be added there.
Again Twilio does not have any intention in selling your work and I know it's not necessarily blocking others from a licensing perspective. Ultimately it's your call what license you put your work under.
We'll make sure to revisit the policy for the next hackathon we run.