Update references following graduation

CONTRIBUTING.md

@@ -6,10 +6,10 @@ There are two main forms of contribution: reporting issues and performing code c
 
 ## Reporting Issues
 
-If you find a problem with Stratos UI, report it using [GitHub issues](https://github.com/cloudfoundry-incubator/stratos/issues/new).
+If you find a problem with Stratos UI, report it using [GitHub issues](https://github.com/cloudfoundry/stratos/issues/new).
 
 Before reporting a new issue, please take a moment to check whether it has already been reported
-[here](https://github.com/cloudfoundry-incubator/stratos/issues). If this is the case, please:
+[here](https://github.com/cloudfoundry/stratos/issues). If this is the case, please:
 
 - Read all the comments to confirm that it's the same issue you're having.
 - Refrain from adding "same thing here" or "+1" comments. Just hit the

README.md

@@ -1,16 +1,16 @@
 # Stratos
 
-<a href="https://travis-ci.org/cloudfoundry-incubator/stratos/branches"><img src="https://travis-ci.org/cloudfoundry-incubator/stratos.svg?branch=v2-master"></a>&nbsp;<a style="padding-left: 4px" href="https://codeclimate.com/github/cloudfoundry-incubator/stratos/maintainability"><img src="https://api.codeclimate.com/v1/badges/61af8b605f385e894632/maintainability" /></a>
+<a href="https://travis-ci.org/cloudfoundry/stratos/branches"><img src="https://travis-ci.org/cloudfoundry-incubator/stratos.svg?branch=v2-master"></a>&nbsp;<a style="padding-left: 4px" href="https://codeclimate.com/github/cloudfoundry/stratos/maintainability"><img src="https://api.codeclimate.com/v1/badges/61af8b605f385e894632/maintainability" /></a>
 <a href="https://goreportcard.com/github.com/cloudfoundry-incubator/stratos"><img src="https://goreportcard.com/badge/github.com/cloudfoundry-incubator/stratos"/></a>
-<a href="https://codecov.io/gh/cloudfoundry-incubator/stratos/branch/v2-master"><img src="https://codecov.io/gh/cloudfoundry-incubator/stratos/branch/v2-master/graph/badge.svg"/></a>
-[![GitHub release](https://img.shields.io/github/release/cloudfoundry-incubator/stratos.svg)](https://github.com/cloudfoundry-incubator/stratos/releases/latest)
-[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://github.com/cloudfoundry-incubator/stratos/blob/master/LICENSE)
+<a href="https://codecov.io/gh/cloudfoundry/stratos/branch/v2-master"><img src="https://codecov.io/gh/cloudfoundry/stratos/branch/v2-master/graph/badge.svg"/></a>
+[![GitHub release](https://img.shields.io/github/release/cloudfoundry-incubator/stratos.svg)](https://github.com/cloudfoundry/stratos/releases/latest)
+[![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://github.com/cloudfoundry/stratos/blob/master/LICENSE)
 [![slack.cloudfoundry.org](https://slack.cloudfoundry.org/badge.svg)](https://cloudfoundry.slack.com/messages/C80EP4Y57/)
 
 
 Stratos is an Open Source Web-based UI (Console) for managing Cloud Foundry. It allows users and administrators to both manage applications running in the Cloud Foundry cluster and perform cluster management tasks.
 
-If you are looking for the V1 version of Stratos, you can find it in the [master](https://github.com/cloudfoundry-incubator/stratos/tree/master) branch.
+If you are looking for the V1 version of Stratos, you can find it in the [master](https://github.com/cloudfoundry/stratos/tree/master) branch.
 
 ![Stratos Application view](docs/images/screenshots/app-summary.png)
 
@@ -39,7 +39,7 @@ Please see our [Troubleshooting](docs/troubleshooting) page.
 ## Project Planning
 We use [ZenHub](https://zenhub.com) for project planning. Feel free to head over to the [Boards](https://github.com/cloudfoundry-incubator/stratos#boards)
 tab and have a look through our pipelines and milestones. Please note in order to view the Github ZenHub Boards tab you will need the [ZenHub
-browser extension](https://www.zenhub.com/extension). Alternatively, to view the planning board without the extension visit our [ZenHub Project Page](https://app.zenhub.com/workspace/o/cloudfoundry-incubator/stratos/boards)
+browser extension](https://www.zenhub.com/extension). Alternatively, to view the planning board without the extension visit our [ZenHub Project Page](https://app.zenhub.com/workspace/o/cloudfoundry/stratos/boards)
 
 ## Further Reading
 
@@ -49,7 +49,7 @@ Get an [Overview](docs/overview.md) of Stratos, its components and the different
 
 Take a look at the [Development Roadmap](docs/roadmap.md) to see where we are heading. We update our status page each week to summarize what we are working on - see the [Status Page](docs/status_updates.md).
 
-Browse through features and issues in the project's [issues](https://github.com/cloudfoundry-incubator/stratos/issues) page or [Zenhub Board](https://github.com/cloudfoundry-incubator/stratos#boards).
+Browse through features and issues in the project's [issues](https://github.com/cloudfoundry/stratos/issues) page or [Zenhub Board](https://github.com/cloudfoundry-incubator/stratos#boards).
 
 What kind of code is in Stratos? We've integrated [Code Climate](https://codeclimate.com) for some code quality and maintainability metrics. Take a stroll around the [project page](https://codeclimate.com/github/cloudfoundry-incubator/stratos)
 

deploy/ci/automation/helmtest.sh

@@ -18,7 +18,7 @@ set -e
 
 NAME=stratos-test
 NAMESPACE=stratos-ns
-HELM_REPO=https://cloudfoundry-incubator.github.io/stratos
+HELM_REPO=https://cloudfoundry.github.io/stratos
 HELM_REPO_NAME=cfstratos
 
 DEV_IMAGE_VERSION=2.0.0-dev

deploy/cloud-foundry/README.md

@@ -73,7 +73,7 @@ and binding a database service instance to Stratos - for more information see [h
 To do so, `clone` the **stratos** repository, `cd` into the newly cloned repository and `push` to Cloud Foundry. This can be done with:
 
 ```
-git clone https://github.com/cloudfoundry-incubator/stratos
+git clone https://github.com/cloudfoundry/stratos
 cd stratos
 git checkout tags/stable -b stable
 ./build/store-git-metadata.sh
@@ -91,7 +91,7 @@ If you wish to enable AOT or reduce the push time, you can pre-build the UI befo
 This can be done with:
 
 ```
-git clone https://github.com/cloudfoundry-incubator/stratos
+git clone https://github.com/cloudfoundry/stratos
 cd stratos
 npm install
 npm run prebuild-ui
@@ -289,7 +289,7 @@ applications:
   disk_quota: 256M
   host: console
   timeout: 180
-  buildpack: https://github.com/cloudfoundry-incubator/stratos-buildpack
+  buildpack: https://github.com/cloudfoundry/stratos-buildpack
   health-check-type: port
   env:
     CF_API_URL: https://<<CLOUD FOUNDRY API ENDPOINT>>>
@@ -306,7 +306,7 @@ applications:
   disk_quota: 256M
   host: console
   timeout: 180
-  buildpack: https://github.com/cloudfoundry-incubator/stratos-buildpack
+  buildpack: https://github.com/cloudfoundry/stratos-buildpack
   health-check-type: port
   env:
     CF_API_FORCE_SECURE: true

deploy/kubernetes/README.md

@@ -79,7 +79,7 @@ You can deploy Stratos from one of three different sources:
 
 Add the Helm repository to your helm installation
 ```
-helm repo add stratos https://cloudfoundry-incubator.github.io/stratos
+helm repo add stratos https://cloudfoundry.github.io/stratos
 ```
 Check the repository was successfully added by searching for the `console`
 ```
@@ -102,7 +102,7 @@ After the install, you should be able to access the Console in a web browser by
 
 ### Deploy using an archive of the Helm Chart
 
-Helm chart archives are available for Stratos releases from our GitHub repository, under releases - see https://github.com/cloudfoundry-incubator/stratos/releases.
+Helm chart archives are available for Stratos releases from our GitHub repository, under releases - see https://github.com/cloudfoundry/stratos/releases.
 
 Download the appropriate release `console-helm-chart.X.Y.Z.tgz` from the GitHub repository and unpack the archive to a local folder. The Helm Chart will be extracted to a sub-folder named `console`.
 
@@ -119,7 +119,7 @@ helm install console --namespace=console --name my-console
 Clone the Stratos GitHub repository:
 
 ```
-git clone https://github.com/cloudfoundry-incubator/stratos.git
+git clone https://github.com/cloudfoundry/stratos.git
 ```
 
 Open a terminal and cd to the `deploy/kubernetes` directory:

docs/cf-api-v2-usage.md

@@ -772,7 +772,7 @@ Endpoint | Inline Relations | Notes
 
 #### Others
 The include-relations property is populated by walking our relationship tree, so for a complete and exhaustive list of all possible
-relations please see the [`entity-factory.ts`](https://github.com/cloudfoundry-incubator/stratos/blob/v2-master/src/frontend/app/store/helpers/entity-factory.ts).
+relations please see the [`entity-factory.ts`](https://github.com/cloudfoundry/stratos/blob/v2-master/src/frontend/app/store/helpers/entity-factory.ts).
 
 In terms of api requests we also make use of...
 

docs/cf-api-v3.md

@@ -120,13 +120,13 @@ Then Stratos should either ..
   - To do this ...
     - Query params need to be converted when making v3 requests
     - v3 responses need to be converted into v2 format (entity/metadata, `<x>_url`, etc).
-- Update application deploy/lifecycle process to match new v3 process (https://github.com/cloudfoundry-incubator/stratos/issues/3150)
-- Support new 'processes' concept (https://github.com/cloudfoundry-incubator/stratos/issues/3154), including updating how
+- Update application deploy/lifecycle process to match new v3 process (https://github.com/cloudfoundry/stratos/issues/3150)
+- Support new 'processes' concept (https://github.com/cloudfoundry/stratos/issues/3154), including updating how
   we determine application state
 - Fully investigate non `get` methods (create an application, delete a space, etc)
 - Related Issues
-  - https://github.com/cloudfoundry-incubator/stratos/issues/2922
-  - https://github.com/cloudfoundry-incubator/stratos/issues/3149 (Container issue for related v3 api process changes)
+  - https://github.com/cloudfoundry/stratos/issues/2922
+  - https://github.com/cloudfoundry/stratos/issues/3149 (Container issue for related v3 api process changes)
 
 ### Questions
 - ~~Will `include` cover children of children? For instance `app` --> `route` --> `domain`~~

docs/contributing.md

@@ -3,7 +3,7 @@
 ## Reporting issues
 
 Before reporting an issue, please check whether it has already been reported
-[here](https://github.com/cloudfoundry-incubator/stratos/issues). If this is the case, please:
+[here](https://github.com/cloudfoundry/stratos/issues). If this is the case, please:
 
 - Read all the comments to confirm that it's the same issue you're having.
 - Refrain from adding "same thing here" or "+1" comments. Just hit the

docs/developers-guide.md

@@ -26,7 +26,7 @@ using Visual Studio Code. If you feel comfortable with these and are happy with
 ### Set up Dependencies
 
 * Set up a Stratos backend - The frontend cannot run without a backend. Both backend and frontend exist in this same repo.
-  * Don't need to make changes to the backend code? To set up a backend run through the [deploy section](https://github.com/cloudfoundry-incubator/stratos/blob/master/deploy/README.md),
+  * Don't need to make changes to the backend code? To set up a backend run through the [deploy section](https://github.com/cloudfoundry/stratos/blob/master/deploy/README.md),
     choose a deployment method and bring one up. These deployments will bring up the entire backend, including api service and database
     along with a V2 frontend.
   * Need to make changes to the backend code? Follow the below [Backend Development](#Backend-Development) set up guide
@@ -40,7 +40,7 @@ Configuration information can be found in two places
 * `./proxy.conf.js`
   * In new forks this is missing and needs to be created using `./proxy.conf.template.js` as a template.
   * Contains the address of the backend. Which will either be...
-     * If the backend is deployed via the instructions in the [deploy section](https://github.com/cloudfoundry-incubator/stratos/blob/master/deploy/README.md)
+     * If the backend is deployed via the instructions in the [deploy section](https://github.com/cloudfoundry/stratos/blob/master/deploy/README.md)
        the url will be the same address as the V1 console's frontend address. For instance `https://localhost` would translate to
         ```
         const PROXY_CONFIG = {

docs/features.md

@@ -1,6 +1,6 @@
 # Features
 
-> **NOTE** This branch is a work-in-progress Angular 2.x version of Stratos. For the current Angular 1 based version see [https://github.com/cloudfoundry-incubator/stratos/tree/master](https://github.com/cloudfoundry-incubator/stratos/tree/master). This version is at an early development stage and we welcome feedback, input and contributions. This version does not currently have feature parity with the Angular 1 version specified below - see the [Development Roadmap](docs/roadmap.md) for more information.
+> **NOTE** This branch is a work-in-progress Angular 2.x version of Stratos. For the current Angular 1 based version see [https://github.com/cloudfoundry/stratos/tree/master](https://github.com/cloudfoundry/stratos/tree/master). This version is at an early development stage and we welcome feedback, input and contributions. This version does not currently have feature parity with the Angular 1 version specified below - see the [Development Roadmap](docs/roadmap.md) for more information.
 
 Stratos provides the feature set outline below. Some of these are illustrated in the [Screenshots gallery](images/screenshots/README.md).
 

docs/planning/services.md

@@ -1,6 +1,6 @@
 # Services
 
-GitHub issue: [\#1391](https://github.com/cloudfoundry-incubator/stratos/issues/1391)
+GitHub issue: [\#1391](https://github.com/cloudfoundry/stratos/issues/1391)
 
 The goal with this feature is to provide first-class Services support in Stratos. Up until now, Services support was limited to:
 
@@ -109,7 +109,7 @@ When a specific service plan is selected, the following considerations need to b
 3. If a service plan is not `public` and no service visibility exists for it, the user should not be able to select the plan.
 4. If the service plan is provided by a service broker that is space-scoped, then the values for the organisation and space should be pre-populated and locked.
 
-The wizard should support parameters with generated form created from JSON schema, see [stratos/issues/1434](https://github.com/cloudfoundry-incubator/stratos/issues/1434) 
+The wizard should support parameters with generated form created from JSON schema, see [stratos/issues/1434](https://github.com/cloudfoundry/stratos/issues/1434) 
 #### Org/Space driven Flow
 From the top level Services view, the user should be able to create a new instance. In this flow however, the user starts with selecting the organisation and space they want to create the service instance in.
 Based on that selection, the appropriate service definitions and service plans should be displayed, following the same considerations as specified for the previous flow.

docs/roadmap.md

@@ -20,20 +20,20 @@ Post 2.0 is released we will be working towards a regular recycle cycle each Spr
 
 We work on a 2-week Sprint cycle. Sprints start on Wednesdays. For reference, Sprint 27 started 4 April 2018.
 
-We are using GitHub issues to track all work items. See: https://github.com/cloudfoundry-incubator/stratos/issues
+We are using GitHub issues to track all work items. See: https://github.com/cloudfoundry/stratos/issues
 
 ## High-Level Features
 
-The high-level features that we schedule into the roadmap are identified by the ```feature-request``` label. You can see the current set of features [here](https://github.com/cloudfoundry-incubator/stratos/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request).
+The high-level features that we schedule into the roadmap are identified by the ```feature-request``` label. You can see the current set of features [here](https://github.com/cloudfoundry/stratos/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request).
 
 ### Near-term roadmap
 
 |#|Description|Issue|Notes|
 |---|---|---|---|
-|1|Technology Refresh (AngularJS => Angular)|[\#1972](https://github.com/cloudfoundry-incubator/stratos/issues/1972)|[Notes](planning/angular.md)|
-|2|1st class support for service plan & service instance|[\#1391](https://github.com/cloudfoundry-incubator/stratos/issues/1391)|[Notes](planning/services.md)|
-|3|Add support for Application and CF Metrics|[\#1985](https://github.com/cloudfoundry-incubator/stratos/issues/1985)|[Notes](planning/metrics.md)|
-|4|Support UAA login UX directly (SSO)|[\#1384](https://github.com/cloudfoundry-incubator/stratos/issues/1384)||
-|5|Support per-endpoint Client ID and Client Secret|[\#2220](https://github.com/cloudfoundry-incubator/stratos/issues/2220)||
-|6|Bring Orgs and Spaces view to top-level|[\#2619](https://github.com/cloudfoundry-incubator/stratos/issues/2619)||
-|7|Deploy application: Enable deploying from private Git repositories|[\#1442](https://github.com/cloudfoundry-incubator/stratos/issues/1442)||
+|1|Technology Refresh (AngularJS => Angular)|[\#1972](https://github.com/cloudfoundry/stratos/issues/1972)|[Notes](planning/angular.md)|
+|2|1st class support for service plan & service instance|[\#1391](https://github.com/cloudfoundry/stratos/issues/1391)|[Notes](planning/services.md)|
+|3|Add support for Application and CF Metrics|[\#1985](https://github.com/cloudfoundry/stratos/issues/1985)|[Notes](planning/metrics.md)|
+|4|Support UAA login UX directly (SSO)|[\#1384](https://github.com/cloudfoundry/stratos/issues/1384)||
+|5|Support per-endpoint Client ID and Client Secret|[\#2220](https://github.com/cloudfoundry/stratos/issues/2220)||
+|6|Bring Orgs and Spaces view to top-level|[\#2619](https://github.com/cloudfoundry/stratos/issues/2619)||
+|7|Deploy application: Enable deploying from private Git repositories|[\#1442](https://github.com/cloudfoundry/stratos/issues/1442)||