Re:What my retraction taught me
by CJefferson on Friday January 22, 2021 @09:21AM
(#25871867)
I have over a dozen open source projects, many where I am the major author :) Therefore, I also get significant numbers of complaining emails.
For a while my e-mail address was in a header in gcc's C++ standard library, in retrospect that was a seriously bad choice.
It is fine to not do much support and bugfixing on such a codebase - but one should make sure to state it clearly in the documentation.
I try out published research code (in machine learning) all the time. Almost every time I have to debug and fix things. But in a couple of hours or days I can usually get it fixed, normally without any help. That is a shorter time than it take (in the best case) to even ask for access to code from a researcher.
Reduce barriers to entry. Make it easy for others to build on your work. Your chances of impact and value created from your work will be higher.