)]}'
{"reference/incubation-integration-requirements":[{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"fd22975be5fe48437b5e7d5849aa2f70e645562b","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"* Scope"},{"line_number":11,"context_line":"** Project must have a clear and defined scope which, in turn, represents"},{"line_number":12,"context_line":"   a measured and obvious progression for OpenStack as a whole."},{"line_number":13,"context_line":"** Project should not inadvertently duplicate functionality present in other"},{"line_number":14,"context_line":"   OpenStack projects. If they do, they should have a clear plan and timeframe"},{"line_number":15,"context_line":"   to prevent long-term scope duplication."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAATn%2F9BaE%3D","line":12,"updated":"2013-12-17 15:57:13.000000000","message":"I don\u0027t think obvious is easily-defined. How about \"a measured and agreed-upon progression\"?","commit_id":"47305dc71c33e4a80fdd870b8a0969e5c61dd4fe"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"80cc9c9f416be3071b4d57077fc3ce6cb8fc80fb","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"* Scope"},{"line_number":11,"context_line":"** Project must have a clear and defined scope which, in turn, represents"},{"line_number":12,"context_line":"   a measured and obvious progression for OpenStack as a whole."},{"line_number":13,"context_line":"** Project should not inadvertently duplicate functionality present in other"},{"line_number":14,"context_line":"   OpenStack projects. If they do, they should have a clear plan and timeframe"},{"line_number":15,"context_line":"   to prevent long-term scope duplication."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAATn%2F827Y%3D","line":12,"in_reply_to":"AAAATn%2F82%2BE%3D","updated":"2013-12-19 14:18:26.000000000","message":"\"Natural\" seems just as hard to define as \"obvious.\" The community has long had the argument over whether OpenStack should stick to IaaS feature or go beyond them, after all.\n\nI like \"measured\" and don\u0027t think we need to add anything to it.\n\n  Project must have a clear and defined scope\n  that represents a measured progression for\n  OpenStack as a whole.","commit_id":"47305dc71c33e4a80fdd870b8a0969e5c61dd4fe"},{"author":{"_account_id":1247,"name":"Mark McLoughlin","email":"markmc@redhat.com","username":"markmc"},"change_message_id":"4f20744e09bf0aa62b6e8a49adf148035520879b","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"* Scope"},{"line_number":11,"context_line":"** Project must have a clear and defined scope which, in turn, represents"},{"line_number":12,"context_line":"   a measured and obvious progression for OpenStack as a whole."},{"line_number":13,"context_line":"** Project should not inadvertently duplicate functionality present in other"},{"line_number":14,"context_line":"   OpenStack projects. If they do, they should have a clear plan and timeframe"},{"line_number":15,"context_line":"   to prevent long-term scope duplication."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAAUH%2F%2FX6k%3D","line":12,"in_reply_to":"AAAATn%2F827Y%3D","updated":"2014-01-14 14:13:32.000000000","message":"Done","commit_id":"47305dc71c33e4a80fdd870b8a0969e5c61dd4fe"},{"author":{"_account_id":964,"name":"Anne Gentle","email":"annegentle@justwriteclick.com","username":"annegentle"},"change_message_id":"b29f13f5f719e1ddf31ebf800c9dcd56a0d8cd85","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"* Scope"},{"line_number":11,"context_line":"** Project must have a clear and defined scope which, in turn, represents"},{"line_number":12,"context_line":"   a measured and obvious progression for OpenStack as a whole."},{"line_number":13,"context_line":"** Project should not inadvertently duplicate functionality present in other"},{"line_number":14,"context_line":"   OpenStack projects. If they do, they should have a clear plan and timeframe"},{"line_number":15,"context_line":"   to prevent long-term scope duplication."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAATn%2F82%2BE%3D","line":12,"in_reply_to":"AAAATn%2F83JM%3D","updated":"2013-12-19 14:08:43.000000000","message":"Yes, I like it.","commit_id":"47305dc71c33e4a80fdd870b8a0969e5c61dd4fe"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"4c127540a45613f63b1024acd2800cc0beca4fd4","unresolved":false,"context_lines":[{"line_number":9,"context_line":""},{"line_number":10,"context_line":"* Scope"},{"line_number":11,"context_line":"** Project must have a clear and defined scope which, in turn, represents"},{"line_number":12,"context_line":"   a measured and obvious progression for OpenStack as a whole."},{"line_number":13,"context_line":"** Project should not inadvertently duplicate functionality present in other"},{"line_number":14,"context_line":"   OpenStack projects. If they do, they should have a clear plan and timeframe"},{"line_number":15,"context_line":"   to prevent long-term scope duplication."}],"source_content_type":"application/octet-stream","patch_set":1,"id":"AAAATn%2F83JM%3D","line":12,"in_reply_to":"AAAATn%2F9BaE%3D","updated":"2013-12-19 13:31:23.000000000","message":"Or \"a measured and natural progression\" ?","commit_id":"47305dc71c33e4a80fdd870b8a0969e5c61dd4fe"}]}
