Re: pushing translated guides to docs.fedoraproject.org

There are publishing instructions in the Documentation Guide, but it occurs to me now that a few bits of the SOP that are missing : - publishing needs membership in the docs-writers and docs-publishers groups. Many translation team leads have been sponsored into these groups to allow publishing, and we are happy to sponsor more. - publish from the release branch, ie f20, not master. Commit your POs to make life easy if we need to republish. - after publishing, open your local copy of web.git and look it over before committing to that repo. In particular, check the menu structure. Strange things can happen. - As Chris said, there is currently no notification for when translations reach 100%, and you might want to publish sooner. It isn't uncommon to see code snippets or command output as untranslated strings, for example, since there's little reason to translate those. I might be able to get such notifications going, but it would require some consensus among the l10n group on what is considered "ready for publishing". Also, I like having translation team leads do the publishing because it gives them the opportunity to do a final review and build test. I can and do correct obvious markup issues, but I can only push changed strings back to projects I manage. I can't assess the language I'm correcting, just the markup structure.