I'm guessing that there are a few people who are really working hard on this, but a lot of your team is in wait mode. If you could give us your idea of the path to completion, then others could get to work. We could shift from a sequential effort to a parallel effort. In another post, you asked everyone to identify obsolete wiki articles. That's too broad. But if you said "Twodogs, go through all the Telecom wiki articles and identify the obsolete ones", then I could say "yes, boss".
So, even though we might not have the wiki structure in place yet, I think we should identify who will be responsible for what chapters. That's what I was getting at in my previous post. I don't care if you use the timeline I suggested - maybe someone else has a better idea. I just think that this is a big job and we need to get lots of people working on it.
Bongo, give us your idea of what we are embarking upon. I suggested a sequence a few weeks ago where you would be the supervisor, and the rest of us would be the worker bees. It also seems like you are asking for us to do things that I thought would come much later (rewrites and new content). I think the sequence below makes your life a whole lot easier and would get us up and running faster.
Create the new wiki structure/framework (programming skills required)
Identify the chapter leads (maybe one or two chapters per volunteer)
Have each chapter lead fill out his chapter by cut/paste from existing content. The first level would come mainly from the manual. Second and third levels would mostly be wiki articles. This would be more of a sorting effort instead of a huge rewrite (which could take forever).
Release the new wiki. Beers for everyone. There would not be much new content, but at least people could finally find what they are looking for (our biggest problem).
Improve/Maintain. Once we have everything properly sorted and organized, we will discover many areas for improvements. This is where we can draft rewrites. The chapter leads can start tracking down the experts and asking for updates (making every effort to avoid bugging the devs).