3 ms·
> Unless, that is, I agree to work on a comparable solution for the university focused on solving the underlying problem I was building HuskySwap for. They woul
by lowercased 2y ago
> Unless, that is, I agree to work on a comparable solution for the university focused on solving the underlying problem I was building HuskySwap for. They would presumably own the IP and were clear that I wouldn’t be compensated. But it was implied that they would then remove the hold, allowing me to graduate.
I'm really baffled here because the code Kaim published is itself MIT licensed. The university could use it however they see fit after his version, and perhaps make a modified version which they then incorporate in to their system as the 'official' version.
Perhaps this code being public may expose potential flaws (logical, security, etc) which they don't want to have to deal with. Or might even be known flaws they don't want to expose.
- buildbot 2y agoI would be really shocked if that part actually happened. Major state universities don’t blackmail random students to write software for them. They make RFQs and send them to companies. There’s a software procurement process. 0 chance some person in the registrars office is taking this persons code off github and deploying it to UW production.
- lowercased 2y agoColleagues of mine at a local university often have students work on projects that get used by various departments. Nothing as big as a registration system, but data reporting UIs, data collection forms, etc. Usually paired with a senior staff member, it gives the students some hands on experience, and helps the dev dept get a bit more done (in theory - in practice, not always). Taking the OP at face value, someone saying "build us a version of this" doesn't seem out of the realm of possibility, but again... whatever was demoed is already MIT. Absolutely no reason the school itself couldn't build on that (inhouse or out-sourcing).