|Thread title||Replies||Last modified|
|/manage||8||20:24, 28 July 2010|
- VCS integration (including user permissions)
- Some UI mockups and work flow
- Need to convert old style groups, especially mediawiki&ext.
Just don't convert until the workflow has been thought out. It must be easily possible to see which groups require updating, i.e. have outdated caches, before having 500 or so groups that each need to be clicked before you know what needs to be done.
Yes I agree and that's the way it's going to be done. One more note:
- Command line alternative (at least non interactive)
We were also discussing having a 'show all' button so you can see all the changes at once for the groups in the list (with possible pagination if there are more than osme large number that your browser would choke on).
I still think there could be a fairly easy fix for this issue. I think we should approach this on 'per language' basis, as that's how translations work. As we already have filters for RC per language, we should have a special page that displays source and translation, as well as 'diff with previous version', if any, similar to 'review' mode of Special:Translate.
As most functionality to accomplish this is already present, I think this shouldn't take more than 12 hours to get done.
Hmm, you were talking '/manage', not review/translate mode, right? :)
Not sure if that's too helpful. We have, or at least will end up when growing, with multiple maintainers of supported products. While I do expect PageTranslation to be used a lot by others, I don't expect UI (source file based) translations to get as big a user as twn is elsewhere. Managing changes on a per-group level keeps things manageable, having 'all changes' will lead to unneeded errors with little efficiency gains, IMNSHO.
non-interactive is only acceptable if it skips conflicts only to show them later in interactive mode.