Is there a proposed change for this task? Or something undesirable about the existing structure that we would like to address?

No one yet.

Perhaps changing this for example

https://fedoraproject.org/wiki/Category:Test_Cases

Installer
Networking
Desktop or Gnome KDE XFCE
etc..

Also move to numeric format for test cases under these category's

Use the Test Case number when reporting if the test case was succesful or not

See here at the bottom of that page.

https://fedoraproject.org/wiki/User:Johannbg/Draft/QA/Test_Days/Features/EXT4

This simplifies reporting test cases results a great deal and does not clutter the wiki

Perhaps changing this for example
https://fedoraproject.org/wiki/Category:Test_Cases
Installer Networking Desktop or Gnome KDE XFCE etc..

What would need to change here ... just adding more content?

Also move to numeric format for test cases under these category's

I've done this in the past and this is great for a system to use internally (e.g. database id's) ... but proved very poor for a human to remember and pass around numbers. I'd like to continue allowing test case authors to name their tests according to mediawiki guidelines. But provide them a collection of categories (as you noted above) to help organize their cases.

A test cases number also changes through the life of a product. It may be test case 0004 in Fedora11, but test case 0014 in Fedora12. The test case number is often assigned when a test case is linked into a specific test plan for execution. That would be a good time to begin numbering the test cases (as a wiki table with links to the test cases).

Any updates here, I'm not sure if this ticket is a request for numerical test cases, or for cleaning up the Category:Test_Cases. The numerical test case option is entirely up to the tester and maintainer group creating the test cases, so I don't feel the need to mandate a particular format there. As for cleaning up the Category:Test_Cases, I've slowly been moving things into sub-categories, but that's a worthy cleanup effort to track if desired.

This cleanup procedure is more or less active task.. We generally improve pages/cases as things evolve I think. So I propose we leave this one open and revisited per release cycle/milestone. What do you think?

Unless there is specific action required, I'd propose closing the ticket and opening specific tickets under the wiki component as the need/work comes available.

On a more general note, what is involved in "cleanup" are there guidelines or procedures to follow? Creating a ticket to define those areas would be worthwhile.

You mean something like I proposed in ticket 8 or could be added to ticket 8 ?

I think James was on the right track here and we should just close this ticket. Tickets work best for tracking specific tasks which are documented and then implemented and the ticket closed, not for an ongoing, broad 'conceptual' task.