3 ms·
Can anyone comment on how much resources are spent on making something 'releasable'? Not just packaging and the initial commit/support, but spending the time to
by bluedino 14y ago
Can anyone comment on how much resources are spent on making something 'releasable'? Not just packaging and the initial commit/support, but spending the time to make it generic enough to be useful to other users.
- analog 14y agoIn my experience it varies quite a lot. From maybe 5% to 100% or more of initial time spent. Depends on the problem the code is solving and also how good the code was in the first place.
- DannyBee 14y agoNote: these are my own views :) It varies depending on your infrastructure and whether the issues were thought about at the time of design. For example, in Google's case, there are plenty of pieces of software that would be insane to open source (time-wise, it would take many years to come up with something someone else could use). On average though, if they had planned on open sourcing it, so that there is some chance it's reusable, someone is probably still spending at least a few weeks, maybe a few months, to make it useful to others.
- mindcrime 14y agoIt'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.
- caseysoftware 14y agoThat's just the code aspect. Most of the time, when you build something "on the clock" and/or with company resources, they own it. Therefore, you are probably not allowed to make licensing decisions or release it without clearing it through proper channels. Regardless of what you think or even the nebulous "company" thinks, at the end of the day, someone - probably a senior exec or legal counsel - will have to authorize it. I think this article does a huge disservice in not noting that.