-
Notifications
You must be signed in to change notification settings - Fork 25
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
Terms and conditions link at VERY bottom of API contest page #17
Comments
Completely agree. We were excited when this contest was announced because our company has spent a significant amount of time automating the collection of a ton of data for import into IT Glue. We thought we had a good shot at winning. Then we read the terms and conditions (which, like you said, we really had to search for):
Given the work we have put into automation, we would never agree to such conditions. It's pretty clear that this contest exists so that IT Glue can repackage good-looking solutions into the product, sell them as their own, and not even have to reference the original author of it. These T&Cs apply regardless if you win or not. Our company held a meeting, and we unanimously agreed not to enter. I hope all those who enter realize what they are giving up for a chance at a gift card. I have a feeling our company's decision was not unique, and I wonder how many more entries they would have received if they didn't try to take possession of everyone's work. |
Exactly. Basically, we have to submit only our own work, but we relinquish any rights or claim to it once submitted and ITG can do anything they want to it, royalty-free. Seems like an abuse of trust, especially given the terms were not as obvious as they should have been. |
Note that the terms and conditions for submission into the contest is at the very bottom of the contest page, below a significant amount of white space. I would strongly advise reading this and understanding what you agree to give up by submitting to this contest.
ITG should have made this link significantly more noticeable, in my opinion.
The text was updated successfully, but these errors were encountered: