)]}'
{"doc/source/code-and-documentation/elastic-recheck.rst":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"1634d342927cd4225b0b93b9f743a539f66e75d9","unresolved":false,"context_lines":[{"line_number":30,"context_line":"leave comments in gerrit and in IRC when it has found a known bug fingerprint"},{"line_number":31,"context_line":"in a failure."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"elastic-recheck is built on top of an ELK (`Elastic Search"},{"line_number":34,"context_line":"\u003chttps://github.com/elastic/elasticsearch\u003e`_, `Logstash \u003chttps://github.com/elastic/logstash\u003e`_,"},{"line_number":35,"context_line":"`Kibana \u003chttps://github.com/elastic/kibana\u003e`_) stack where we use Logstash to store all logs from CI jobs in an"},{"line_number":36,"context_line":"Elastic Search cluster. We also host a `Kibana dashboard \u003chttp://logstash.openstack.org/\u003e`_ which can be used"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9fdfeff1_897c4dec","line":33,"range":{"start_line":33,"start_character":44,"end_line":33,"end_character":58},"updated":"2019-02-04 17:18:32.000000000","message":"So like here, I hope nobody translates \"Elastic Search\".","commit_id":"4bece76e60db2a0de746ec3a189724ab2b9c2b0b"}],"doc/source/code-and-documentation/using-gerrit.rst":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"00ef046c23b7fe4b76a0f2bad0e26d02e09d9336","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Reviewing changes is often suggested as a way to get started on a"},{"line_number":133,"context_line":"project. Whether this is how you choose to get started or not, it\u0027s"},{"line_number":134,"context_line":"an important community activity. See `How to Review Changes the"},{"line_number":135,"context_line":"OpenStack Way"},{"line_number":136,"context_line":"\u003chttps://docs.openstack.org/project-team-guide/review-the-openstack-way.html\u003e`_"},{"line_number":137,"context_line":"for more detailed guidance on when to use which votes"},{"line_number":138,"context_line":"on a change review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_38aecd98","line":135,"updated":"2019-02-04 15:11:22.000000000","message":"I\u0027m concerned about changing these. The link text used to be the title of the target doc. Now, if it gets translated, it could be... weird.","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"4b02b30c807c816930d5b54d6f03f76c1dd09c40","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Reviewing changes is often suggested as a way to get started on a"},{"line_number":133,"context_line":"project. Whether this is how you choose to get started or not, it\u0027s"},{"line_number":134,"context_line":"an important community activity. See `How to Review Changes the"},{"line_number":135,"context_line":"OpenStack Way"},{"line_number":136,"context_line":"\u003chttps://docs.openstack.org/project-team-guide/review-the-openstack-way.html\u003e`_"},{"line_number":137,"context_line":"for more detailed guidance on when to use which votes"},{"line_number":138,"context_line":"on a change review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_63bcaa6c","line":135,"in_reply_to":"9fdfeff1_38aecd98","updated":"2019-02-04 16:09:10.000000000","message":"It\u0027s marked for translation and might get translated, see http://git.openstack.org/cgit/openstack/contributor-guide/tree/doc/source/locale/de/LC_MESSAGES/doc-code-and-documentation.po#n889","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"1634d342927cd4225b0b93b9f743a539f66e75d9","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Reviewing changes is often suggested as a way to get started on a"},{"line_number":133,"context_line":"project. Whether this is how you choose to get started or not, it\u0027s"},{"line_number":134,"context_line":"an important community activity. See `How to Review Changes the"},{"line_number":135,"context_line":"OpenStack Way"},{"line_number":136,"context_line":"\u003chttps://docs.openstack.org/project-team-guide/review-the-openstack-way.html\u003e`_"},{"line_number":137,"context_line":"for more detailed guidance on when to use which votes"},{"line_number":138,"context_line":"on a change review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_89f3ed73","line":135,"in_reply_to":"9fdfeff1_63bcaa6c","updated":"2019-02-04 17:18:32.000000000","message":"No, this is exactly my point. If we leave it the way it was, and someone translates it, it\u0027ll break the build and they\u0027ll have to fix it. Whereas if we change it like this, they can translate it with impunity, and then we have link text that\u0027s supposed to be the title of the target doc, translated so it\u0027s not that anymore.\n\nWe *want* the build to break if someone tries to translate this title.","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"c80fef06680dffa1a421b15c57a66e62560fc7c6","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Reviewing changes is often suggested as a way to get started on a"},{"line_number":133,"context_line":"project. Whether this is how you choose to get started or not, it\u0027s"},{"line_number":134,"context_line":"an important community activity. See `How to Review Changes the"},{"line_number":135,"context_line":"OpenStack Way"},{"line_number":136,"context_line":"\u003chttps://docs.openstack.org/project-team-guide/review-the-openstack-way.html\u003e`_"},{"line_number":137,"context_line":"for more detailed guidance on when to use which votes"},{"line_number":138,"context_line":"on a change review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_c9a6d554","line":135,"in_reply_to":"9fdfeff1_89f3ed73","updated":"2019-02-04 17:21:15.000000000","message":"That\u0027s of course assuming that the target itself is not translated. Which we really have no way to know or detect here in any case, so we have no choice but to link to the English version.","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"},{"author":{"_account_id":17765,"name":"Frank Kloeker","email":"f.kloeker@telekom.de","username":"eumel8"},"change_message_id":"f848ad440548f872c7fb9b6fa6e0ab07e6174e23","unresolved":false,"context_lines":[{"line_number":132,"context_line":"Reviewing changes is often suggested as a way to get started on a"},{"line_number":133,"context_line":"project. Whether this is how you choose to get started or not, it\u0027s"},{"line_number":134,"context_line":"an important community activity. See `How to Review Changes the"},{"line_number":135,"context_line":"OpenStack Way"},{"line_number":136,"context_line":"\u003chttps://docs.openstack.org/project-team-guide/review-the-openstack-way.html\u003e`_"},{"line_number":137,"context_line":"for more detailed guidance on when to use which votes"},{"line_number":138,"context_line":"on a change review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_4f5bae53","line":135,"in_reply_to":"9fdfeff1_c9a6d554","updated":"2019-02-05 19:29:10.000000000","message":"I think thats a learning process. We now care about more on translation errors, which is pretty good. And translators must to be carefull with internal link references. A good thing is always to use proper names for links, so it\u0027s untranslatable at the end.","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"00ef046c23b7fe4b76a0f2bad0e26d02e09d9336","unresolved":false,"context_lines":[{"line_number":157,"context_line":""},{"line_number":158,"context_line":".. image:: /_assets/using-gerrit/regular-reviewer.png"},{"line_number":159,"context_line":""},{"line_number":160,"context_line":"`-1 \u003chttps://docs.openstack.org/project-team-guide/review-the-openstack-way.html#code-review-minus-1\u003e`_: This patch needs further work before it can be merged."},{"line_number":161,"context_line":"A -1 is usually given when the reviewer sees some issue that needs to be"},{"line_number":162,"context_line":"fixed before the patch can be merged. The issues the author needs to"},{"line_number":163,"context_line":"address would, ideally, have inline comments posted on them unless there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_98757935","line":160,"updated":"2019-02-04 15:11:22.000000000","message":"This was better as it was. That way, if translators tried to translate \"-1\" (not sure how, but...) it would break the build. But \"-1\" has special meaning and should remain unchanged. With it set up this way, they could \"translate\" it with impunity and we would end up with something in the translated doc that didn\u0027t necessarily make sense.","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"4b02b30c807c816930d5b54d6f03f76c1dd09c40","unresolved":false,"context_lines":[{"line_number":157,"context_line":""},{"line_number":158,"context_line":".. image:: /_assets/using-gerrit/regular-reviewer.png"},{"line_number":159,"context_line":""},{"line_number":160,"context_line":"`-1 \u003chttps://docs.openstack.org/project-team-guide/review-the-openstack-way.html#code-review-minus-1\u003e`_: This patch needs further work before it can be merged."},{"line_number":161,"context_line":"A -1 is usually given when the reviewer sees some issue that needs to be"},{"line_number":162,"context_line":"fixed before the patch can be merged. The issues the author needs to"},{"line_number":163,"context_line":"address would, ideally, have inline comments posted on them unless there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_43bba671","line":160,"in_reply_to":"9fdfeff1_98757935","updated":"2019-02-04 16:09:10.000000000","message":"will change those back","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"}],"doc/source/common/introduction.rst":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"00ef046c23b7fe4b76a0f2bad0e26d02e09d9336","unresolved":false,"context_lines":[{"line_number":12,"context_line":"Private cloud covering various use cases including Enterprise and Telecom."},{"line_number":13,"context_line":"The main focus is on Infrastructure as a Service (IaaS) cloud and additional"},{"line_number":14,"context_line":"services built upon IaaS."},{"line_number":15,"context_line":"The Technical Committee maintains an evolving `vision for OpenStack"},{"line_number":16,"context_line":"clouds"},{"line_number":17,"context_line":"\u003chttps://governance.openstack.org/tc/reference/technical-vision.html\u003e`_"},{"line_number":18,"context_line":"describing the overall design scope for an OpenStack cloud and the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_58b631df","line":15,"updated":"2019-02-04 15:11:22.000000000","message":"++","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"}],"doc/source/organizations/index.rst":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"00ef046c23b7fe4b76a0f2bad0e26d02e09d9336","unresolved":false,"context_lines":[{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Having engineers spending more time upstream helps everyone by providing"},{"line_number":62,"context_line":"continuous input and feedback to tasks that you set as high priority."},{"line_number":63,"context_line":"But it\u0027s more then that, OpenStack relies on `peer review"},{"line_number":64,"context_line":"\u003chttps://governance.openstack.org/tc/reference/principles.html#we-value-constructive-peer-review\u003e`_."},{"line_number":65,"context_line":"From landing code to its governance, to function the project needs"},{"line_number":66,"context_line":"people in the community reviewing."}],"source_content_type":"text/x-rst","patch_set":3,"id":"9fdfeff1_78bbf5c3","line":63,"updated":"2019-02-04 15:11:22.000000000","message":"++","commit_id":"c3b40b9f1a70b1dd9f9415e500d60be02f95f4df"}]}