The Wiki "Project" is probably parked in the foundation's org structure as a subplot of the infrastructure PMC.
The following enhancements are being worked on:
RSSFeeds include more data -Andy is going to make them more useful via including info now that he uses an aggregator and knows what people mean by that.
Done:
RSSFeeds - YES! We have rss feeds: here.
InterWiki now works.
"this page linked from" ala CLiki: http://www.cliki.net/mod_lisp - UseMod wiki already has this feature, just click on the title of the wiki page in the top right hand corner.
MailNotification - All wiki changes are sent to the wikidiffs@ list.
The following enhancements are suggested by the peanut gallery as things for SomeoneElse to do (which means you're probably just blowing hot air...consider contribution instead of gabbing):
- GIFs, JPGs, and PNGs, are automatically recognized. Maybe someone could put in a patch to automatically recognize SVg extensions and put down a embed or object tag.
We could impose some WikiDenotationalConventions on the pages so a tool like like works: http://c2.com/cgi/like?MaskingInterfaces
- RESTful interfaces [over SOAP or XMLRPC :-)] that enable automated content management.
- Now that interlinking works - a light hearted way to setup per-PMC Wiki - then we could solve the who's responsible oversight of this this content mystery.
'Printer View'. As well as a collaborative website, a wiki can usefully be used for writing a document as a collection of pages in a collaborative way. In the past, I've implemented this as a 'Printer View' (like e.g. http://www.xml.com/lpt/a/2003/01/02/xmlchar.html) by using the current page as a TOC for the document, and only presenting pages directly linked to from the TOC as part of the unified document (in exactly the order they are linked from the TOC). 'potential' links ('?' ones) aren't exported, other links out of the doc are linked to the live site. I'm sure you can do this kind of thing with UseModWiki but it'd take some heavy lifting to make it as good (eg export as PDF); my impl was java/xsl.
Version retrieval by timestamp. You run into a problem with microsites as described above when you have two versions of the same product; the manual moves on. One neat way of providing 'frozen' docs is to browse the site 'as if the date was XXXX' (much like the http://www.archive.org). Of course, in this view, the site is not editable, there are no 'potential' links, etc.
To submit patches, its best to post them to some server (in diff -u format) and provide a link or send them to infrastructure@apache.org.
Wikis have been around since 1995, and lots and lots of features have been discussed. WardsWiki has a surprisingly sparse feature set, yet is still one of the most popular ones. MeatballWiki has a lot of discussions on this topic, as well. The point is that just because something can be done, doesn't necessarily mean it should be. -- DevilsAdvocate
(printer view and version retreival) Its nearly always the case that projects need better documentation. Wikis help provide online documentation, but these two features (ab)use the wiki to provide better offline documentation. In case anyone's interested, the key trick in my implementation was to write the wiki text parser as a SAX2 XMLReader; this makes it trivial to implement hordes of wiki features as XSL-T, (these days jelly might be a better choice!) and removes a whole class of bugs to do with malformed HTML.
JustDoIt - Send me patches, I'll apply them. The source is listed on the ApacheWiki page.
Someone who wishes to remain anonymous (and I think I understand why) has sent me patches but boy this PERL stuff is a bitch. It aint working great.. I've blown WAY to much time on this. (for email notification...bah..)
Hey, give us some tips on UseMod:NextRelease for what you want to see included. Clearly the 1.0 code is ugly, so you might want to take a look at UseMod:UseModWiki/FuturePlanning as well. -- SunirShah
The WikiLogo at the top of each page is too long, or needs a newline after it so that medium length page titles don't trail off the right edge of the page.
JustDoIt - Send the patches (see ApacheWiki), it will be applied. The logo just refers to the apache logo..
Search for { { { $header = &ScriptLink($HomePage, "<$logoImage>"); } } } . Around that line you can either append a line break or a paragraph marker to $header or you can change the logo alignment. The choice and implementation are left as an exercise to the hacker, but I'm sure you can figure it out. 
-- SunirShah