I still don't understand why Publican can't just be changed to generate all the translated guides from the same SRPM like kde-l10n is doing.

In reply to comment #1:

It could. However, this means that anytime a new translation shows up, or changes are made to a translation, ALL users with any translation get an update, even if their content doesn't change any.

If folks think thats worth the pain we can ask that they do that... There is no perfect answer here, but making people download packages where there are no changes seems a poor solution to me.

In case my opinion counts for anything, I'm opposed to allowing packages into the distribution without a proper review. If the new packages are substantially similar to existing packages then the review process should be relatively quick. Also, if the proposed policy were already in place, we'd have fedora-security-guide-es-ES in the distro with a guidelines violation, because it has non-English Symmary: and %description tags.

Package review is good. The fact that we may have manpower issues is no reason to abandon the process. And lately the manpower issues have been less prominent, to the point that we are at a queue length not seen since the merge reviews were first dumped onto the queue and are actually able to give some attention to essentially all new submissions within a couple of weeks.

Replying to [comment:3 tibbs]:
But there is no real reason why they need to be in English if they are available in English in the English version. The SPEC files aren't similar... they are exactly the same (as far as the technical information goes). Each package is built from the same SPEC with the exception of translations being used where they would be helpful. Publican generates the SPEC based on standard information that is located in the book that isn't changed by the translation.

If you don't speak English then an English description is NOT helpful. But this is being suggested in a different ticket so I won't further this conversation here.

There really isn't a reason to put both on the ticket unless you speak the other language as you wouldn't be able to verify that the translation is correct.

I would be against packages without review as well; furthermore, I do wonder about an end game if we have 50 docs each translated into 30 languages.

I guess because of the conversation here, I never put this on the agenda. Putting it there now.

Translated publican documents may not bypass review.