Hi, folks! Erik already answered this, but I wanted to add one bit.
Alex wrote:
What exactly is William going to be doing? [...]
This seems like it has the potential to introduce even more delays into something that people are already impatient for.
That's a very reasonable worry, but I don't think that will be the case.
Aaron will continue to do any coding[1], and my goal is to maximize the amount of time he can spend actually doing that. Partly by handling the communication with the community, and partly by turning that, plus Howie's usability recommendations, into a queue of clear, precise feature requests.
In addition, I'm hoping we can split the future work into a series of releases, rather than one big one. That will let us get the core part out as soon as possible. Not only will that benefit readers and the community, but feedback and data from real-world usage will help make future releases better.
William
[1] If I end up with extra cycles, I'd love to write some automated tests for this to hook into the existing test suite. The usage by the en and de wikis is divergent enough that it seems like there's a real risk of accidentally breaking something, and I'd rather have the computer do my worrying for me. I aim to stay out of the production code, though.