)]}'
{"doc/source/drivers.rst":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"8fddd4bf7e521fa4f941a4fd85c37e053e987563","unresolved":false,"context_lines":[{"line_number":579,"context_line":""},{"line_number":580,"context_line":"This document describes a consistent naming scheme for Zuul jobs."},{"line_number":581,"context_line":"The goal is to give job developer and reviewers of jobs a common"},{"line_number":582,"context_line":"document as reference."},{"line_number":583,"context_line":""},{"line_number":584,"context_line":".. warning:: This is a living document, it may get updates as our"},{"line_number":585,"context_line":"             use of Zuul changes over time."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1fa4df85_4c1faf5a","line":582,"updated":"2020-03-04 20:14:00.000000000","message":"Let\u0027s add a variant of the following from the zuulv3 file you removed here:\n\nNote that all OpenStack projects share a single namespace for job\nnames, so we have established some guidelines detailed in\n:ref:`v3_naming` for how to name jobs.  Adhere to these so that we may\navoid collisions between jobs defined in various repositories.","commit_id":"ff0093e8a661cd4439e63e7365186946c7c77b25"}]}