2 ms·
It's hard to quantify, but it can be non-trivial. See my other comment about the one internal tool we might release. Part of the reason it hasn't been released
by mindcrime 14y ago
It's hard to quantify, but it can be non-trivial. See my other comment about the one internal tool we might release. Part of the reason it hasn't been released yet is exactly because it needs work to make it "releasable". For a tool which is strictly used internally, I might take some short-cuts or make some compromises that I wouldn't want seen in any code I release to the world. I know FUCIT has hard-coded file paths, hard-coded usernames, pages which are not "built" but render using Grails scaffolding (and look pretty hideous), and all manner of bugs that I don't care about, or aren't serious enough to justify fixing right now. I'd want to fix all of that stuff before releasing that thing to the wild, just as a matter of professional pride. If I sat down and focused on it intently, I could probably get it into releasable form in a couple of weeks. But justifying that much work is hard to do right now.
Oh, and there's also no documentation, so that would need to be done.
Anyway, the point is, taking something internal and prepping it for widespread release can be a fairly substantial undertaking.