)]}'
{"README.rst":[{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"2bdb6d042b79be55306a4edc4ea31c5b10f09784","unresolved":false,"context_lines":[{"line_number":39,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":40,"context_line":"#. Land quickly: A spec is a living document, and lives in the repository"},{"line_number":41,"context_line":"   not in gerrit. Potential users, ops and developers will look at"},{"line_number":42,"context_line":"   specs.openstack.org to get an idea of what\u0027s being worked on, so they"},{"line_number":43,"context_line":"   need to be quick to land."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"#. Initial spec patch is an idea not a technical design: That way the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_2884d108","line":42,"updated":"2015-06-10 17:03:07.000000000","message":"would be nice to have a full address so it turns clicky when rendered","commit_id":"98cc0d768844dadd10433631ee06a381c77d8f00"},{"author":{"_account_id":7847,"name":"Alistair Coles","email":"alistairncoles@gmail.com","username":"acoles"},"change_message_id":"6d474b5b808b005e13f49acf1202548e2b792e12","unresolved":false,"context_lines":[{"line_number":47,"context_line":"   limbo land."},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"#. Technical design elements added in subsequent patches: This keeps rule"},{"line_number":50,"context_line":"   #1. And no doubt be added up until the end of the specs life cycle."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"#. Missed your say in a conversation, raise a patch: Your idea could be"},{"line_number":53,"context_line":"   merged with the spec or abandoned if there a reason it wont work, so no"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_a348d8cc","line":50,"updated":"2015-06-10 21:29:17.000000000","message":"nit-ish: Second sentence takes a bit of parsing. How about:\n\n  And no doubt patches will be added up until the end of the specs life cycle.","commit_id":"98cc0d768844dadd10433631ee06a381c77d8f00"},{"author":{"_account_id":12193,"name":"Hisashi Osanai","email":"osanai.hisashi@jp.fujitsu.com","username":"ho"},"change_message_id":"bd269da0a0bd6f6b0cf62c41486cb756099cbe4c","unresolved":false,"context_lines":[{"line_number":48,"context_line":""},{"line_number":49,"context_line":"#. Technical design elements added in subsequent patches: This keeps rule"},{"line_number":50,"context_line":"   #1. And no doubt be added up until the end of the specs life cycle."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"#. Missed your say in a conversation, raise a patch: Your idea could be"},{"line_number":53,"context_line":"   merged with the spec or abandoned if there a reason it wont work, so no"},{"line_number":54,"context_line":"   harm."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_76a4d149","line":51,"updated":"2015-06-11 04:46:05.000000000","message":"I would like to classify patches like following:\n* Initial spec patch (an idea not a technical design)\n* 2nd spec patch (a technical design which covers whole thing)\n* subsequent spec patches (I like Alistair\u0027s idea like code)\n\nIf there are a lot of subsequent spec patches without 2nd spec patch, I think it\u0027s not possible to make review whether it looks good or not from technical point of view.","commit_id":"98cc0d768844dadd10433631ee06a381c77d8f00"},{"author":{"_account_id":330,"name":"John Dickinson","email":"me@not.mn","username":"notmyname"},"change_message_id":"2bdb6d042b79be55306a4edc4ea31c5b10f09784","unresolved":false,"context_lines":[{"line_number":49,"context_line":"#. Technical design elements added in subsequent patches: This keeps rule"},{"line_number":50,"context_line":"   #1. And no doubt be added up until the end of the specs life cycle."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"#. Missed your say in a conversation, raise a patch: Your idea could be"},{"line_number":53,"context_line":"   merged with the spec or abandoned if there a reason it wont work, so no"},{"line_number":54,"context_line":"   harm."},{"line_number":55,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"3afb71cf_e8935959","line":52,"updated":"2015-06-10 17:03:07.000000000","message":"I don\u0027t understand this sentence.","commit_id":"98cc0d768844dadd10433631ee06a381c77d8f00"},{"author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"change_message_id":"0e2ef70ab1ece80f4506ca90668d18ef42e0e34b","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"#. Initial patch is an idea not a technical design: That way the merits of"},{"line_number":46,"context_line":"   the idea can be discussed and landed and not stuck in gerrit limbo land."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"#. Second patch is an overview of the technical design: This will aid in the"},{"line_number":49,"context_line":"   technical discussions amongst the community."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_e42855e4","line":47,"updated":"2015-06-25 07:25:42.000000000","message":"I\u0027m now realizing that using the term, \"patch\" (e.g. \"initial patch\", \"second patch\" or so on) seems to confuse someone because we can count up the patch set number in gerrit.\n\ni.e. \"Initial patch\" means *both* the first patch set on gerrit review system and the first *landed* patch set. I know we want to mean the second one but we can be able to misunderstand easily that we can push technical design as patch set 2 of \"Initial patch\".\n\nSorry...I have no good idea to improve the expression but I wanna mean something like \"Second update patch based on landed initial patch\" but it seems verbose :/","commit_id":"619cda6a7f083395127081dd7013d103d0528fba"},{"author":{"_account_id":9625,"name":"Thiago da Silva","email":"thiagodasilva@gmail.com","username":"thiago"},"change_message_id":"bb0375a672b8c3b687114f94bd9f0eb7a07a920e","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"#. Initial patch is an idea not a technical design: That way the merits of"},{"line_number":46,"context_line":"   the idea can be discussed and landed and not stuck in gerrit limbo land."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"#. Second patch is an overview of the technical design: This will aid in the"},{"line_number":49,"context_line":"   technical discussions amongst the community."},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fa32b979_0b7765a0","line":47,"in_reply_to":"fa32b979_e42855e4","updated":"2015-06-25 19:37:27.000000000","message":"maybe change \"patch\" to \"version\"????\n\n\"First version of your spec should be an idea not a technical design\"\n\"The second version is an overview of the technical design...\"\n\"Subsequent versions improve/enhance....\"","commit_id":"619cda6a7f083395127081dd7013d103d0528fba"}]}