HoldTillRename: Rename knative-sandbox to knative-extensions

.github/ISSUE_TEMPLATE/new-repo.md

@@ -1,17 +1,17 @@
 ---
 name: Request a new repo
-about: Request creation of a new repo in the knative or knative-sandbox orgs
+about: Request creation of a new repo in the knative or knative-extensions orgs
 title: "New Repo: `$REPONAME`"
 ---
 
-Use this issue type to request a new repo in `knative-sandbox` (or
+Use this issue type to request a new repo in `knative-extensions` (or
 `knative`, which may require additional discussion).
 
 <!-- Update the information below with your request -->
 
 ## Repo information
 
-Org: `knative-sandbox`
+Org: `knative-extensions`
 
 Repo: `$REPONAME`
 
@@ -31,7 +31,7 @@ The TOC is involved only in the **TOC Gate** steps.
 
 _You may not be able to use the Projects quick menu on this page. In that case, go to the project board and use the **Add cards** interface._
 
-- [ ] Send a PR adding entries for this repo in [`/peribolos/knative-sandbox.yaml`](https://github.com/knative/community/blob/main/peribolos/knative-sandbox.yaml). Please mind the alphabetical order when adding to a list.
+- [ ] Send a PR adding entries for this repo in [`/peribolos/knative-extensions.yaml`](https://github.com/knative/community/blob/main/peribolos/knative-extensions.yaml). Please mind the alphabetical order when adding to a list.
   - [ ] Add the repository and a description.
   - [ ] Grant `Knative Admin` the `admin` privilege.
   - [ ] Grant the sponsoring WG the `write` privilege.
@@ -43,15 +43,15 @@ _You may not be able to use the Projects quick menu on this page. In that case,
 - [ ] (golang) Send a PR to add aliases for `knative.dev/$REPONAME` import paths ([sample](https://github.com/knative/docs/pull/4160)).
 
 - [ ] Have a lead from the sponsoring WG bootstrap the Git repository by pushing an
-  appropriate "template" repository ([basic](https://github.com/knative-sandbox/wg-repository),
-  [sample-controller](https://github.com/knative-sandbox/sample-controller),
-  [sample-source](https://github.com/knative-sandbox/sample-source)) to the new repository as
+  appropriate "template" repository ([basic](https://github.com/knative-extensions/wg-repository),
+  [sample-controller](https://github.com/knative-extensions/sample-controller),
+  [sample-source](https://github.com/knative-extensions/sample-source)) to the new repository as
   a git remote.  For example:
 
   ```shell
-    git clone https://github.com/knative-sandbox/sample-controller.git
+    git clone https://github.com/knative-extensions/sample-controller.git
     cd sample-controller
-    git remote add newrepo https://github.com/knative-sandbox/$REPONAME.git
+    git remote add newrepo https://github.com/knative-extensions/$REPONAME.git
     git push newrepo main
   ```
 
@@ -66,4 +66,4 @@ _You may not be able to use the Projects quick menu on this page. In that case,
 - [ ] Verify that within 24 hours the appropriate branch protections have been applied
    requiring `tide` to pass before PRs are merged.
 
-- [ ] (optional) Send a PR adding the repo to [knobots](https://github.com/knative-sandbox/knobots).
+- [ ] (optional) Send a PR adding the repo to [knobots](https://github.com/knative-extensions/knobots).

.github/workflows/peribolos-schema-validate.yaml

@@ -32,5 +32,5 @@ jobs:
     - run: pip install strictyaml
     - name: Validate knative.yaml
       run: python3 peribolos/validate-schema.py peribolos/knative.yaml
-    - name: Validate knative-sandbox.yaml
-      run: python3 peribolos/validate-schema.py peribolos/knative-sandbox.yaml
+    - name: Validate knative-extensions.yaml
+      run: python3 peribolos/validate-schema.py peribolos/knative-extensions.yaml

.github/workflows/verify.yaml

@@ -14,7 +14,7 @@
 
 # This file is **********NOT********** automagically synced here by knobots
 # because its too hard to opt-in to a single action. See
-# https://github.com/knative-sandbox/knobots/pull/99 for a potential solution.
+# https://github.com/knative-extensions/knobots/pull/99 for a potential solution.
 
 name: Verify
 

REPOSITORY-GUIDELINES.md

@@ -96,23 +96,23 @@ repository is retired and no longer maintained.
 
 It is beneficial for Knative working groups to be able to own code outside the
 core `knative` organization, which is kept intentionally small and has a high
-bar for entry.  The `knative-sandbox` GitHub organization was created for this
-purpose.  Repositories in `knative-sandbox` are intended to give working groups
+bar for entry.  The `knative-extensions` GitHub organization was created for this
+purpose.  Repositories in `knative-extensions` are intended to give working groups
 more latitude to experiment with new ideas and to self-organize and manage
 contributions which may be important to the project but which do not need the
 level of governance of the core project.
 
-Note that `knative-sandbox` is **not** an incubation area for projects entering
+Note that `knative-extensions` is **not** an incubation area for projects entering
 the `knative` github org; in most cases, projects in the sandbox will remain
-there for the entire duration. `knative-sandbox` also provides a location for
+there for the entire duration. `knative-extensions` also provides a location for
 implementations of core interfaces which do not themselves need to be part of
 every knative installation, such as networking or eventing integrations. In the
 event that a working group wants a project in sandbox to be considered for
 transfer to the `knative` org, the request will be considered on a case-by-case
 basis by joint decision of the Steering Committee and the Technical Oversight
 Committee.
 
-### Mechanics of working-group owned repositories in `knative-sandbox`
+### Mechanics of working-group owned repositories in `knative-extensions`
 
 #### Creation
 
@@ -189,7 +189,7 @@ The following are not required to create a working-group-owned repository:
 ### The fine print
 
 Steering and Trademark reserve the right to require that repos be removed or
-transferred out of the `knative-sandbox` organization and API groups to be
+transferred out of the `knative-extensions` organization and API groups to be
 renamed. This is intended to simplify the process in the common case, while
 giving Steering or Trademark the ability to step in and rectify problems that
 may arise.
@@ -198,7 +198,7 @@ may arise.
 
 Working groups are responsible for the upkeep of their repositories and are
 expected to keep a high quality bar. Inactive or non-conforming repositories
-should be archived, deleted, or moved out of the `knative-sandbox` organization,
+should be archived, deleted, or moved out of the `knative-extensions` organization,
 following the general [Procedure for Removal](#procedure-for-removal) for
 repositories.
 

ROLES.md

@@ -113,7 +113,7 @@ table describes:
 
 </table>
 
-Please note that repos in the knative-sandbox GitHub org are a reflection of the WG leads. These leads are free to use their judgement to set the bar for what is required to become an approver and/or owner for knative-sandbox repos they are responsible for.
+Please note that repos in the knative-extensions GitHub org are a reflection of the WG leads. These leads are free to use their judgement to set the bar for what is required to become an approver and/or owner for knative-extensions repos they are responsible for.
 
 ## Member
 
@@ -137,7 +137,7 @@ this is not a requirement.
 
 - Member of the Knative github org. Create a PR adding you to
 [knative.yaml](../main/peribolos/knative.yaml) and/or to
-[knative-sandbox.yaml](../main/peribolos/knative-sandbox.yaml) which after when
+[knative-extensions.yaml](../main/peribolos/knative-extensions.yaml) which after when
 merged will send you an invite that you have to accept to become a member
 of these organizations.
 

hack/update-codegen.sh

@@ -25,7 +25,7 @@ function make_aliases() {
   ( cd mechanics/tools/gen-aliases; go build . )
   # Auto-generate OWNERS_ALIASES from peribolos configs
   ./mechanics/tools/gen-aliases/gen-aliases knative peribolos/knative.yaml peribolos/knative-OWNERS_ALIASES
-  ./mechanics/tools/gen-aliases/gen-aliases knative-sandbox peribolos/knative-sandbox.yaml peribolos/knative-sandbox-OWNERS_ALIASES
+  ./mechanics/tools/gen-aliases/gen-aliases knative-extensions peribolos/knative-extensions.yaml peribolos/knative-extensions-OWNERS_ALIASES
   # Clean up the tool so we don't try to check it in.
   rm ./mechanics/tools/gen-aliases/gen-aliases
 }

mechanics/CREATING-A-SANDBOX-REPO.md

@@ -11,17 +11,17 @@ may need to look there, too. -->
 
 # Background
 
-The [`knative-sandbox`](https://github.com/knative-sandbox) GitHub org exists to
+The [`knative-extensions`](https://github.com/knative-extensions) GitHub org exists to
 hold "non-core" Knative components which are owned and sponsored by a Working
 Group. See the [Knative Repository Guidelines](../REPOSITORY-GUIDELINES.md) for
-more details on the requirements for the `knative-sandbox` org.
+more details on the requirements for the `knative-extensions` org.
 
 ## Criteria
 
 A Working Group Lead (either
 [technical](../ROLES.md#working-group-technical-lead) or
 [execution](../ROLES.md#working-group-execution-lead)) may request a new repo in
-`knative-sandbox` by filing an issue in the
+`knative-extensions` by filing an issue in the
 [knative/community](https://github.com/knative/community/issues/new?template=new-repo.md)
 repo. Once filed, the TOC should handle these promptly, though it should also be
 considered fine to ping members or the group on Slack if it hasn't been acted on
@@ -38,18 +38,18 @@ other WGs to review and approve impacting changes.
   copyright holders under an Apache 2.0 license. See also
   [this section of the repository guidelines](../REPOSITORY-GUIDELINES.md#creation).
 
-- Names between `knative-sandbox` and the main `knative` repo should not
+- Names between `knative-extensions` and the main `knative` repo should not
   overlap. This simplifies promoting repos between the two orgs and setting up
   `knative.dev` import paths for golang.
 
 - Prow automation for tests is encouraged but not required for
-  `knative-sandbox`, but the Google CLA bot and OWNERS files/tide merge should
+  `knative-extensions`, but the Google CLA bot and OWNERS files/tide merge should
   be enforced.
 
 ## Process (to be executed by TOC or Steering member)
 
 1. (Requires Org owner) Create the new repo in
-   https://github.com/knative-sandbox using the "New" button. Set the repo to
+   https://github.com/knative-extensions using the "New" button. Set the repo to
    public and include an "Apache License 2.0" but no `.gitignore` or `README`.
 
 1. (Requires repo write/org owner) Create:
@@ -66,7 +66,7 @@ other WGs to review and approve impacting changes.
    `CODE-OF-CONDUCT.md`, and `README.md`
 
 1. Add entries for the repo to
-   [`../peribolos/knative-sandbox.yaml` in knative/community](https://github.com/knative/community/peribolos/knative-sandbox.yaml).
+   [`../peribolos/knative-extensions.yaml` in knative/community](https://github.com/knative/community/peribolos/knative-extensions.yaml).
    As part of this, grant one or more sponsoring WGs the "write" permission on
    the repo ([sample PR](https://github.com/knative/community/pull/170))
 
@@ -83,7 +83,7 @@ other WGs to review and approve impacting changes.
 
 1. Ensure that Prow is working correctly by creating a PR against the repo. One
    good way to do this is to
-   [add a `test/presubmit-tests.sh`](https://github.com/knative-sandbox/discovery/pull/1)
+   [add a `test/presubmit-tests.sh`](https://github.com/knative-extensions/discovery/pull/1)
    via either the web UI or using a fork.
 
 1. Once at least one PR has been created, you'll be able to select the branch

mechanics/MATURITY-LEVELS.md

@@ -1,7 +1,7 @@
 # Knative Migration-To-Core Process
 
 This document provides a maturity model for projects in the Knative community.
-This includes projects in knative-sandbox (broader community) or as well as
+This includes projects in knative-extensions (broader community) or as well as
 projects in other GitHub organizations which wish to participate in the
 community process. It also defines a process for
 [migrating community projects into the Knative core](#migration-to-core), if
@@ -22,7 +22,7 @@ are not in the core may be equally valuable and production-worthy.
 
 In the initiating phase, a project is starting up, and may have minimal
 additional artifacts around the code itself. The minimum bar for an initiating
-project in the knative-sandbox org is:
+project in the knative-extensions org is:
 
 - [Adopted the CLA bot and OWNERS file / Tide merge process](https://github.com/knative/community/blob/master/mechanics/CREATING-A-SANDBOX-REPO.md#technical-requirements),
   to ensure IP ownership
@@ -42,9 +42,9 @@ This phase is suitable for:
 - Templates
 - etc
 
-Note that Initiating projects do not need to be hosted in knative-sandbox, and
+Note that Initiating projects do not need to be hosted in knative-extensions, and
 can be hosted under either individual accounts or in other orgs. For projects in
-knative-sandbox, review requirements and cadence are at the discretion of the
+knative-extensions, review requirements and cadence are at the discretion of the
 sponsoring WG lead.
 
 ## Usable

mechanics/ROADMAPS.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-All [working groups](../working-groups/WORKING-GROUPS.md) should maintain a current and up-to-date roadmap in a GitHub Project. It's recommended that a _single org-level project_ in the `knative` org should be used; for linking to issues in `knative-sandbox`, cards with the URL of the sandbox issue can be used.
+All [working groups](../working-groups/WORKING-GROUPS.md) should maintain a current and up-to-date roadmap in a GitHub Project. It's recommended that a _single org-level project_ in the `knative` org should be used; for linking to issues in `knative-extensions`, cards with the URL of the sandbox issue can be used.
 
 Working Groups should link to their roadmaps in the Working Group documentation, and should work off the roadmap on a week-to-week or month-to-month basis.
 
@@ -62,4 +62,4 @@ See https://github.com/knative/community/issues/746 for the original discussion
 
 * The TOC does not yet have a recommended process for handling issues which have reached "In Progress" but have some type of time-based delay (e.g. feature is released in "alpha", needs to be progressed to "beta" after one release). One option is to create a new "Ready To Work" issue like `Post-1.3: promote $FEATURE to Beta` and close the original issue, but this is up to Working Group leads to manage.
 
-* TOC reviews will generally focus on management and possibly coordination implications of work items, and will generally rely on the judgement of the working group in terms of which items to complete first.
+* TOC reviews will generally focus on management and possibly coordination implications of work items, and will generally rely on the judgement of the working group in terms of which items to complete first.

mechanics/TOC.md

@@ -33,7 +33,7 @@ Current TOC members and
 with at least 3 months tenure are eligible to stand for election. The approver
 role may be held within either 
 [Knative](https://github.com/knative/community/blob/main/peribolos/knative.yaml) or
-[Knative Sandbox](https://github.com/knative/community/blob/main/peribolos/knative-sandbox.yaml).
+[Knative Sandbox](https://github.com/knative/community/blob/main/peribolos/knative-extensions.yaml).
 Candidates may self-nominate or be nominated by another eligible member. The
 approximate time commitment of a TOC member is around 8 hours per week.
 

peribolos/knative-sandbox-OWNERS_ALIASES

@@ -1,5 +1,5 @@
 # This file is auto-generated from peribolos.
-# Do not modify this file, instead modify peribolos/knative-sandbox.yaml
+# Do not modify this file, instead modify peribolos/knative-extensions.yaml
 
 aliases:
   async-component-approvers:

peribolos/knative-sandbox.yaml

@@ -1,5 +1,5 @@
 orgs:
-  knative-sandbox:
+  knative-extensions:
     name: Knative Sandbox
     description: Sandbox for projects that are part of the broader knative project
     email: [email protected]
@@ -602,7 +602,7 @@ orgs:
             members:
             - travis-minke-sap
       Function Runtime Writers:
-        description: Grants write access to knative-sandbox/func-go
+        description: Grants write access to knative-extensions/func-go
         privacy: closed
         repos:
           func-go: write