)]}'
{"goals/index.rst":[{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"63cbc804f94283ec4f610f36b49a5d7ef9046cad","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_ab5c814b","line":147,"updated":"2019-03-07 00:59:57.000000000","message":"I thought story status was tied to task status. Can a story be closed if it has open tasks?","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"c87938bd586b6b37a7b6ff748430c8dbf2d5a6fe","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_6b0206b7","line":147,"in_reply_to":"5fc1f717_02148e4d","updated":"2019-03-07 18:02:07.000000000","message":"\u003e What is the benefit of moving the tasks to another story vs. just\n \u003e leaving them open?\n\nThe benefit from my perspective as owning a goal story is I can effectively close out my story.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"f23506ea01a488d0f792aeddef8f9298fd0b6aa4","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_f59be362","line":147,"in_reply_to":"5fc1f717_0c2f9df6","updated":"2019-03-12 17:57:01.000000000","message":"OK, so how about I just remove the \"close out the story in StoryBoard\" part of that so we have:\n\n\"At the end of the release, there may be open tasks and these can remain open in case someone comes along later and completes the task. As goal champion you are not responsible for completing any incomplete tasks for which you are not assigned, i.e. the project assigned to the task is responsible for completing it.\"\n\nI should note that my upgrade checkers story has a lot of tasks under it:\n\nhttps://storyboard.openstack.org/#!/story/2003657\n\nAnd those are all by default owned by the openstack/governance project, so to really follow what I\u0027m saying above I would need to change the project on any open tasks from governance to openstack/aodh, for example (assuming the project is even in storyboard, of which not all are).","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"20d230775633e5ac4fafa7731c94f4f707ef89db","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_e0a0b144","line":147,"in_reply_to":"5fc1f717_20f6b964","updated":"2019-03-15 23:12:53.000000000","message":"and as this is about goal closure steps. should not we add this in \u0027Completing Goals\u0027 section?","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"ccc36350755b57e4216cd0ee4a264ff84272c99b","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_e68720d7","line":147,"in_reply_to":"5fc1f717_46c5d43b","updated":"2019-03-07 01:59:12.000000000","message":"+1. if non-complete projects need more time then, tasks can be moved to new story with ownership to project otherwise just invalidate the tasks with PTL agreement.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"61955ba6ab88978ab0797d4a933cd18590cd888a","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_df0b5d7a","line":147,"in_reply_to":"5fc1f717_54e434e1","updated":"2019-03-12 22:41:45.000000000","message":"Yes, I like that new wording.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"cad6bf4013ef49ae57ec33fecff8c780f818bfc9","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_a641ca0d","line":147,"in_reply_to":"5fc1f717_5d2c8798","updated":"2019-03-11 18:36:14.000000000","message":"In my opinion, this eludes to one of the tougher areas we have with community goals. In the event a percentage of projects don\u0027t complete the goal, then we probably shouldn\u0027t close it out. Conversely, I understand the rub in not being able to close something out as a goal champion despite working on an effort for months.\n\nMaybe part of the issue here is that the status we\u0027re currently using via storyboard is too binary for such a massive amount of work (which community goals typically are).\n\nWould it be nice or better if SB displayed a completion percentage based on the status of the associated tasks?","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"17171dee32c39c22cba262c2e3f781a7efc070e9","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_f2148250","line":147,"in_reply_to":"5fc1f717_6b0206b7","updated":"2019-03-10 23:48:00.000000000","message":"yeah, it is about transitioning the original story to some state at the end of cycle when goal champion thinks goal work for all the required projects is finished. \n\nAs we are now tracking goal under Story, the marking of the goal as complete means closing the Stroy which is nothing but no open tasks under it.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"ed947ad1ab186bc83cab45eef7d3ea6c3b12a3b5","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_0c2f9df6","line":147,"in_reply_to":"5fc1f717_a641ca0d","updated":"2019-03-11 21:06:18.000000000","message":"I think there are some misunderstandings about how storyboard works to clear up.\n\nA \u0027story\u0027 is little more than a collection of tasks, each of which belongs to a particular project (not necessarily all the same project). Tasks can be moved between projects but they can\u0027t be moved between stories. A story doesn\u0027t really have a \u0027status\u0027 except inasmuch as it can be seen to either contain open tasks or not. It has an author (i.e. reporter), but it doesn\u0027t have an assignee. Only tasks have assignees. So there\u0027s no need for the goal champion to close out \u0027their\u0027 story (presumably by marking all the open tasks as invalid, since there\u0027s no way to change the state of a story directly); they don\u0027t own the story, nobody does. And as others have said, marking tasks that do in fact still need to be done as \u0027Invalid\u0027 seems wrong.\n\nIf the goal champion is listed as the assignee for any of the tasks and they don\u0027t plan to complete them personally, they should remove themselves as the task owner. They should feel free to unsubscribe from the story. They should mark any tasks that are actually invalid as invalid. But I don\u0027t see any reason to close/delete valid tasks.\n\nProjects with an open task are the ones who will ultimately have to complete/mark invalid/ignore forever the task, so it wouldn\u0027t hurt to remind the PTL of its existence, but I don\u0027t think the goal champion should be required to come to a resolution on every task.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"eb429dd58613fd0d457b728e9779e8b5f287f077","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_46c5d43b","line":147,"in_reply_to":"5fc1f717_ab5c814b","updated":"2019-03-07 01:50:01.000000000","message":"That\u0027s something I was wondering about as well, and I had started documenting something to the effect of, \"close the story and any remaining tasks. For any not yet complete tasks, consider discussing with the associated PTL what they would like to do about the task for tracking, e.g. move to a new story so the goal story can be closed out, or just invalidate or delete the task if it will never be completed.\"","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"c4a93cb18f35be7d8da9adab7f33e6e44d432cf7","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_11a775a9","line":147,"in_reply_to":"5fc1f717_df0b5d7a","updated":"2019-03-14 14:50:56.000000000","message":"+1","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"89cacfe37d7ac634085bcf9f889edfe2ce4e7057","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_7ab432f3","line":147,"in_reply_to":"5fc1f717_e0a0b144","updated":"2019-03-19 22:37:38.000000000","message":"\u003e and as this is about goal closure steps. should not we add this in\n \u003e \u0027Completing Goals\u0027 section?\n\nI could see it fitting in either place.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"39dd61e0bafcfca39c7bc72cd236a0ea454f5e31","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_eebb72e2","line":147,"in_reply_to":"5fc1f717_e68720d7","updated":"2019-03-07 08:28:05.000000000","message":"I would prefer if we had this under a generic backlog/story of uncompleted tasks with a clear reference of the initial goal. All the unfinished business can be pointed to, with a simple link, to this generic story.\n\nPositive points:\n- We can point the link to people eager to help.\n- The tasks can still be assigned to PTL if necessary.\n- We can track how those evolve over time with a single view.\n- We can analyse what\u0027s going on with project x if it is piling tasks up.\n\nNegative points:\n- It effectively shows a graveyard of community things. It might look like a list of failure (which could have a negative connotation for some).\n\nI think I/we can come up with more negative and positive points but...\n\nWhat I would like to know first is what the benefit is to allow the PTL to decide where this should be stored, for the OpenStack community in general.\n\nIf we consider it\u0027s better to have it handled by PTL, fine. Else I believe the TC should track this in \"unfinished business\".","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"5533b33564518486bd1913f9a419fa6b5101ea42","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_02148e4d","line":147,"in_reply_to":"5fc1f717_eebb72e2","updated":"2019-03-07 13:09:06.000000000","message":"What is the benefit of moving the tasks to another story vs. just leaving them open?","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"3a6b9154859c9eb855cc7bf5dc8f07d8f5dd4d31","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_5d2c8798","line":147,"in_reply_to":"5fc1f717_f2148250","updated":"2019-03-11 00:02:57.000000000","message":"But if the work isn’t actually done, why close the ticket as though it is? Why make extra work by opening separate tickets to track work that we already have tickets to track?","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"f502ba6d005a35ab33e5a27e81b7fb21dfbbec66","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_54e434e1","line":147,"in_reply_to":"5fc1f717_f59be362","updated":"2019-03-12 21:48:03.000000000","message":"I like that wording. (Although maybe avoid using the word \u0027assigned\u0027 to refer to both the assignee and the project for a task.)\n\nIn a world in which all projects were on Storyboard then I\u0027d expect that all of the tasks would have belonged to particular projects, and none of them to openstack/governance, from the beginning. (I\u0027m actually mildly surprised that the Gerrit integration worked, because I thought it required the task\u0027s project to match the repo.)\n\nIn a world where we are in Storyboard/Launchpad limbo... I\u0027m not sure what the answer it TBH.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"3c680cedbfb036afefff7035e481a7678cc7ebf4","unresolved":false,"context_lines":[{"line_number":144,"context_line":"they are able to make progress on the work and have not become stuck."},{"line_number":145,"context_line":""},{"line_number":146,"context_line":"At the end of the release, close out the story in StoryBoard. There may"},{"line_number":147,"context_line":"be open tasks and these can remain open in case someone comes along later and"},{"line_number":148,"context_line":"completes the task. It is also encouraged to send a retrospective email to the"},{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_20f6b964","line":147,"in_reply_to":"5fc1f717_f59be362","updated":"2019-03-15 23:10:55.000000000","message":"yeah, same type of agreement is written in \u0027Tracking Goal Progress\u0027 and \u0027Completing Goal\u0027 section too. tasks need to be owned but projects side and they can add further information about \u0027when to complete\u0027 or \u0027if not completing, explain the appropriate reason.\u0027\n\nOne area to address here is about the tasks owned by champions or volunteer. Which is case of upgrade check goal. few tasks which code is up but not reviewed by projects are either asigned to matt or akhil/rajat(goal volunteer). \n\nThese has to be re-assign to project PTL so that it get attension. We can write down  this step too.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"cad6bf4013ef49ae57ec33fecff8c780f818bfc9","unresolved":false,"context_lines":[{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"},{"line_number":151,"context_line":"that did not complete the goal, anything notable that came up during the goal"},{"line_number":152,"context_line":"implementation phase, and next steps if there are any."},{"line_number":153,"context_line":""},{"line_number":154,"context_line":"Release Cycles"},{"line_number":155,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_866fee90","line":152,"updated":"2019-03-11 18:36:14.000000000","message":"++\n\nFocusing on the completion percentage is important because I think it\u0027s less likely to mislead people. For example, saying the community did X as a community-wide goal when 15% of projects didn\u0027t actually finish is going to frustrate users and operators (if those goals are end user facing).\n\nThe pattern you have here enables more \"granular\" communication, if that makes sense.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"a69ae2601787aec951e4ca772155d631ac4d210f","unresolved":false,"context_lines":[{"line_number":149,"context_line":"openstack-discuss mailing list with a summary of the goal including things"},{"line_number":150,"context_line":"such as how many projects completed the goal, reasons behind some projects"},{"line_number":151,"context_line":"that did not complete the goal, anything notable that came up during the goal"},{"line_number":152,"context_line":"implementation phase, and next steps if there are any."},{"line_number":153,"context_line":""},{"line_number":154,"context_line":"Release Cycles"},{"line_number":155,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5fc1f717_ecb52c33","line":152,"in_reply_to":"5fc1f717_866fee90","updated":"2019-03-14 15:07:39.000000000","message":"That is indeed nice.","commit_id":"311f0b144ba8ce2d1a991ddddfffb5ded100e878"}]}
