I consider it important for old urls to still work after the move. If this is not possible, I'd suggest we just ignore the "wrong" url.

minor thing to keep in mind when/if doing this: when changing the wiki name from "jakarta-lucene" to something else, that something should be "java-lucene" or "lucene-java" ... but it really shouldn't be "lucene" just inc ase we ever want to set up a central wiki for the Lucene PMC (not subproject specific)

To summarize: someone should file an issue in the Infrastructure Jira requesting that the jakarta-lucene wiki be renamed "lucene-java", and for links to pages in http://wiki.apache.org/jakarta-lucene/ to redirect to the corresponding pages in http://wiki.apache.org/lucene-java/.

something to consider...

is it worth migrating to cwiki.apache.org ?

http://cwiki.apache.org/confluence/display/CWIKI/Index

http://www.nabble.com/Created%3A-%28LUCENE-805%29-New-Lucene-Demo-tf3234570.html#a9131628

OK, https://issues.apache.org/jira/browse/INFRA-1173 has been resolved. I will update the main links when I get a chance. It is redirecting just fine. New location is http://wiki.apache.org/jakarta-lucene/

oops, good catch by Steve Rowe, the new location is actually properly specified on the issue as http://wiki.apache.org/lucene-java/

I will commit the updates shortly to the documentation.

OK, I have reorganized the Front Page wiki a bit. Hopefully a little easier to navigate, a little more like Solr. Also added a UseCases section where it would be cool if people donated how they solved a particular problem in Lucene.

Moved some of the old planning pages to the Archives section.

Still would like to know how to set it up to send edit notifications to the commit list. Is this an Infrastructure issue or is it something that can be handled by either the PMC or the committers?

Well, individuals can get commits themselves by registering and then, under UserPreferences, specifying .* for Subscribed wiki pages.

One can imagine setting up a pseudo-account on the wiki to represent the commit list, using the commit list as the e-mail address, and then subscribing. At least one issue there is that you can ask to have your info sent to you (including a link that allows you to change your password), and that's would go to the whole list.

1) at the moment, the old URLs are still working, these should probably be issuing 301 redirects so that Search Engines update to point to the new URLs (instead of different competing URLs with the same content both getting indexed)...

http://wiki.apache.org/jakarta-lucene/LuceneFAQ

2) on the issue of having updates sent to the commit list, this is currently working for Solr, and we don't have any pseudo-account setup monitoring the pages so there must be some lower level way to configure this ... consulting with infra may be wise
(you can tell by looking at the general info for each page: http://wiki.apache.org/solr/FAQ?action=info&general=1 )

Requested that infrastructure change the notification email for the wiki

Change notifications are now being sent to java-commits per INFRA-1197

I think I am more or less happy with the changes at this point and am going to close this and specific issues w/ the wiki can be brought up with new issues.