)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"b3fb2888ed041a3b4ea62c7f64437aade763c27e","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Start a goals document"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"As explained in the document, this is a way to keep track of long term"},{"line_number":10,"context_line":"ideas or hopes that are too far away or two vague to warrant specs, even"},{"line_number":11,"context_line":"wishlist specs. The main goal of these goals is to keep an eye forward"},{"line_number":12,"context_line":"to long term improvements which are not really related to features."},{"line_number":13,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_05898e1c","line":10,"range":{"start_line":9,"start_character":52,"end_line":10,"end_character":5},"updated":"2018-11-22 10:19:38.000000000","message":"I thougt tracking a task is what blueprint is for, isn\u0027t it? I don\u0027t think official document has an ability to track tasks.","commit_id":"ecf9a976ffb046419fffc86b2df2b043f7d326b0"},{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"33fe14cf95ceff58081a5b6af7f629eff48c934c","unresolved":false,"context_lines":[{"line_number":9,"context_line":"As explained in the document, this is a way to keep track of long term"},{"line_number":10,"context_line":"ideas or hopes that are too far away or two vague to warrant specs, even"},{"line_number":11,"context_line":"wishlist specs. The main goal of these goals is to keep an eye forward"},{"line_number":12,"context_line":"to long term improvements which are not really related to features."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: Ic76852d3bea36f797dd845fd7be520670d214aa3"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_50e66216","line":12,"range":{"start_line":12,"start_character":3,"end_line":12,"end_character":66},"updated":"2018-11-22 12:24:57.000000000","message":"If this document is for things not related to features, I would say so explicitly in the document.","commit_id":"ecf9a976ffb046419fffc86b2df2b043f7d326b0"}],"doc/source/contributor/goals.rst":[{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"b3fb2888ed041a3b4ea62c7f64437aade763c27e","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Like many OpenStack projects, placement uses blueprints and specifications to"},{"line_number":19,"context_line":"plan and design upcoming work. Sometimes, however, certain types of work fit"},{"line_number":20,"context_line":"more in the category of wishlist, or when-we-get-around-to-it. In those cases a"},{"line_number":21,"context_line":"specification is too formal and detailed but it is still worthwhile to remember"},{"line_number":22,"context_line":"the idea and put it somewhere. That\u0027s what this document is for: a place to"},{"line_number":23,"context_line":"find and put goals for placement that are too vague for immediate action."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"This document can also operate as one of several sources of guidance on how not"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_e5c6d29b","line":22,"range":{"start_line":20,"start_character":63,"end_line":22,"end_character":30},"updated":"2018-11-22 10:19:38.000000000","message":"Agreed that spec is too formal, but then why not blueprint?","commit_id":"ecf9a976ffb046419fffc86b2df2b043f7d326b0"},{"author":{"_account_id":25625,"name":"Tetsuro Nakamura","email":"tetsuro.nakamura.bc@hco.ntt.co.jp","username":"tetsuro0907"},"change_message_id":"33fe14cf95ceff58081a5b6af7f629eff48c934c","unresolved":false,"context_lines":[{"line_number":25,"context_line":"This document can also operate as one of several sources of guidance on how not"},{"line_number":26,"context_line":"to stray too far from the long term vision of placement."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Stop Using Global Config"},{"line_number":29,"context_line":"------------------------"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Placement uses `oslo.config`_ to manage configuration. From nova, it inherits"},{"line_number":32,"context_line":"using a global ``CONF`` as the way to interact with the configuration options."},{"line_number":33,"context_line":"This isn\u0027t necessary. If changed, it would make tests less likely to leak"},{"line_number":34,"context_line":"configuration settings amongsts themselves and will also ease use of the"},{"line_number":35,"context_line":"``PlacementFixture`` by other projects which wish to use placement in their"},{"line_number":36,"context_line":"functional tests."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":".. _oslo.config: https://docs.openstack.org/oslo.config"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_6b0ff32b","line":36,"range":{"start_line":28,"start_character":0,"end_line":36,"end_character":17},"updated":"2018-11-22 12:24:57.000000000","message":"Can we re-write this more like a guidance format rather than todo format so that we can use this guidance even after it is resolved? Something like;\n\n\n\nUse non-Global Configuration\n\n-----------------------\n\nPlacement should use its own configuration not to leak the configuration settings to functional tests of other projects. Note that now it uses `oslo.config` and from nova ...so the problem","commit_id":"ecf9a976ffb046419fffc86b2df2b043f7d326b0"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"18f0a679d96831c2175e91c22eb6b6886956d305","unresolved":false,"context_lines":[{"line_number":40,"context_line":"``PlacementFixture`` by other projects which wish to use placement in their"},{"line_number":41,"context_line":"functional tests. Once we fix this we should ensure that we avoid regressing to"},{"line_number":42,"context_line":"using global configuration."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":""},{"line_number":45,"context_line":".. _oslo.config: https://docs.openstack.org/oslo.config"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_0dc0974a","line":43,"updated":"2018-11-27 10:20:48.000000000","message":"If we say we want to fix this then that is a bug or spec for me.\nIf we say that new feature implementations should be designed in a way that they are using non-global config whenever it is possible then this is a guidance for the implementor and then  I\u0027m fine having it here in the documentation.","commit_id":"1c6b06bd96083fbc96a1612875a23aa05c31f700"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"f9d0f4ddc118da282a915c9c9989aa22a4955a2d","unresolved":false,"context_lines":[{"line_number":30,"context_line":"This document can also operate as one of several sources of guidance on how not"},{"line_number":31,"context_line":"to stray too far from the long term vision of placement."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Don\u0027t Global Config"},{"line_number":34,"context_line":"-------------------"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Placement uses `oslo.config`_ to manage configuration. From nova, it inherits"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_926a3081","line":33,"range":{"start_line":33,"start_character":0,"end_line":33,"end_character":19},"updated":"2018-11-30 15:50:19.000000000","message":"Should this be \"Don\u0027t Use Global Config\" or were you being cute?\n\nSince [1] is merging, we should fup and edit this section.\n\n[1] https://review.openstack.org/619121","commit_id":"24fb4ef52495a888e39ba6dfd3e6904b8f8960dd"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"d04c0fd0dfd8041b6b119f02fd7d255fac56ed19","unresolved":false,"context_lines":[{"line_number":30,"context_line":"This document can also operate as one of several sources of guidance on how not"},{"line_number":31,"context_line":"to stray too far from the long term vision of placement."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Don\u0027t Global Config"},{"line_number":34,"context_line":"-------------------"},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Placement uses `oslo.config`_ to manage configuration. From nova, it inherits"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3f79a3b5_52125800","line":33,"range":{"start_line":33,"start_character":0,"end_line":33,"end_character":19},"in_reply_to":"3f79a3b5_926a3081","updated":"2018-11-30 15:52:14.000000000","message":"Was probably being exhausted. But yeah, will fup to reflect the new state of affairs.","commit_id":"24fb4ef52495a888e39ba6dfd3e6904b8f8960dd"}]}