0) Best thing is not to get to this point in the first place! It was necessary from the outset to just let 100 things proceed and see what sticks. Now I think we can gently move towards more focus. So I'd hope someone doesn't make up a big patch without it being clear there's a path to commit it quickly. And that's why some nominal owners are going to be useful.
1) I'd say don't mothball stuff for a long time. I'm not really touching anything that seems to have had any activity in 6 months. That mitigates this a lot. 2) Finding an old issue is still possible in JIRA of course, but might not be obvious. Old patches are probably not applicable anymore, so the use may be somewhat limited. So maybe this too means it's not such a big deal in practice. That is, I doubt we're actually going to have the same work happen once, and fail, twice, and fail, etc. with nobody remembering. On Fri, Dec 11, 2009 at 9:36 PM, Ted Dunning <[email protected]> wrote: > I am also unclear on how to do this. > > Anybody have good suggestions? > > On Fri, Dec 11, 2009 at 1:33 PM, Jake Mannix <[email protected]> wrote: > >> I'm not sure of the right way to avoid redoing work again and again, yet >> still avoid cluttering our codebase with a bunch of unsupported, unfinished >> code. >> > > > > -- > Ted Dunning, CTO > DeepDyve >
