It's not right to allow commercialization and selling of people's submissions in your license. You have to stop this. Please remove this language from your rules. Exploiting entries for profit is a bad look in any case, but especially given current circumstances.
LICENSE. You grant to Twilio and their affiliates a non-exclusive, worldwide, perpetual, fully paid up, royalty-free, sublicensable, transferable license to (1) hyperlink to your website and software from Twilioβs websites, or websites from Twilioβs agents, affiliates, or assigns; (2) use and display your name, professional and personal information, photo, likeness, and your trademarks related to your software for any purpose related to this Competition ; (3) copy, distribute, sell, compile, revise, commercialize and otherwise use any Submission transmitted to Twilio, linked to, or listed on any registration form.
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.
Thanks for raising your concern, @imgntn
! Twilio definitely has no intention to sell or commercialize your submissions. We will work with our legal counsel to revise the terms.
Thank you - I know a lot of this is boilerplate but I think you'll get more/better entries if people are comfortable that their work won't be commercialized or sold. Best.
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.
Totally get it. We updated our terms for the hackathon and dropped the sell and commercialize from (3). You can find the updated terms here: twilio.com/legal/twilio-dev-hackat...
Way to respond quickly and kindly to helpful feedback! I love the mindset of almost everyone I've run across on this site, and appreciate you following suit despite the corporate presence! π
If so, I wasnβt bashing all corporations. I understand their helpfulness, certainly.
However, my personal belief is that the idea that this mindset youβve described is needed for continued growth is aging quickly. Iβm working on developing new economic ideas behind user centric DAOs, for lack of a better term. Thatβs all Iβll say on that point.
To clarify my comment: again I understand the usefulness of corporations. However, itβs getting more and more obvious in techland where corporations interests and biases and influences lay. As a member of tech land, I find this obnoxious if not outright abusive (of monopoly, for example).
The above concession with the removal of the abuse of power is refreshing.
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.
Twilio has no intention to sell or commercialize your submissions. We updated our terms for the hackathon and dropped the sell and commercialize from (3). You can find the updated terms here: twilio.com/legal/twilio-dev-hackat...
French web developer mainly but touches everything. Volunteer mod here at DEV. I learn Nuxt at this moment and databases. β Addict to Cappuccino and Music
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.
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.
It's not right to allow commercialization and selling of people's submissions in your license. You have to stop this. Please remove this language from your rules. Exploiting entries for profit is a bad look in any case, but especially given current circumstances.
Thanks for raising your concern, @imgntn ! Twilio definitely has no intention to sell or commercialize your submissions. We will work with our legal counsel to revise the terms.
Thank you - I know a lot of this is boilerplate but I think you'll get more/better entries if people are comfortable that their work won't be commercialized or sold. Best.
Totally get it. We updated our terms for the hackathon and dropped the sell and commercialize from (3). You can find the updated terms here: twilio.com/legal/twilio-dev-hackat...
Way to respond quickly and kindly to helpful feedback! I love the mindset of almost everyone I've run across on this site, and appreciate you following suit despite the corporate presence! π
Try to understand that without the funding from a corporation of some kind neither this Hackathon nor the internet, or IETF would exist.
If I don't have an alphanumeric to stand on please enlighten me. Happy to discuss this you.
Take a look at this en.m.wikipedia.org/wiki/Internet_S... it might help you understand more about how things got started.
Hey Bernard, was this a response to me?
If so, I wasnβt bashing all corporations. I understand their helpfulness, certainly.
However, my personal belief is that the idea that this mindset youβve described is needed for continued growth is aging quickly. Iβm working on developing new economic ideas behind user centric DAOs, for lack of a better term. Thatβs all Iβll say on that point.
To clarify my comment: again I understand the usefulness of corporations. However, itβs getting more and more obvious in techland where corporations interests and biases and influences lay. As a member of tech land, I find this obnoxious if not outright abusive (of monopoly, for example).
The above concession with the removal of the abuse of power is refreshing.
Does that help clarify my point?
Yes it was. More information about your economic ideas please.
Please explain the interests, biases and influence.
When you say "above concession", are you referring to the legal clause?
Wow. I think you have a complicated task on your hands. But I'll leave you with these questions? How will you fund it? Keep the lights on?
I have to get back to work now. Bye!
I think you should pursue this idea.
Thank you so much for pointing this out.
Have a blessed day.
Twilio has no intention to sell or commercialize your submissions. We updated our terms for the hackathon and dropped the sell and commercialize from (3). You can find the updated terms here: twilio.com/legal/twilio-dev-hackat...
twilio.com/legal/twilio-dev-hackat... return 404 error :c
Sorry for that glitch. It's back :)
Should be working now!!
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.