-
Notifications
You must be signed in to change notification settings - Fork 10
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
Possible sponsors #128
Comments
I don't think that this working group, or any part of the rust project, should have anything to do with Blockchain or Cryptocurrency anything. It's destructive to the planet, and to society. Since rustaceans live on the planet, and are members of society, it's harmful to all rustaceans. |
I second that. Additionally, crypto lends itself to scams that are far too frequent and lead to significant legal consequences. |
Crypto associations will be controversial, independent of one's position on the topic. A small reward like 100$ is a very good idea, and given the small amount (it's 1 or 2 hours of the salary of a senior SWE), probably (my guess), companies that already support Rust Gamedev, will be able to sponsor, without any associated controversy. |
I feel like the Rust community is largely (and rightly) negative on crypto/blockchain - for example, see the reaction to the recent Rust Foundation tweet promoting a blockchain startup. Taking a sponsorship from a company like that is likely to put off as many people as the prize would attract, if not more. |
Rusty Jam(Game jam with games written in rust) co-host here. We recently got approached by a crypto company wanting this:
I don't exactly know what they want from us, but I think it would be great if they're going to be ready to sponsor Rusty Jam #3 prizes. I have zero experience with prizes, but I think the prize should be something small but will still make them feel good thing, like maybe 100$ dollars. Bigger prize is going to turn the whole thing from light-hearted competiotion to a battlefiled.
What do you think?
The text was updated successfully, but these errors were encountered: