{"action":"created","comment":{"url":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/comments/70268317","id":70268317,"diff_hunk":"@@ -26,26 +26,156 @@\n   * Security  - non-upgrade-impacting\n   * Bug fixes - non-upgrade-impacting\n \n-## Working in the repository\n+# Issue workflow\n+\n+### Definitions\n+#### Issues\n+Issues are work items, they may be bugs or enhancements. They are managed using [Waffle](https://waffle.io/rcbops/u-suk-dev?source=rcbops%2Frpc-openstack) and stored in [GitHub](https://github.com/rcbops/rpc-openstack/issues). Issues that are logged in other places, for example on Launchpad for OSA, are not within scope unless they have been reported on this project by the creation of a new issue to track the upstream item.\n+\n+#### Waffle board\n+The [Waffle board](https://waffle.io/rcbops/u-suk-dev?source=rcbops%2Frpc-openstack) is a Kanban board consisting of a series of columns used to manage the progress of issues. This board is the only place to view or update the current work commitments.\n+\n+#### WIP (Work In Progress) limits\n+Each column on the board has a WIP limit that is used to control the amount of new work to which the engineering team commits. The WIP limits will be listed in the column titles on the Waffle board. No column can receive new work if it violates the WIP limit unless there is an explicit exception made for it as defined in the processes below.\n+\n+#### Stakeholders\n+* reporter - the individual that created the issue.\n+* owner(s) - the individual(s) assigned to manage the issue through to its closure.\n+* reviewer(s) - the individual(s) who review a pull request and provide feedback.\n+\n+#### Labels\n+Labels are used to categorise issues to aid with tracking and prioritisation.\n+\n+|Type                     |Label name              |Description                                                                                                                                                   |Examples                                                                                      |\n+|-------------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|\n+|Issue type               |type-bug                |Defects affecting the RPCO project.                                                                                                                           |                                                                                              |\n+|Issue type               |type-enhancement-large  |Significant new features that require tracking by the product team.                                                                                           |Adding a new OpenStack service.                                                               |\n+|Issue type               |type-enhancement-medium |Enhancements that impact other teams, such as requiring QE to implement significant new testing. These issues need to be factored into specific minor release.|                                                                                              |\n+|Issue type               |type-enhancement-small  |Enhancements can reasonably be added to any minor release, these should in general not change default behaviour only add to it.                               |Additional MaaS plugin metrics or new logstash filters.                                       |\n+|Issue type               |type-undecided          |Used when there is not enough information provided to determine the type.                                                                                     |                                                                                              |\n+|Team affected            |impacts-qe              |Identifies issues that affect the QE team.                                                                                                                    |                                                                                              |\n+|Team affected            |impacts-support         |Identifies issues that affect the Support team.                                                                                                               |                                                                                              |\n+|Team affected            |impacts-onboarding      |Identifies issus that are suitable activities for new team members or individuals.                                                                            |                                                                                              |\n+|Team affected            |impacts-training        |Identifies issues that affect the Training group.                                                                                                             |                                                                                              |\n+|Team affected            |impacts-rpcr            |Identifies issues that affect the Rackspace-supported Red Hat OpenStack Platform team.                                                                        |                                                                                              |\n+|Priority                 |prio-expedited          |Expedited issue, any issue that causes a fundamental failure in the product, especially if there is no workaround or it affects all deployments.              |Customers down, inoperable service, deployment failures of core functionality, blocked gating.|\n+|Priority                 |prio-1                  |Priority 1 issues are fundamental failures where there is a workaround or only a subset of users are affected.                                                |Incorrect default configurations.                                                             |\n+|Priority                 |prio-2                  |Priority 2 issues affect non-standard configurations or do not directly affect the customer experience or non-core features.                                  |Individual MaaS plugin failures.                                                              |\n+|Priority                 |prio-3                  |Priority 3 issue are low impact, they are cosmetic or cause limited tangible impact.                                                                          |Typographical errors.                                                                         |\n+|Priority                 |prio-undecided          |Unprioritised issue contain insufficient information on which to determine a priority.                                                                        |Issues that do not clearly describe what is broken or the impact it is having.                |\n+|Workflow status (Waffle) |status-approved         |An issue that has been moved into the column Approved.                                                                                                        |                                                                                              |\n+|Workflow status (Waffle) |status-doing            |An issue that has been moved into the column Doing.                                                                                                           |                                                                                              |\n+|Workflow status (Waffle) |status-needs-review     |An issue that has been moved into the column Needs-review.                                                                                                    |                                                                                              |\n+|Workflow status          |status-needs-information|The issue requires further information to enable it to be completed.                                                                                          |                                                                                              |\n+|Workflow status          |status-blocked          |Indicates an issue is blocked on another item of work. The description should be updated with a link to the blocking issue.                                   |                                                                                              |\n+|Workflow status          |status-duplicate        |Any issue that duplicates an existing issue.                                                                                                                  |                                                                                              |\n+|Workflow status          |status-invalid          |Any issue that is not within scope of the project.                                                                                                            |                                                                                              |\n+|Workflow status          |status-wontfix          |Any issue that it is determined will not be fixed.                                                                                                            |                                                                                              |\n+|Tracking upstream project|tracking-upstream       |For tracking issues with upstream projects that are affecting the RPCO project.                                                                               |                                                                                              |\n+|Product feature          |feature-gating          |Gating-related work.                                                                                                                                          |                                                                                              |\n+|Product feature          |feature-upgrades        |Upgrades-related work.                                                                                                                                        |                                                                                              |\n+|Product feature          |feature-monitoring      |Monitoring-related work.                                                                                                                                      |                                                                                              |\n+|Product feature          |feature-osa             |OSA-related work.                                                                                                                                             |                                                                                              |\n+\n+## Pre-Backlog -> Backlog\n+### Adding an issue to the backlog\n+Click [here](https://github.com/rcbops/rpc-openstack/issues/new) to load the form used when creating a new issue in the backlog. The form is generated from [this template](.github/ISSUE_TEMPLATE.md) which includes a set of questions for the reporter and a checklist to be completed by the owner as the issue is worked. Currently Waffle does not support the use of an issue template and so issues should not be created directly in Waffle.\n+\n+## Backlog\n+All issues that are are not approved to be worked are listed in Backlog, this includes new issues and those that have been triaged but not yet committed to.\n+\n+### Issue triage\n+Issue triage is an ongoing process that should happen on a daily basis, the engineering team will triage new issues and monitor unprioritised issues so that new commitments are always targetting the most import work.\n+\n+Each issue is given a priority and that priority is used to help decide the order in which issues are worked. It is important to remember that there is a finite resource available to fix issues. The process of prioritisation is used to focus the available resources on the most important tasks identified.\n+\n+Issues are labelled with a priority as defined in the [labels table](#Labels).\n+\n+#### Expedited issues\n+Expedited issues are allowed to exceed the WIP limit on any column. These issues are critical to fix and must be prioritised above all other work. They are identified with the label 'prio-expedited'. Due to the negative impact expedited issues have on WIP it is important they are used appropriately.\n+\n+#### Enhancements\n+Issues labeled as 'type-enhancement-large' or 'type-enhancement-medium' filter into planning for major and minor releases and should never be moved to Approved.\n+\n+Issues labeled as 'type-enhancement-small' should also be given a priority, in general they should be labeled as 'prio-3' but a higher priority can be given if the enhancement helps to prevent customer downtime.\n+\n+#### Classifying issues\n+Issues are categorised to simplify the process of identifying the highest priority issues and allow different types of work to be tracked. The steps taken to correctly label an issue are:\n+* Label issue type\n+  * Assign the appropriate issue-type label.\n+  * If the issue is determined to be 'type-undecided', also add the labels 'prio-undecided' and 'status-needs-information'. Add a comment detailing the required information.\n+  * If the issue is determined to be 'type-enhancement-large', the issue should be logged as an idea on the [product roadmap](https://trello.com/b/OdRe9RxX/rpc-engineering-roadmap) and closed here with a link to the roadmap card.\n+  * If the issue is determined to be 'type-enhancement-medium', the issue should be added to the [existing-feature backlog](https://waffle.io/rcbops/u-suk-dev?source=rcbops%2Fu-suk-dev) and closed here with a link to the new card.\n+* Identify the teams impacted by the issue\n+  Any labels relevant to this step will start with 'impacts-'.\n+  * If an issue is reported by support or they update an existing issue to say they are impacted add the label 'impacts-support'.\n+  * If an issue is reported by QE, they update an existing issue to say they are impacted or someone else discovers an issue that affects a release candidate add the label 'impacts-qe'.\n+* Identify the product features impacted by the issue.  \n+  Any labels relevant to this section will start with 'feature-'.\n+* Confirm the issue is valid\n+  * If the issue is invalid add the label 'status-invalid' and close the issue with a comment detailing why the issue is invalid.\n+* Confirm the issue is something that will be fixed\n+  * If the issue is not going to be fixed add the label 'status-wontfix' and close it with a comment explaining why.\n+* Confirm the issue hasn't previously been logged\n+  * If there is a pre-existing issue add the label 'status-duplicate' to this new one and close it with a comment linking to the pre-existing issue.\n+* Determine if the issue is blocked by something\n+  * If the issue is blocked by some other activity add the label 'status-blocked' and add details of the blocker to the issue description.\n+* Prioritise the issue if 'type-bug' or 'type-enhancement-small'\n+  * If there is insufficient information from which to determine the priority add the labels 'prio-undecided' and 'status-needs-information'. Also add a comment detailing the missing information.\n+  * Assign the appropriate priority label based on the definitions of each priority category, if the issue is labeled with 'type-enhancement-small' generally this will be 'prio-3'.\n+\n+#### Triage meetings\n+Triage meetings are held on a weekly basis, with ad hoc meetings held as required. Their main purpose is to review what has been achieved since the last meeting and provide an opportunity to discuss specific cards if there is concern about their current priority. The Waffle board is used to provide this information.\n+\n+##### Triage meeting tasks\n+* Review tasks completed since the last meeting\n+* Review new issues in the backlog\n+* Allow the opportunity to discuss the classification of any open issue that has not already been discussed in the meeting, this should not be used as a chance to rehash old arguments but instead to highlight the case for issues where the circumstances have changed.\n+\n+## Backlog -> Approved\n+Approved is updated with tasks from Backlog if Approved is under its WIP limit. In general the next card to move to Approved will be decided based on priority and age, with the oldest card of the highest priority the next moved. This task will generally be performed by the PTL or Bernardo as and when Approved moves below its WIP limit.\n+\n+## Approved\n+This column shows the work to which the engineering team has currently committed but not yet started.\n+\n+## Approved -> Doing\n+### Selecting an issue to work on\n+Working on a task means moving it from Approved to Doing, this operation is only allowed if it doesn't violate the Doing WIP limit. All available work is found on the Waffle board in Approved, the next task is always at the top. Assign yourself as the owner of the issue at the top and move it from the top of Approved to the bottom of Doing.\n+\n+If a task includes an existing pull request from someone outside the engineering team, they should not be assigned as the owner. All work must be owned by the engineering team, if someone on another team e.g. support has provided code then work with them to get it merged but ultimately it is the responsibility of the engineering team to manage the flow of work and ensure all aspects of a card are completed.\n+\n+## Doing\n+#### Fixing an issue\n+The issue description contains a list of the steps required to close an issue, this is added by the [issue template](.github/ISSUE_TEMPLATE.md). As each step is completed, update the description.\n+\n+##### New issues discovered while working an issue\n+If a new bug or feature requirement is found while working on an assigned issue, that new work item should be logged as a separate issue in Backlog.\n+\n+If the new issue blocks the existing issue, you should assign yourself to the new issue and move it to Doing. The existing issue should be updated with all the work that has been done, the label 'status-blocked' added and a link to the blocking issue should be included in the issue description. In this situation the WIP limit can be exceeded. Similar to situations where the WIP limit prevents new work being started the team needs to work to reduce the WIP so that new tasks can be started.\n+\n+If the new issue does not prevent the resolution of your current task it will be treated as any new issue.\n+\n+##### Creating a pull request\n+If an issue affects multiple branches the owner should always start by creating a pull request for the newest branch, generally this means master. Only one pull request should ever be in progress for a task in Doing.\n+\n+To ensure that issues and pull request are correctly associated, reference the issue at the end of the commit message, e.g.:\n+    Connected https://github.com/rcbops/rpc-openstack/issues/0\n+\n+## Doing -> Needs review\n+A card can only be moved from Doing to Needs-review if Needs-review is below its WIP limit. If that condition is met and you are ready for feedback on your pull request, move the card (this should be a connected pair of the issue and pull request) to the bottom of Needs-review.\n+\n+## Needs review\n+Reviewers should always review the tasks in the order the are listed in Needs-review. If owners need to make changes to the pull request, for example base on feedback from reviewers, the task should remain in Needs-review while that is done. The reviewer merging the commit should delete the issue branch (using the link on the pull request page) and tick the issue checklist for the fixed branch.","path":"CONTRIBUTING.md","position":144,"original_position":144,"commit_id":"45b2a96086c4bd74a6b2e73ff94ce2d84e42800d","original_commit_id":"45b2a96086c4bd74a6b2e73ff94ce2d84e42800d","user":{"login":"prometheanfire","id":1869923,"avatar_url":"https://avatars.githubusercontent.com/u/1869923?v=3","gravatar_id":"","url":"https://api.github.com/users/prometheanfire","html_url":"https://github.com/prometheanfire","followers_url":"https://api.github.com/users/prometheanfire/followers","following_url":"https://api.github.com/users/prometheanfire/following{/other_user}","gists_url":"https://api.github.com/users/prometheanfire/gists{/gist_id}","starred_url":"https://api.github.com/users/prometheanfire/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/prometheanfire/subscriptions","organizations_url":"https://api.github.com/users/prometheanfire/orgs","repos_url":"https://api.github.com/users/prometheanfire/repos","events_url":"https://api.github.com/users/prometheanfire/events{/privacy}","received_events_url":"https://api.github.com/users/prometheanfire/received_events","type":"User","site_admin":false},"body":"Who manages this order?","created_at":"2016-07-11T14:30:53Z","updated_at":"2016-07-11T14:30:53Z","html_url":"https://github.com/rcbops/rpc-openstack/pull/1229#discussion_r70268317","pull_request_url":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/1229","_links":{"self":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/comments/70268317"},"html":{"href":"https://github.com/rcbops/rpc-openstack/pull/1229#discussion_r70268317"},"pull_request":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/1229"}}},"pull_request":{"url":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/1229","id":76781584,"html_url":"https://github.com/rcbops/rpc-openstack/pull/1229","diff_url":"https://github.com/rcbops/rpc-openstack/pull/1229.diff","patch_url":"https://github.com/rcbops/rpc-openstack/pull/1229.patch","issue_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/1229","number":1229,"state":"open","locked":false,"title":"Update guidelines for issue triage and workflow","user":{"login":"git-harry","id":687171,"avatar_url":"https://avatars.githubusercontent.com/u/687171?v=3","gravatar_id":"","url":"https://api.github.com/users/git-harry","html_url":"https://github.com/git-harry","followers_url":"https://api.github.com/users/git-harry/followers","following_url":"https://api.github.com/users/git-harry/following{/other_user}","gists_url":"https://api.github.com/users/git-harry/gists{/gist_id}","starred_url":"https://api.github.com/users/git-harry/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/git-harry/subscriptions","organizations_url":"https://api.github.com/users/git-harry/orgs","repos_url":"https://api.github.com/users/git-harry/repos","events_url":"https://api.github.com/users/git-harry/events{/privacy}","received_events_url":"https://api.github.com/users/git-harry/received_events","type":"User","site_admin":false},"body":"This change updates the contributing guidelines to define the workflow\r\nby which issues are managed. This includes detailing the steps that take\r\nan issue from the backlog to being done as well as providing a more\r\ncomplete picture of the process for triaging issues.","created_at":"2016-07-08T16:48:40Z","updated_at":"2016-07-11T14:30:53Z","closed_at":null,"merged_at":null,"merge_commit_sha":"32703b477ab2558fabb9fc2977b7d6e526e552ef","assignee":null,"assignees":[],"milestone":null,"commits_url":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/1229/commits","review_comments_url":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/1229/comments","review_comment_url":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/comments{/number}","comments_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/1229/comments","statuses_url":"https://api.github.com/repos/rcbops/rpc-openstack/statuses/45b2a96086c4bd74a6b2e73ff94ce2d84e42800d","head":{"label":"rcbops:issue_management","ref":"issue_management","sha":"45b2a96086c4bd74a6b2e73ff94ce2d84e42800d","user":{"login":"rcbops","id":1153548,"avatar_url":"https://avatars.githubusercontent.com/u/1153548?v=3","gravatar_id":"","url":"https://api.github.com/users/rcbops","html_url":"https://github.com/rcbops","followers_url":"https://api.github.com/users/rcbops/followers","following_url":"https://api.github.com/users/rcbops/following{/other_user}","gists_url":"https://api.github.com/users/rcbops/gists{/gist_id}","starred_url":"https://api.github.com/users/rcbops/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rcbops/subscriptions","organizations_url":"https://api.github.com/users/rcbops/orgs","repos_url":"https://api.github.com/users/rcbops/repos","events_url":"https://api.github.com/users/rcbops/events{/privacy}","received_events_url":"https://api.github.com/users/rcbops/received_events","type":"Organization","site_admin":false},"repo":{"id":30100099,"name":"rpc-openstack","full_name":"rcbops/rpc-openstack","owner":{"login":"rcbops","id":1153548,"avatar_url":"https://avatars.githubusercontent.com/u/1153548?v=3","gravatar_id":"","url":"https://api.github.com/users/rcbops","html_url":"https://github.com/rcbops","followers_url":"https://api.github.com/users/rcbops/followers","following_url":"https://api.github.com/users/rcbops/following{/other_user}","gists_url":"https://api.github.com/users/rcbops/gists{/gist_id}","starred_url":"https://api.github.com/users/rcbops/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rcbops/subscriptions","organizations_url":"https://api.github.com/users/rcbops/orgs","repos_url":"https://api.github.com/users/rcbops/repos","events_url":"https://api.github.com/users/rcbops/events{/privacy}","received_events_url":"https://api.github.com/users/rcbops/received_events","type":"Organization","site_admin":false},"private":false,"html_url":"https://github.com/rcbops/rpc-openstack","description":"Rackspace Private Cloud Offering based on OpenStack","fork":false,"url":"https://api.github.com/repos/rcbops/rpc-openstack","forks_url":"https://api.github.com/repos/rcbops/rpc-openstack/forks","keys_url":"https://api.github.com/repos/rcbops/rpc-openstack/keys{/key_id}","collaborators_url":"https://api.github.com/repos/rcbops/rpc-openstack/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/rcbops/rpc-openstack/teams","hooks_url":"https://api.github.com/repos/rcbops/rpc-openstack/hooks","issue_events_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/events{/number}","events_url":"https://api.github.com/repos/rcbops/rpc-openstack/events","assignees_url":"https://api.github.com/repos/rcbops/rpc-openstack/assignees{/user}","branches_url":"https://api.github.com/repos/rcbops/rpc-openstack/branches{/branch}","tags_url":"https://api.github.com/repos/rcbops/rpc-openstack/tags","blobs_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/refs{/sha}","trees_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/trees{/sha}","statuses_url":"https://api.github.com/repos/rcbops/rpc-openstack/statuses/{sha}","languages_url":"https://api.github.com/repos/rcbops/rpc-openstack/languages","stargazers_url":"https://api.github.com/repos/rcbops/rpc-openstack/stargazers","contributors_url":"https://api.github.com/repos/rcbops/rpc-openstack/contributors","subscribers_url":"https://api.github.com/repos/rcbops/rpc-openstack/subscribers","subscription_url":"https://api.github.com/repos/rcbops/rpc-openstack/subscription","commits_url":"https://api.github.com/repos/rcbops/rpc-openstack/commits{/sha}","git_commits_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/commits{/sha}","comments_url":"https://api.github.com/repos/rcbops/rpc-openstack/comments{/number}","issue_comment_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/comments{/number}","contents_url":"https://api.github.com/repos/rcbops/rpc-openstack/contents/{+path}","compare_url":"https://api.github.com/repos/rcbops/rpc-openstack/compare/{base}...{head}","merges_url":"https://api.github.com/repos/rcbops/rpc-openstack/merges","archive_url":"https://api.github.com/repos/rcbops/rpc-openstack/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/rcbops/rpc-openstack/downloads","issues_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues{/number}","pulls_url":"https://api.github.com/repos/rcbops/rpc-openstack/pulls{/number}","milestones_url":"https://api.github.com/repos/rcbops/rpc-openstack/milestones{/number}","notifications_url":"https://api.github.com/repos/rcbops/rpc-openstack/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/rcbops/rpc-openstack/labels{/name}","releases_url":"https://api.github.com/repos/rcbops/rpc-openstack/releases{/id}","deployments_url":"https://api.github.com/repos/rcbops/rpc-openstack/deployments","created_at":"2015-01-31T02:51:12Z","updated_at":"2016-07-10T07:05:09Z","pushed_at":"2016-07-11T09:31:29Z","git_url":"git://github.com/rcbops/rpc-openstack.git","ssh_url":"git@github.com:rcbops/rpc-openstack.git","clone_url":"https://github.com/rcbops/rpc-openstack.git","svn_url":"https://github.com/rcbops/rpc-openstack","homepage":"","size":2615,"stargazers_count":28,"watchers_count":28,"language":"Python","has_issues":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":40,"mirror_url":null,"open_issues_count":121,"forks":40,"open_issues":121,"watchers":28,"default_branch":"master"}},"base":{"label":"rcbops:master","ref":"master","sha":"b18bf6a9204826ffab998b398f65029de97699f8","user":{"login":"rcbops","id":1153548,"avatar_url":"https://avatars.githubusercontent.com/u/1153548?v=3","gravatar_id":"","url":"https://api.github.com/users/rcbops","html_url":"https://github.com/rcbops","followers_url":"https://api.github.com/users/rcbops/followers","following_url":"https://api.github.com/users/rcbops/following{/other_user}","gists_url":"https://api.github.com/users/rcbops/gists{/gist_id}","starred_url":"https://api.github.com/users/rcbops/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rcbops/subscriptions","organizations_url":"https://api.github.com/users/rcbops/orgs","repos_url":"https://api.github.com/users/rcbops/repos","events_url":"https://api.github.com/users/rcbops/events{/privacy}","received_events_url":"https://api.github.com/users/rcbops/received_events","type":"Organization","site_admin":false},"repo":{"id":30100099,"name":"rpc-openstack","full_name":"rcbops/rpc-openstack","owner":{"login":"rcbops","id":1153548,"avatar_url":"https://avatars.githubusercontent.com/u/1153548?v=3","gravatar_id":"","url":"https://api.github.com/users/rcbops","html_url":"https://github.com/rcbops","followers_url":"https://api.github.com/users/rcbops/followers","following_url":"https://api.github.com/users/rcbops/following{/other_user}","gists_url":"https://api.github.com/users/rcbops/gists{/gist_id}","starred_url":"https://api.github.com/users/rcbops/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rcbops/subscriptions","organizations_url":"https://api.github.com/users/rcbops/orgs","repos_url":"https://api.github.com/users/rcbops/repos","events_url":"https://api.github.com/users/rcbops/events{/privacy}","received_events_url":"https://api.github.com/users/rcbops/received_events","type":"Organization","site_admin":false},"private":false,"html_url":"https://github.com/rcbops/rpc-openstack","description":"Rackspace Private Cloud Offering based on OpenStack","fork":false,"url":"https://api.github.com/repos/rcbops/rpc-openstack","forks_url":"https://api.github.com/repos/rcbops/rpc-openstack/forks","keys_url":"https://api.github.com/repos/rcbops/rpc-openstack/keys{/key_id}","collaborators_url":"https://api.github.com/repos/rcbops/rpc-openstack/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/rcbops/rpc-openstack/teams","hooks_url":"https://api.github.com/repos/rcbops/rpc-openstack/hooks","issue_events_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/events{/number}","events_url":"https://api.github.com/repos/rcbops/rpc-openstack/events","assignees_url":"https://api.github.com/repos/rcbops/rpc-openstack/assignees{/user}","branches_url":"https://api.github.com/repos/rcbops/rpc-openstack/branches{/branch}","tags_url":"https://api.github.com/repos/rcbops/rpc-openstack/tags","blobs_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/refs{/sha}","trees_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/trees{/sha}","statuses_url":"https://api.github.com/repos/rcbops/rpc-openstack/statuses/{sha}","languages_url":"https://api.github.com/repos/rcbops/rpc-openstack/languages","stargazers_url":"https://api.github.com/repos/rcbops/rpc-openstack/stargazers","contributors_url":"https://api.github.com/repos/rcbops/rpc-openstack/contributors","subscribers_url":"https://api.github.com/repos/rcbops/rpc-openstack/subscribers","subscription_url":"https://api.github.com/repos/rcbops/rpc-openstack/subscription","commits_url":"https://api.github.com/repos/rcbops/rpc-openstack/commits{/sha}","git_commits_url":"https://api.github.com/repos/rcbops/rpc-openstack/git/commits{/sha}","comments_url":"https://api.github.com/repos/rcbops/rpc-openstack/comments{/number}","issue_comment_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/comments{/number}","contents_url":"https://api.github.com/repos/rcbops/rpc-openstack/contents/{+path}","compare_url":"https://api.github.com/repos/rcbops/rpc-openstack/compare/{base}...{head}","merges_url":"https://api.github.com/repos/rcbops/rpc-openstack/merges","archive_url":"https://api.github.com/repos/rcbops/rpc-openstack/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/rcbops/rpc-openstack/downloads","issues_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues{/number}","pulls_url":"https://api.github.com/repos/rcbops/rpc-openstack/pulls{/number}","milestones_url":"https://api.github.com/repos/rcbops/rpc-openstack/milestones{/number}","notifications_url":"https://api.github.com/repos/rcbops/rpc-openstack/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/rcbops/rpc-openstack/labels{/name}","releases_url":"https://api.github.com/repos/rcbops/rpc-openstack/releases{/id}","deployments_url":"https://api.github.com/repos/rcbops/rpc-openstack/deployments","created_at":"2015-01-31T02:51:12Z","updated_at":"2016-07-10T07:05:09Z","pushed_at":"2016-07-11T09:31:29Z","git_url":"git://github.com/rcbops/rpc-openstack.git","ssh_url":"git@github.com:rcbops/rpc-openstack.git","clone_url":"https://github.com/rcbops/rpc-openstack.git","svn_url":"https://github.com/rcbops/rpc-openstack","homepage":"","size":2615,"stargazers_count":28,"watchers_count":28,"language":"Python","has_issues":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":40,"mirror_url":null,"open_issues_count":121,"forks":40,"open_issues":121,"watchers":28,"default_branch":"master"}},"_links":{"self":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/1229"},"html":{"href":"https://github.com/rcbops/rpc-openstack/pull/1229"},"issue":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/issues/1229"},"comments":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/issues/1229/comments"},"review_comments":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/1229/comments"},"review_comment":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/comments{/number}"},"commits":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/pulls/1229/commits"},"statuses":{"href":"https://api.github.com/repos/rcbops/rpc-openstack/statuses/45b2a96086c4bd74a6b2e73ff94ce2d84e42800d"}}}}
{"actor":{"display_login":"prometheanfire"}}