)]}'
{"reference/incubation-integration-requirements.rst":[{"author":{"_account_id":3108,"name":"daisy-ycguo","email":"guoyingc@cn.ibm.com","username":"daisy-ycguo"},"change_message_id":"9e2665539ee4a72b406e6d98af470f79a1a7e35b","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  configuration reference information for all options"},{"line_number":139,"context_line":"* Project should have a proven history of providing user support (on the"},{"line_number":140,"context_line":"  openstack@ mailing list and on Ask OpenStack)"},{"line_number":141,"context_line":"* Project must have translation support enabled for user-facing error"},{"line_number":142,"context_line":"  messages and deployer-facing log messages, following the guidelines"},{"line_number":143,"context_line":"  of the I18nTeam_ and `oslo.i18n`_. The translation export/import"},{"line_number":144,"context_line":"  jobs must be running properly, and patches with translation updates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_1d09eb2b","line":141,"updated":"2014-06-05 02:29:54.000000000","message":"Suggest to remove \"error\". Just use \"user-facing messages\".","commit_id":"d3c2b8cd0d22a3a22ae362f1daa8310408274ed1"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"40b06f69d6763243300b69e64a641dc75f2e17a9","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  configuration reference information for all options"},{"line_number":139,"context_line":"* Project should have a proven history of providing user support (on the"},{"line_number":140,"context_line":"  openstack@ mailing list and on Ask OpenStack)"},{"line_number":141,"context_line":"* Project must have translation support enabled for user-facing error"},{"line_number":142,"context_line":"  messages and deployer-facing log messages, following the guidelines"},{"line_number":143,"context_line":"  of the I18nTeam_ and `oslo.i18n`_. The translation export/import"},{"line_number":144,"context_line":"  jobs must be running properly, and patches with translation updates"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_9b95e734","line":141,"in_reply_to":"1ae5cdf2_1d09eb2b","updated":"2014-06-05 18:53:07.000000000","message":"Done","commit_id":"d3c2b8cd0d22a3a22ae362f1daa8310408274ed1"},{"author":{"_account_id":3108,"name":"daisy-ycguo","email":"guoyingc@cn.ibm.com","username":"daisy-ycguo"},"change_message_id":"9e2665539ee4a72b406e6d98af470f79a1a7e35b","unresolved":false,"context_lines":[{"line_number":145,"context_line":"  must be reviewed and accepted by the reviewers when submitted by"},{"line_number":146,"context_line":"  those jobs. If translators have not started processing the strings"},{"line_number":147,"context_line":"  for a project, that should not block graduation if all of the other"},{"line_number":148,"context_line":"  translation requirements are met."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":".. _I18nTeam: https://wiki.openstack.org/wiki/I18n"},{"line_number":151,"context_line":".. _oslo.i18n: http://docs.openstack.org/developer/oslo.i18n/"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_bd455744","line":148,"updated":"2014-06-05 02:29:54.000000000","message":"Suggest to change the last sentence to: Unfinished translations would not block graduation if all of the other translation requirements are met.","commit_id":"d3c2b8cd0d22a3a22ae362f1daa8310408274ed1"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"40b06f69d6763243300b69e64a641dc75f2e17a9","unresolved":false,"context_lines":[{"line_number":145,"context_line":"  must be reviewed and accepted by the reviewers when submitted by"},{"line_number":146,"context_line":"  those jobs. If translators have not started processing the strings"},{"line_number":147,"context_line":"  for a project, that should not block graduation if all of the other"},{"line_number":148,"context_line":"  translation requirements are met."},{"line_number":149,"context_line":""},{"line_number":150,"context_line":".. _I18nTeam: https://wiki.openstack.org/wiki/I18n"},{"line_number":151,"context_line":".. _oslo.i18n: http://docs.openstack.org/developer/oslo.i18n/"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1ae5cdf2_fba50ba2","line":148,"in_reply_to":"1ae5cdf2_bd455744","updated":"2014-06-05 18:53:07.000000000","message":"Done","commit_id":"d3c2b8cd0d22a3a22ae362f1daa8310408274ed1"},{"author":{"_account_id":2889,"name":"Aeva Black","email":"aeva.online@gmail.com","username":"tenbrae"},"change_message_id":"4d38df8c1c309cceb8c3b6436287e3115e0b977f","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  configuration reference information for all options"},{"line_number":139,"context_line":"* Project should have a proven history of providing user support (on the"},{"line_number":140,"context_line":"  openstack@ mailing list and on Ask OpenStack)"},{"line_number":141,"context_line":"* Project must have translation support enabled for user-facing and"},{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_0098031a","line":141,"updated":"2014-06-17 22:15:36.000000000","message":"Everything else in this proposal looks good to me except the wording of\n\n  \"enabled for user-facing and deployer-facing messages\"\n\nI recall some discussions about whether or not we should be translating errors in log files, as this makes troubleshooting (by searching google) more difficult for non-english locales.\n\nI just checked the I18n wiki page and didn\u0027t see any suggested guidelines regarding this. I would like to see a statement from that team about this before we encode it in policy. As I understand it right now, this is left up to each project.\n\nIf there was a decision reached in the past and I missed reading it, please point me to it.","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"3668fe6b826b7eff23aab79f1eb3d44e62ff546f","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  configuration reference information for all options"},{"line_number":139,"context_line":"* Project should have a proven history of providing user support (on the"},{"line_number":140,"context_line":"  openstack@ mailing list and on Ask OpenStack)"},{"line_number":141,"context_line":"* Project must have translation support enabled for user-facing and"},{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_7978f18f","line":141,"in_reply_to":"1ae5cdf2_0098031a","updated":"2014-07-08 19:17:14.000000000","message":"The translation guidelines are in the oslo.i18n documentation where we expected developers using that library to go to look for them: http://docs.openstack.org/developer/oslo.i18n/guidelines.html\n\nThe deployers can configure their logs to use as many different languages as they want, so simple messages can be read directly and confusing messages have the English available for searching.\n\nWe have had discussions of this at the last 3 summits. The easiest place for me to provide a list of the history is this in-progress review where I\u0027m adding it to the oslo.i18n documentation: https://review.openstack.org/#/c/102028/","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"17f3e9b6b784861c2d0058235074ecd24695c8d0","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  configuration reference information for all options"},{"line_number":139,"context_line":"* Project should have a proven history of providing user support (on the"},{"line_number":140,"context_line":"  openstack@ mailing list and on Ask OpenStack)"},{"line_number":141,"context_line":"* Project must have translation support enabled for user-facing and"},{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_610a4121","line":141,"in_reply_to":"baada198_0dd8de51","updated":"2014-07-21 15:16:48.000000000","message":"\u003e I would be very curious to have a pointer to how this specific aspect of the argument was lost?\n\nI tend to agree with this viewpoint, but the argument was lost because feedback from some of the translator communities was that log messages in their native language would be more useful, even given the google issue.\n\nThis is about allowing the translators give their users the *option* of having log messages be translated. Personally, I\u0027m skeptical, but it is the translators that bear the majority of the burden hear (i.e. translating the log messages) and I\u0027m happy to trust they know their users best.\n\n(Sorry I don\u0027t have a reference to where this feedback was given)","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"269917c5ea523aa836731ce47a9cd9deb47f5952","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  configuration reference information for all options"},{"line_number":139,"context_line":"* Project should have a proven history of providing user support (on the"},{"line_number":140,"context_line":"  openstack@ mailing list and on Ask OpenStack)"},{"line_number":141,"context_line":"* Project must have translation support enabled for user-facing and"},{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_a827d9b4","line":141,"in_reply_to":"baada198_610a4121","updated":"2014-07-21 16:41:37.000000000","message":"I think a lot of the discussion happened on the openstack-dev mailing list and at summits discussing the blueprint. Here are some reference links:\n\nhttp://lists.openstack.org/pipermail/openstack-dev/2014-February/026136.html\n\nhttps://blueprints.launchpad.net/oslo/+spec/log-messages-translation-domain\n\nI think the discussion acknowledges that there is still the possibility of user-facing messages not being translated. So how about this wording for the sentence:\n\nProject must have translation support enabled that follows the guidelines of the I18nTeam_ and `oslo.i18n`_. Currently that guideline considers user-facing messages a must-have, and debug messages for operators and developers a secondary priority. \n\n---\nI\u0027m using this thread: http://lists.openstack.org/pipermail/openstack-dev/2014-February/026089.html as a reference.","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"c5e9f7fc98cf762477264f1eb28905cd6cb72574","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  configuration reference information for all options"},{"line_number":139,"context_line":"* Project should have a proven history of providing user support (on the"},{"line_number":140,"context_line":"  openstack@ mailing list and on Ask OpenStack)"},{"line_number":141,"context_line":"* Project must have translation support enabled for user-facing and"},{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_de6483e8","line":141,"in_reply_to":"baada198_610a4121","updated":"2014-07-22 13:43:00.000000000","message":"This may be straying into too heavyweight and/or intrusive a solution to apply retrospectively, but one approach I\u0027ve seen used sucessfully from the outset before was to allocate an error ID (combining major and minor codes, the latter partitioning the ID space by component, the former by failure mode) for each log message of severity warning or higher.\n\nThis approach allows the numeric ID to be primary searchable key (retaining the strong \"google juice\" as Chris puts it) while the l10n\u0027d natural language component is then purely for human consumption.\n\nSuch numeric error codes are fairly widely used, e.g. by mysql:\n\n  http://dev.mysql.com/doc/refman/5.5/en/error-messages-server.html","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"aaed9f9a9156af9d4032675558fc25bf4eba5eaa","unresolved":false,"context_lines":[{"line_number":138,"context_line":"  configuration reference information for all options"},{"line_number":139,"context_line":"* Project should have a proven history of providing user support (on the"},{"line_number":140,"context_line":"  openstack@ mailing list and on Ask OpenStack)"},{"line_number":141,"context_line":"* Project must have translation support enabled for user-facing and"},{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"}],"source_content_type":"text/x-rst","patch_set":2,"id":"baada198_0dd8de51","line":141,"in_reply_to":"baada198_7978f18f","updated":"2014-07-21 14:05:25.000000000","message":"I fear this may be too late but:\n\nI think the \"by searching google\" use case is of absolutely critical importance for any log message and simply _allowing_ the log messages to be in different languages will weaken the google juice of any single message, making solutions more difficult to find. A log message has two important functions: a) it identifies that some thing went wrong b) it identifies the context of that happening. The \"thing\" in a) is solely an identifier or pointer for finding more info somewhere else, it hardly has need to be meaningful in a multitude of language: it is a series of symbols that say \"X happened here\".\n\nUser-facing messages should not come from logging. It may be that an exceptional situation (which is logged) will need to cause a user facing message, but that message should be in the UI, not (just) the log message itself.\n\nIt is far more important that log messages be universal and repeatable in different environments. Otherwise we are creating a support nightmare for deployers and for developers.\n\nI would be very curious to have a pointer to how this specific aspect of the argument was lost?","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"a1dba0905ce25af0b565bb7cc125304f13457c68","unresolved":false,"context_lines":[{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"},{"line_number":145,"context_line":"  accepted by the reviewers when submitted by those jobs. Unfinished"},{"line_number":146,"context_line":"  translations will not block graduation if all of the other"},{"line_number":147,"context_line":"  translation requirements are met."},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_2277e803","line":145,"updated":"2014-06-09 21:52:10.000000000","message":"Just wondering about the \"must be accepted\" language here, seems to override the discretion of the core teams.\n\nHow about a looser requirement:\n\n  \"patches with translation updates must receive timely attention\n   from the core team when submitted by those jobs.\"","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4542ca65c1f02352d2db546657623b92fd83721a","unresolved":false,"context_lines":[{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"},{"line_number":145,"context_line":"  accepted by the reviewers when submitted by those jobs. Unfinished"},{"line_number":146,"context_line":"  translations will not block graduation if all of the other"},{"line_number":147,"context_line":"  translation requirements are met."},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_a38bcc66","line":145,"in_reply_to":"1ae5cdf2_2277e803","updated":"2014-06-10 21:01:02.000000000","message":"I want to make it clear that a team cannot say \"we reviewed it\" but then never merge the patch.","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"7606b67b7156a56c60f00e1bc50993f9b5c1ff80","unresolved":false,"context_lines":[{"line_number":142,"context_line":"  deployer-facing messages, following the guidelines of the I18nTeam_"},{"line_number":143,"context_line":"  and `oslo.i18n`_. The translation export/import jobs must be running"},{"line_number":144,"context_line":"  properly, and patches with translation updates must be reviewed and"},{"line_number":145,"context_line":"  accepted by the reviewers when submitted by those jobs. Unfinished"},{"line_number":146,"context_line":"  translations will not block graduation if all of the other"},{"line_number":147,"context_line":"  translation requirements are met."},{"line_number":148,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1ae5cdf2_e3a4f4ba","line":145,"in_reply_to":"1ae5cdf2_a38bcc66","updated":"2014-06-10 21:06:23.000000000","message":"OK, I see that vague handwaveyness around timeliness would not suffice in that case.\n\nFair enough, the original wording makes more sense to me now.","commit_id":"5095975117b3e46f2ecd14840cff7313a54045ed"}]}
