)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"e202817ee5aac85a940e52c573ccc3890ac75341","unresolved":false,"context_lines":[{"line_number":11,"context_line":"repository. The new repo is created by the change at the depends-on"},{"line_number":12,"context_line":"below, which will seed the repo from a filtered clone of nova. The new"},{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_43fed405","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":72},"updated":"2018-08-31 19:23:13.000000000","message":"The existing core team selects the new cores. Unless non-nova-core, not even remotely placement contributing TC folk are fine with changing this standard operating procedure within the nova team too.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"76ca2a583020ed8204813e0d647eb16672fae6cc","unresolved":false,"context_lines":[{"line_number":11,"context_line":"repository. The new repo is created by the change at the depends-on"},{"line_number":12,"context_line":"below, which will seed the repo from a filtered clone of nova. The new"},{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_83ef0ce8","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":72},"in_reply_to":"3f79a3b5_43fed405","updated":"2018-08-31 19:32:36.000000000","message":"I expect to get lambasted by saying \"nova core\" here since there is a placement repo with a placement-core team, but as it stands today, the placement-core team *is* nova-core so that\u0027s why I used those words.\n\nGod it sucks that I have to think about everything I say and how it will be interpreted in this whole mess.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"ebb99cf04bcd201043272833984ee21bbe53356f","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_c3267dbb","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"updated":"2018-08-30 23:10:55.000000000","message":"I don\u0027t think it\u0027s appropriate at this stage to set a hard deadline. We have a lot of technical work ahead of us, just to get the code extraction done, and we don\u0027t yet know how long it will take.\n\nGiven that, I think once the code extraction is complete and working with all of the necessary zuul jobs, ensuring upgrade works, etc, we turn toward a discussion of an agreeable timeline for switching the governance.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":7,"name":"Jay Pipes","email":"jaypipes@gmail.com","username":"jaypipes"},"change_message_id":"930d24623f2e7a9121ca921ecd4e8784f8af5dee","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_c8276dc7","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_144fc2be","updated":"2018-08-31 13:19:10.000000000","message":"\u003e I\u0027m not asking anyone to predict the future; I\u0027m asking to have a\n \u003e plan for it.\n \u003e \n \u003e I want to understand what preconditions for a governance change the\n \u003e nova team thinks are important so that I can make a good decision\n \u003e when someone asks to have the placement team created, and I want to\n \u003e have some idea of when that is likely to happen.\n \u003e \n \u003e Of course plans change when events happen differently than\n \u003e anticipated. But we make plans anyway so that we can at least be\n \u003e aligned while things are going as we expect.\n\nI think it\u0027s pretty clear from the IRC and ML conversations that the issues that exist are not technical or bureaucratic in nature. They are political, emotional and personal (on all sides).\n\nI fail to see how setting a date/timeline for a separate core team will do anything other than aggravate the underlying emotions that feed the inevitable uncomfortable discussions that will need to be aired about core team membership.\n\nAnd I think that\u0027s mostly the point of setting a timeline like this: as a forcing function and catalyst for that uncomfortable conversation.\n\nThere are better and more direct ways of forcing that conversation, though, IMHO. Matt has been direct and forthcoming with his feelings about the matter on IRC and the ML. I would hope that the rest of us can do the same.\n\nLet\u0027s have adult conversations that start with a recognition that what we\u0027re talking about here is a people issue and not a technical or process issue. Let\u0027s have adult conversations at the PTG about expectations for the proposed placement-core team and its makeup. Let\u0027s have adult conversations at the PTG about the feelings some members of the community have about the concentration of technical and decision-making power under too few (or the wrong) individuals. Let\u0027s have the airing of grievances that some individuals would like to see and address those grievances in an adult, honest manner.\n\n-jay","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"b1bc2aab1ec150b271b5fd699865aff71461f014","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_833f2586","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_6363e9de","updated":"2018-08-30 23:28:20.000000000","message":"The extraction process has literally just started today. The PTG is about a week away. I don\u0027t think anyone can make an accurate prediction within the next two weeks about how long it will take the extract the code. I don\u0027t think we should be talking about when to switch the governance before we\u0027ve done the technical work of extracting the code.\n\nI don\u0027t want anything to be indefinite, but trying to set a hard deadline on day 1 of the effort doesn\u0027t seem useful to me. I think we should extract the code, make sure an upgrade from rocky \u003d\u003e stein works for deployers, and then decide together on a timeline for switching governance. I don\u0027t think switching governance in the middle of a code extraction would be useful.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":4690,"name":"melanie witt","display_name":"melwitt","email":"melwittt@gmail.com","username":"melwitt"},"change_message_id":"5c3cdd1f87956b240c0c48eb410ab1cb6b18c3f7","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_f8f6b45d","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_75238da8","updated":"2018-08-31 15:22:15.000000000","message":"I\u0027m thinking about this simply. This says, \"The expectation is that by the Stein 2 milestone, placement will become its own official project,\" and that is not my expectation, nor is it what I\u0027ve explained in detail on the ML when we talked about governance. I don\u0027t feel comfortable to +1 something that I don\u0027t agree with, even if it\u0027s, \"only in the commit message.\"\n\nWhat I said before is, after the code has been extracted, we stay as one group while we get challenging, first-ever work done that is important to operators and users. The main one is integrating NRPs for vGPUs -- vGPUs are feature that has community-wide appeal, that the foundation wanted to highlight at the last summit keynote.\n\nWhat I would like to see is the code extracted and working with upgrades, have a checkpoint discussion where we talk timelines for changing governance, agree on a set of work items to complete before we switch, and then carry out that plan.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"76bbd191867dc01f5c1c4e115595dcffb3467cad","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_b1f14098","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_833f2586","updated":"2018-08-31 10:17:57.000000000","message":"I don\u0027t really read this as a hard deadline or a prediction... I read \"the expectation is\" more as an inspirational goal. Would rewriting it as \"the goal is for placement to become its own official project by the Stein 2 milestone\"  and \"when extraction is completed another change will be posted\" make that clearer ?","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"f9889f79d8b6bf981e7d68aa27a5a3a3f0713fdf","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_144fc2be","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_b1f14098","updated":"2018-08-31 11:25:05.000000000","message":"I\u0027m not asking anyone to predict the future; I\u0027m asking to have a plan for it.\n\nI want to understand what preconditions for a governance change the nova team thinks are important so that I can make a good decision when someone asks to have the placement team created, and I want to have some idea of when that is likely to happen.\n\nOf course plans change when events happen differently than anticipated. But we make plans anyway so that we can at least be aligned while things are going as we expect.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"1c1de415a7f6d5b8c5c94cdf869fa452befa7fe0","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_6363e9de","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_c3267dbb","updated":"2018-08-30 23:15:58.000000000","message":"I want to see a plan, after the PTG, that includes a timeline and a minimal set of \"must happen first\" technical things. It is not OK to keep the contributors to this project in limbo indefinitely.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"c006ddae0027a405982d5654a2ef6fef975b4b17","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_75238da8","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_c8276dc7","updated":"2018-08-31 14:01:20.000000000","message":"I agree we need to have those conversations. I see a timeline/plan as a framework for them to occur.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"0845aed6141dd3beb9482fde1c9cf01071322923","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_23cf222a","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_c8276dc7","updated":"2018-08-31 13:52:45.000000000","message":"I too read this as a goal (which is what we had discussed, as Chris documents earlier in the review comments), not a hard deadline.  Even hard deadlines move all the time when things don\u0027t go as expected, circumstances/priorities change, etc. Besides, when has text in a commit message ever represented a contractual commitment to future action?\n\nI\u0027m not some big proponent of heavyweight project management process, but setting a target date for a piece of work is, like, a pretty normal thing to do. (Believe me - I\u0027ve tried getting a date of \"eventually\" past PMPs before. It hasn\u0027t gone well.)","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"49581a2b634400cc9341fda77896ed270e05d7a0","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_4b97d43b","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_f8f6b45d","updated":"2018-08-31 15:39:14.000000000","message":"I think it\u0027s unfortunate to see so many TC members voting to ignore the concerns of the PTL for the project that this directly affects. Many of the comments seem to circle around \"meh this is a minor suggestion of a deadline\" yet remain steadfast against getting it adjusted. In the discussion of this split, many historical artifacts have been quoted as evidence of the urgency and intent, so I don\u0027t think it\u0027s at all unreasonable to be concerned about setting (or even implying) expectations for a specific date (especially one as close as stein-2).\n\nI would expect the TC to be extremely supportive of the PTL\u0027s concerns here, especially as she\u0027s trying to be supportive of a very difficult situation as Jay said.","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"b2cca7f743c792ebd6aa8c52212c0d2a4ebe7777","unresolved":false,"context_lines":[{"line_number":13,"context_line":"repo will initially have as its core reviewers existing nova-cores plus"},{"line_number":14,"context_line":"a small number of additional cores selected from placement contributors."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"The expectation is that by the Stein 2 milestone, placement will become"},{"line_number":17,"context_line":"its own official project, to help make it clear that placement is a"},{"line_number":18,"context_line":"service for all of openstack, and to help narrow (slightly) the scope of"},{"line_number":19,"context_line":"nova. Near that milestone another change will be posted proposing the"},{"line_number":20,"context_line":"change in governance."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_2b77f83d","line":17,"range":{"start_line":16,"start_character":0,"end_line":17,"end_character":24},"in_reply_to":"3f79a3b5_f8f6b45d","updated":"2018-08-31 15:38:03.000000000","message":"That\u0027s a lot of good detail. Let\u0027s get that written down some place where it\u0027s clear and everyone with an interest can comment on it so we can tell when there\u0027s general agreement. I\u0027m not sure what tool you\u0027d want to use for that. Maybe a spec?","commit_id":"c53d9ca0f1b372e228ce08f5eb682325cd3dfbb8"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"49c398ba10eb627a45584c958a38233500afda3c","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add placement deliverable to nova"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Add openstack/placement as repo under the nova project to indicate the"},{"line_number":10,"context_line":"the home for placement as it is extracted from the nova code repository"},{"line_number":11,"context_line":"to its own."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3f79a3b5_217cc9b4","line":9,"range":{"start_line":9,"start_character":24,"end_line":9,"end_character":31},"updated":"2018-09-04 12:58:11.000000000","message":"as a repo","commit_id":"86f80953867e802fb168ea505043cb4a935be39f"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"49c398ba10eb627a45584c958a38233500afda3c","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Add placement deliverable to nova"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Add openstack/placement as repo under the nova project to indicate the"},{"line_number":10,"context_line":"the home for placement as it is extracted from the nova code repository"},{"line_number":11,"context_line":"to its own."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"The new repo [1] was created by the (merged) change at the depends-on"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3f79a3b5_e14b3184","line":10,"range":{"start_line":9,"start_character":67,"end_line":10,"end_character":3},"updated":"2018-09-04 12:58:11.000000000","message":"s/the the/the/","commit_id":"86f80953867e802fb168ea505043cb4a935be39f"}],"reference/projects.yaml":[{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"49c398ba10eb627a45584c958a38233500afda3c","unresolved":false,"context_lines":[{"line_number":2058,"context_line":"    name: Melanie Witt"},{"line_number":2059,"context_line":"    irc: melwitt"},{"line_number":2060,"context_line":"    email: melwittt@gmail.com"},{"line_number":2061,"context_line":"  irc-channel: openstack-nova"},{"line_number":2062,"context_line":"  service: Compute service"},{"line_number":2063,"context_line":"  mission: \u003e"},{"line_number":2064,"context_line":"    To implement services and associated libraries to provide massively"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"3f79a3b5_a10f7937","line":2061,"range":{"start_line":2061,"start_character":15,"end_line":2061,"end_character":29},"updated":"2018-09-04 12:58:11.000000000","message":"is there a way to list more than one here? (openstack-placement)","commit_id":"86f80953867e802fb168ea505043cb4a935be39f"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"518ed3c8f0e395ecaabab22af42559a4152e596d","unresolved":false,"context_lines":[{"line_number":2058,"context_line":"    name: Melanie Witt"},{"line_number":2059,"context_line":"    irc: melwitt"},{"line_number":2060,"context_line":"    email: melwittt@gmail.com"},{"line_number":2061,"context_line":"  irc-channel: openstack-nova"},{"line_number":2062,"context_line":"  service: Compute service"},{"line_number":2063,"context_line":"  mission: \u003e"},{"line_number":2064,"context_line":"    To implement services and associated libraries to provide massively"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"3f79a3b5_6fe8eab2","line":2061,"range":{"start_line":2061,"start_character":15,"end_line":2061,"end_character":29},"in_reply_to":"3f79a3b5_94647923","updated":"2018-09-10 17:58:11.000000000","message":"For placement? #openstack-placement. If we can only use one for this section, #openstack-nova and you\u0027ll quickly be pointed to #openstack-placement :)","commit_id":"86f80953867e802fb168ea505043cb4a935be39f"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"119ce748e4d5437a7eef66cea40d971e981c4762","unresolved":false,"context_lines":[{"line_number":2058,"context_line":"    name: Melanie Witt"},{"line_number":2059,"context_line":"    irc: melwitt"},{"line_number":2060,"context_line":"    email: melwittt@gmail.com"},{"line_number":2061,"context_line":"  irc-channel: openstack-nova"},{"line_number":2062,"context_line":"  service: Compute service"},{"line_number":2063,"context_line":"  mission: \u003e"},{"line_number":2064,"context_line":"    To implement services and associated libraries to provide massively"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"3f79a3b5_94647923","line":2061,"range":{"start_line":2061,"start_character":15,"end_line":2061,"end_character":29},"in_reply_to":"3f79a3b5_a10f7937","updated":"2018-09-10 17:36:21.000000000","message":"I don\u0027t think we have that now. Which is the best channel to use?","commit_id":"86f80953867e802fb168ea505043cb4a935be39f"}]}
