3 ms·
You forgot to consider IP issues. Schools vary a lot on their policies by but for many the code belongs to the school and can not be open sourced without permis
by robotresearcher 11y ago
You forgot to consider IP issues. Schools vary a lot on their policies by but for many the code belongs to the school and can not be open sourced without permission which requires extra work. Funding sources have their own IP deals to consider too.
It all sounds so easy until you look at the actual constraints. Professors are usually smart and experienced and they have thought about this stuff a lot. If it was as easy as you thought, it wouldn't be a problem.
I publish all code as a matter of lab policy. I chose where to set up my lab partly so that I was able to do this. Not everyone has this luxury or makes this a priority.
- wyattpeak 11y agoYou're right, I did, but I wasn't actually addressing ease in some absolute sense, I was talking about the appropriate tools for the job. If researchers have the legal right to publish their work, I can't see any reason why github wouldn't be exactly the place they'd share it, rather than some custom online research system as proposed by the parent. That said, I don't have any experience in CS research, it's not my field, so I may be wrong about that, do tell if so.
- robotresearcher 11y agoWe share our code on github and publish the commit hash for the code that generated the results in the paper. That way we can continue to develop the code after publication but readers can retrieve the exact code described in the paper if they wish. Simple and effective. But again, the IP rules at my university allow this at my sole discretion, which is unusual.