2010/2/7 David Gerard dgerard@gmail.com:
The problem is that doing this before the feature that uses it is in place renders categorisation on Commons even more useless. What this will mean is that you will be requiring a direct reduction in the usability of the wiki content before *possibly* implementing a feature.
In practice, the difference between this and saying "No, never" is telling people to do work that you know can't happen.
There's no reason why it couldn't be the other way around: an intersection feature could be written and deployed *first*, *then* the category trees on Commons would be gradually migrated to the new system. Issues like nonsense results for automatic flattening could be migitated by disabling features or making them less visible.
Please leave commons-l in the cc: this time, thanks.
I did on my earlier reply, and I got a bounce from commons-l-owner saying my message was rejected because I'm not subscribed to commons-l. I'm not going to subscribe to that list, so I left the Cc: commons-l out this time.
Roan Kattouw (Catrope)