Over the past few weeks I've realised that I've completely lost all enthusiasm for OpenGuides. This is a bad thing, and it needs fixing. Part of the problem is that I'm really not very well right now, and I could very much do with handing off some of my responsibilities.

The thing that I'm finding hardest at the moment is being the release manager/kwalitee assurer/whatever for OpenGuides. There are several people with CVS commit rights, and that means that before I make a release I have to make sure of a whole pile of things, for example that people's changes work smoothly together, that nobody is going off in a completely bogus direction, that implementation decisions are made sensibly, that the code is no more complicated than is necessary to get the job done, that documentation is kept up to date, that new code is thoroughly tested, and that old tests still pass. And so on.

I let 0.41 escape with a failing test, and this is yet another indicator that I'm getting tired. I need to pass on overall responsibility for OpenGuides to someone else, at least for a couple of months. However this leaves me with a problem - who?

It seems to me that although there are several people connected with the project who are exceedingly enthusiastic about OpenGuides, and likewise several people who I feel could take this task over from me, these groups don't overlap at all. In other words, I don't think any of the people who are likely to want to take over from me are quite ready for it just yet, and I don't think any of the people who could handle the job are likely to both want it and have time to do it.

(I'm not going to get into an argument with anyone over whether they're up to this task. Please trust my judgement. However if you think you could do it and you think I've overlooked you solely due to underestimating your enthusiasm for OpenGuides or free time to work on it, please drop me a private mail.)

So it looks like we're probably going to have to start trying to recruit someone who's not currently hooked on OpenGuides - find somebody competent and *get* them hooked. Unless one of you clever people can come up with another solution.

Comments and discussion welcomed and encouraged - the sooner we start sorting this out the better, both for me and for the project.

Kake