> > Bram, what happens to Vim if you are suddenly incapacitated? Look at > > Exuberant Ctags: it's been in limbo for many months, since Darren > > Hiebert went AWOL. It seems like there's a lot of stuff that only you > > have the permissions to do. > > If my plain crashes then there might be a bit of a problem :-). With > Darren the problem also is that he is still there, just doesn't have > time to work on ctags. You can't take over a project if the author is > still there and doesn't release it. And it's not so easy to give away > your baby.
I wouldn't think of it as 'giving away your baby', more like 'sending it off to school'. To risk over-extending a metaphor (too late!), but you've got to let vim expand and grow through other tutors, other environments, other ideas.. Maybe, who knows, one day vim will grow up, find a nice IDE and settle down.. ;-) Well, ok, enough with the metaphors, but I think an apprentice vim maintainer/pumpking or two wouldn't hurt. You'd retain final control, but not be the sole focus for vim development. And as long as your apprentices were on the same wavelength as to where you'd want to go with vim, there's no reason why vim should stray from the vision that you've set for it. (plus, having dictatorial powers in the case of a disagreement is always a nice thing..) Ed
