docs: Update CZO links from stream to channel in docs and comments.

Updates all the https://chat.zulip.org/#narrow/stream/ links in the docs and comments to use the new /channel/ path. All these links are for documentation/reference purposes only and thus, can be bulk-updated. This commit is a part of the effort to rename stream to channel.
2025-11-03 13:33:24 +00:00 · 2024-06-07 01:18:31 +05:30
parent 16f2c4195b
commit a7772f86a2
34 changed files with 109 additions and 109 deletions
--- a/docs/contributing/code-reviewing.md
+++ b/docs/contributing/code-reviewing.md
@@ -297,7 +297,7 @@ also some additional ways to ask for a code review:
  can also include a link to this guide.

 - If you're not sure who to ask, you can post a message in
-  [#code-review](https://chat.zulip.org/#narrow/stream/91-code-review) on [the Zulip
+  [#code-review](https://chat.zulip.org/#narrow/channel/91-code-review) on [the Zulip
  development community server](https://zulip.com/development-community/) to reach
  out to a wider group of potential reviewers.

--- a/docs/contributing/code-style.md
+++ b/docs/contributing/code-style.md
@@ -45,7 +45,7 @@ to do the same thing. If you think the other code has actively bad
 style, fix it (in a separate commit).

 When in doubt, ask in
-[#development help](https://chat.zulip.org/#narrow/stream/49-development-help).
+[#development help](https://chat.zulip.org/#narrow/channel/49-development-help).

 ### Use the linters

--- a/docs/contributing/design-discussions.md
+++ b/docs/contributing/design-discussions.md
@@ -11,9 +11,9 @@ perspectives, respectfully shared.

 Most design discussions take place in the [#design][design channel] channel in the
 development community. Discussions about mobile app design happen in
-[#mobile-team](https://chat.zulip.org/#narrow/stream/243-mobile-team), and
+[#mobile-team](https://chat.zulip.org/#narrow/channel/243-mobile-team), and
 design of the terminal app is discussed in
-[#zulip-terminal](https://chat.zulip.org/#narrow/stream/206-zulip-terminal).
+[#zulip-terminal](https://chat.zulip.org/#narrow/channel/206-zulip-terminal).

 ## Guidelines for all participants

@@ -168,7 +168,7 @@ Sometimes it helps to move (part of) a thread to a different channel, so that
 it's seen by the appropriate audience.

 - We generally aim to discuss raw user feedback on the product’s design in
-  [#feedback](https://chat.zulip.org/#narrow/stream/137-feedback).
+  [#feedback](https://chat.zulip.org/#narrow/channel/137-feedback).
  The [#design][design channel] should be reserved for design aspects that we’re
  actively (considering) working on. This lets the design team focus on
  discussions that are expected to result in actionable decisions.
@@ -178,13 +178,13 @@ it's seen by the appropriate audience.
  follow the conversation.

 - Discussion of implementation-related decisions should ideally happen in
-  [#frontend](https://chat.zulip.org/#narrow/stream/6-frontend). The line can
+  [#frontend](https://chat.zulip.org/#narrow/channel/6-frontend). The line can
  sometimes blur (and that’s OK), but we should aim to move (parts of) the
  thread if there is an extensive conversation that belongs in the other channel.

- We use [#mobile-team](https://chat.zulip.org/#narrow/stream/243-mobile-team)
+- We use [#mobile-team](https://chat.zulip.org/#narrow/channel/243-mobile-team)
  for discussions of mobile app design, and
-  [#zulip-terminal](https://chat.zulip.org/#narrow/stream/206-zulip-terminal) for
+  [#zulip-terminal](https://chat.zulip.org/#narrow/channel/206-zulip-terminal) for
  terminal app design.

 ## Guidelines for decision makers
@@ -268,4 +268,4 @@ to a decision:
  - If the thread has died down, and the decision makers feel that they have
    enough information to go on. (If they don’t, the thread can be bumped.)

-[design channel]: https://chat.zulip.org/#narrow/stream/101-design
+[design channel]: https://chat.zulip.org/#narrow/channel/101-design
--- a/docs/contributing/reporting-bugs.md
+++ b/docs/contributing/reporting-bugs.md
@@ -90,18 +90,18 @@ Steps and best practices for starting a conversation:
   community](https://zulip.com/development-community/) if you don't already
   have an account.
 2. Pick an **appropriate channel** to report your issue:
-   - [#issues](https://chat.zulip.org/#narrow/stream/9-issues) for issues with
+   - [#issues](https://chat.zulip.org/#narrow/channel/9-issues) for issues with
     the Zulip web app or server. Use this channel if you aren't sure which
     channel is most appropriate.
-   - [#mobile](https://chat.zulip.org/#narrow/stream/48-mobile) for issues with
+   - [#mobile](https://chat.zulip.org/#narrow/channel/48-mobile) for issues with
     the mobile apps.
-   - [#desktop](https://chat.zulip.org/#narrow/stream/16-desktop) for issues
+   - [#desktop](https://chat.zulip.org/#narrow/channel/16-desktop) for issues
     that are specific to the Zulip desktop app, and therefore _do not_
     occur in the web app.
-   - [#zulip-terminal](https://chat.zulip.org/#narrow/stream/206-zulip-terminal)
+   - [#zulip-terminal](https://chat.zulip.org/#narrow/channel/206-zulip-terminal)
     for issues with the terminal app.
   - [#production
-     help](https://chat.zulip.org/#narrow/stream/31-production-help) for issues
+     help](https://chat.zulip.org/#narrow/channel/31-production-help) for issues
     related to self-hosting Zulip. See the [troubleshooting
     guide](../production/troubleshooting.md) for additional details.
 3. **[Start a new topic](https://zulip.com/help/starting-a-new-topic)** for
--- a/docs/contributing/suggesting-features.md
+++ b/docs/contributing/suggesting-features.md
@@ -34,17 +34,17 @@ Steps and best practices for starting a conversation:
   community](https://zulip.com/development-community/) if you don't already
   have an account.
 2. Pick an **appropriate channel** to discuss your idea:
-   - [#feedback](https://chat.zulip.org/#narrow/stream/137-feedback) for suggestions for
+   - [#feedback](https://chat.zulip.org/#narrow/channel/137-feedback) for suggestions for
     the Zulip web app or server. Use this channel if you aren't sure which channel is
     most appropriate.
-   - [#mobile](https://chat.zulip.org/#narrow/stream/48-mobile) for suggestions
+   - [#mobile](https://chat.zulip.org/#narrow/channel/48-mobile) for suggestions
     for the mobile apps.
-   - [#desktop](https://chat.zulip.org/#narrow/stream/16-desktop) for suggestions
+   - [#desktop](https://chat.zulip.org/#narrow/channel/16-desktop) for suggestions
     that are specific to the Zulip desktop app.
-   - [#zulip-terminal](https://chat.zulip.org/#narrow/stream/206-zulip-terminal)
+   - [#zulip-terminal](https://chat.zulip.org/#narrow/channel/206-zulip-terminal)
     for suggestions for the terminal app.
   - [#production
-     help](https://chat.zulip.org/#narrow/stream/31-production-help) for suggestions
+     help](https://chat.zulip.org/#narrow/channel/31-production-help) for suggestions
     related to self-hosting Zulip.
 3. **[Start a new topic](https://zulip.com/help/starting-a-new-topic)** for
   discussing your suggestions, using a brief summary of your idea as the
--- a/docs/development/request-remote.md
+++ b/docs/development/request-remote.md
@@ -43,7 +43,7 @@ zulip/zulip, you are ready to request your Zulip developer instance.
 If you haven't already, create an account on https://chat.zulip.org/.

 Next, join the [development
-help](https://chat.zulip.org/#narrow/stream/49-development-help) channel. Create a
+help](https://chat.zulip.org/#narrow/channel/49-development-help) channel. Create a
 new **channel message** with your GitHub username as the **topic** and request
 your remote dev instance. **Please make sure you have completed steps 1 and 2
 before doing so**. A core developer should reply letting you know they're
--- a/docs/development/setup-advanced.md
+++ b/docs/development/setup-advanced.md
@@ -272,7 +272,7 @@ As with other installation methods, please visit [#provision
 help][provision-help] in the [Zulip development community
 server](https://zulip.com/development-community/) if you need help.

-[provision-help]: https://chat.zulip.org/#narrow/stream/21-provision-help
+[provision-help]: https://chat.zulip.org/#narrow/channel/21-provision-help

 ## Newer versions of supported platforms

@@ -287,7 +287,7 @@ Ubuntu that you're using, we'd love to add support for it. It's
 likely only a few lines of changes to `tools/lib/provision.py` and
 `scripts/lib/setup-apt-repo` if you'd like to do it yourself and
 submit a pull request, or you can ask for help in
-[#development help](https://chat.zulip.org/#narrow/stream/49-development-help)
+[#development help](https://chat.zulip.org/#narrow/channel/49-development-help)
 in [the Zulip development community](https://zulip.com/development-community/),
 and a core team member can help guide you through adding support for the platform.

--- a/docs/development/setup-recommended.md
+++ b/docs/development/setup-recommended.md
@@ -26,7 +26,7 @@ Contents:
 environment,** check [troubleshooting and common
 errors](#troubleshooting-and-common-errors). If that doesn't help,
 please visit [#provision
-help](https://chat.zulip.org/#narrow/stream/21-provision-help) in the
+help](https://chat.zulip.org/#narrow/channel/21-provision-help) in the
 [Zulip development community
 server](https://zulip.com/development-community/) for real-time help or
 [file an issue](https://github.com/zulip/zulip/issues).
@@ -312,7 +312,7 @@ $ vagrant up --provider=docker
 ```

 **Important note**: There is a [known upstream issue on
-macOS](https://chat.zulip.org/#narrow/stream/21-provision-help/topic/provision.20error.20ERR_PNPM_LINKING_FAILED/near/1649241)
+macOS](https://chat.zulip.org/#narrow/channel/21-provision-help/topic/provision.20error.20ERR_PNPM_LINKING_FAILED/near/1649241)
 that can cause provisioning to fail with `ERR_PNPM_LINKING_FAILED` or
 other errors. The temporary fix is to open the Docker desktop app's
 settings panel, and choose `osxfs (legacy)` under "Choose file sharing
@@ -492,7 +492,7 @@ After provisioning, you'll want to
 [(re)start the Zulip development server](/development/setup-recommended.md#step-3-start-the-development-environment).

 If you run into any trouble, [#provision
-help](https://chat.zulip.org/#narrow/stream/21-provision-help) in the
+help](https://chat.zulip.org/#narrow/channel/21-provision-help) in the
 [Zulip development community
 server](https://zulip.com/development-community/) is a great place to ask for
 help.
@@ -709,7 +709,7 @@ equivalently `vagrant provision` from outside).
 If these solutions aren't working for you or you encounter an issue not
 documented below, there are a few ways to get further help:

- Ask in [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help)
+- Ask in [#provision help](https://chat.zulip.org/#narrow/channel/21-provision-help)
  in the [Zulip development community server](https://zulip.com/development-community/).
 - [File an issue](https://github.com/zulip/zulip/issues).

--- a/docs/development/setup/vagrant-up.md
+++ b/docs/development/setup/vagrant-up.md
@@ -20,6 +20,6 @@ without provisioning after the first time). Other common issues are
 documented in the
 [Troubleshooting and common errors](/development/setup-recommended.md#troubleshooting-and-common-errors)
 section. If that doesn't help, please visit
-[#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help)
+[#provision help](https://chat.zulip.org/#narrow/channel/21-provision-help)
 in the [Zulip development community server](https://zulip.com/development-community/) for
 real-time help.
--- a/docs/development/setup/vagrant-update.md
+++ b/docs/development/setup/vagrant-update.md
@@ -12,7 +12,7 @@ After provisioning, you'll want to
 [(re)start the Zulip development server](/development/setup-recommended.md#step-3-start-the-development-environment).

 If you run into any trouble, [#provision
-help](https://chat.zulip.org/#narrow/stream/21-provision-help) in the
+help](https://chat.zulip.org/#narrow/channel/21-provision-help) in the
 [Zulip development community
 server](https://zulip.com/development-community/) is a great place to ask for
 help.
--- a/docs/documentation/helpcenter.md
+++ b/docs/documentation/helpcenter.md
@@ -80,7 +80,7 @@ be merged into the existing help center documentation where appropriate.

 If you are unsure about how and where to document the feature, you
 can always ask in
-[#documentation](https://chat.zulip.org/#narrow/stream/19-documentation)
+[#documentation](https://chat.zulip.org/#narrow/channel/19-documentation)
 on the [Zulip community server](https://zulip.com/development-community/).

 ### Updating an existing article
--- a/docs/outreach/apply.md
+++ b/docs/outreach/apply.md
@@ -67,14 +67,14 @@ We recommend taking the following steps before diving into the issue tracker:
 - Join the [Zulip development
  community](https://zulip.com/development-community/), and introduce yourself
  in the channel for the program you are participating in
-  ([#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
-  [#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)). Before you
+  ([#GSoC](https://chat.zulip.org/#narrow/channel/14-GSoC) or
+  [#Outreachy](https://chat.zulip.org/#narrow/channel/391-Outreachy)). Before you
  jump in, be sure to review the [Zulip community
  norms](https://zulip.com/development-community/).

 - Follow our instructions to [install the development
  environment](../development/overview.md), getting help in [#provision
-  help](https://chat.zulip.org/#narrow/stream/21-provision-help) if needed.
+  help](https://chat.zulip.org/#narrow/channel/21-provision-help) if needed.

 - Familiarize yourself with [using the development
  environment](../development/using.md).
@@ -87,7 +87,7 @@ As you are getting started on your first pull request:

 - Read the [Zulip guide to Git](../git/overview.md). It's especially important
  to master using `git rebase`, so that you can restructure your commits. You can
-  get help in [#git help](https://chat.zulip.org/#narrow/stream/44-git-help) if
+  get help in [#git help](https://chat.zulip.org/#narrow/channel/44-git-help) if
  you get stuck.

 - To make it easier to structure your PRs well, we recommend installing a
@@ -182,8 +182,8 @@ give you feedback and help you improve your proposal.

 - Please post a link to your draft in the Zulip development community
  channel dedicated to your program (e.g.,
-  [#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
-  [#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)). Use
+  [#GSoC](https://chat.zulip.org/#narrow/channel/14-GSoC) or
+  [#Outreachy](https://chat.zulip.org/#narrow/channel/391-Outreachy)). Use
  `Your name - project proposal` as the topic.

 - We recommend linking to a draft in an app that works in the browser and allows
--- a/docs/outreach/experience.md
+++ b/docs/outreach/experience.md
@@ -103,8 +103,8 @@ to ask your questions effectively.

 A check-in is a regular update that you post in the Zulip development community.
 You can find many examples in the
-[#checkins](https://chat.zulip.org/#narrow/stream/65-checkins) and
-[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) channels.
+[#checkins](https://chat.zulip.org/#narrow/channel/65-checkins) and
+[#GSoC](https://chat.zulip.org/#narrow/channel/14-GSoC) channels.

 - **Frequency**: _Regular check-ins are a required for all program
  participants._ If you are working 20+ hours per week, post a check-in at least
@@ -113,8 +113,8 @@ You can find many examples in the

 - **Where to post**: Unless your mentor or program administrator requests
  otherwise, post your check-ins in the channel for your program
-  (e.g., [#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
-  [#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)), using your
+  (e.g., [#GSoC](https://chat.zulip.org/#narrow/channel/14-GSoC) or
+  [#Outreachy](https://chat.zulip.org/#narrow/channel/391-Outreachy)), using your
  name as the topic.

 - **What to include** in each check-in:
--- a/docs/outreach/gsoc.md
+++ b/docs/outreach/gsoc.md
@@ -129,7 +129,7 @@ Django, TypeScript/JavaScript, and CSS.

  Experts: Zixuan James Li, Evy Kassirer, Anders Kaseorg

-[typescript-migration]: https://chat.zulip.org/#narrow/stream/6-frontend/topic/typescript.20migration
+[typescript-migration]: https://chat.zulip.org/#narrow/channel/6-frontend/topic/typescript.20migration

 - Migrate server's Python codebase from the legacy
  `@has_request_variables` decorator to the new `@typed_endpoint`
@@ -415,9 +415,9 @@ Experts: Greg Price, Chris Bobbe
  experience with Android or iOS may also be helpful but is not
  necessary.

-[flutter-why]: https://chat.zulip.org/#narrow/stream/2-general/topic/Flutter/near/1582367
-[flutter-beta]: https://chat.zulip.org/#narrow/stream/2-general/topic/Flutter/near/1708728
+[flutter-why]: https://chat.zulip.org/#narrow/channel/2-general/topic/Flutter/near/1582367
+[flutter-beta]: https://chat.zulip.org/#narrow/channel/2-general/topic/Flutter/near/1708728
 [flutter-board]: https://github.com/orgs/zulip/projects/5/views/4
 [flutter-milestone-launch]: https://github.com/zulip/zulip-flutter/milestone/3
-[flutter-upstream-summary]: https://chat.zulip.org/#narrow/stream/2-general/topic/Flutter/near/1524757
+[flutter-upstream-summary]: https://chat.zulip.org/#narrow/channel/2-general/topic/Flutter/near/1524757
 [flutter-upstream-autocomplete]: https://github.com/flutter/flutter/pull/129802
--- a/docs/production/security-model.md
+++ b/docs/production/security-model.md
@@ -3,7 +3,7 @@
 This section attempts to document the Zulip security model. It likely
 does not cover every issue; if there are details you're curious about,
 please feel free to ask questions in [#production
-help](https://chat.zulip.org/#narrow/stream/31-production-help) on the
+help](https://chat.zulip.org/#narrow/channel/31-production-help) on the
 [Zulip community server](https://zulip.com/development-community/) (or if you
 think you've found a security bug, please report it to
 security@zulip.com so we can do a responsible security
--- a/docs/production/troubleshooting.md
+++ b/docs/production/troubleshooting.md
@@ -20,7 +20,7 @@ To report a problem or ask a question, please start a new topic in the
  which versions you are upgrading.

 [chat-zulip-org]: https://zulip.com/development-community/
-[production-help]: https://chat.zulip.org/#narrow/stream/31-production-help
+[production-help]: https://chat.zulip.org/#narrow/channel/31-production-help
 [code-block]: https://zulip.com/help/code-blocks

 Contact [sales@zulip.com](mailto:sales@zulip.com) if you'd like to
--- a/docs/production/upgrade.md
+++ b/docs/production/upgrade.md
@@ -187,7 +187,7 @@ Useful logs are available in a few places:

 If you need help and don't have a support contract, you can visit
 [#production
-help](https://chat.zulip.org/#narrow/stream/31-production-help) in the
+help](https://chat.zulip.org/#narrow/channel/31-production-help) in the
 [Zulip development community
 server](https://zulip.com/development-community/) for best-effort help.
 Please include the relevant error output from the above logs in a
--- a/docs/subsystems/release-checklist.md
+++ b/docs/subsystems/release-checklist.md
@@ -84,7 +84,7 @@ preparing a new release.
 - Announce the release, pointing to the blog post, via:
  - Email to [zulip-announce](https://groups.google.com/g/zulip-announce)
  - Email to [zulip-blog-announce](https://groups.google.com/a/zulip.com/g/zulip-blog-announce)
-  - Message in [#announce](https://chat.zulip.org/#narrow/stream/1-announce)
+  - Message in [#announce](https://chat.zulip.org/#narrow/channel/1-announce)
  - Tweet from [@zulip](https://twitter.com/zulip).
  - Toot from [fosstodon.org/@zulip](https://fosstodon.org/@zulip)

--- a/docs/translating/french.md
+++ b/docs/translating/french.md
@@ -7,8 +7,8 @@ in the main "#translation" stream, there is a dedicated stream
 [#translation/fr][] for discussing the French translations.
 Please join there too and say hello.

-[#translation > French translations]: https://chat.zulip.org/#narrow/stream/58-translation/topic/French.20translations
-[#translation/fr]: https://chat.zulip.org/#narrow/stream/371-translation.2Ffr
+[#translation > French translations]: https://chat.zulip.org/#narrow/channel/58-translation/topic/French.20translations
+[#translation/fr]: https://chat.zulip.org/#narrow/channel/371-translation.2Ffr

 ## Rules

--- a/docs/translating/hindi.md
+++ b/docs/translating/hindi.md
@@ -1,7 +1,7 @@
 # Hindi translation style guide (हिन्दी अनुवाद शैली मार्गदर्शक)

 - Use _आप_ as the second-person pronoun. Don't use तुम or तू.
-  (See [chat thread](https://chat.zulip.org/#narrow/stream/58-translation/topic/Hindi.20Translation/near/1762384).)
+  (See [chat thread](https://chat.zulip.org/#narrow/channel/58-translation/topic/Hindi.20Translation/near/1762384).)

 - Imperative, active, and continuous verbs, e.g. _manage streams_ -
  _चैनल प्रबंधित करें_, not _चैनल प्रबंधन_.
--- a/docs/translating/translating.md
+++ b/docs/translating/translating.md
@@ -86,7 +86,7 @@ Some useful tips for your translating journey:
  the string with `Ctrl+F` in your browser.

 - When in doubt, ask for context in
-  [#translation](https://chat.zulip.org/#narrow/stream/58-translation) in
+  [#translation](https://chat.zulip.org/#narrow/channel/58-translation) in
  the [Zulip development community server](https://zulip.com/development-community/).

 - If there are multiple possible translations for a term, search for it in
@@ -225,4 +225,4 @@ suite](../testing/testing.md#other-test-suites)
 (`./tools/check-capitalization`; `tools/lib/capitalization.py` has
 some exclude lists, e.g. `IGNORED_PHRASES`).

-[translation-channel]: https://chat.zulip.org/#narrow/stream/58-translation
+[translation-channel]: https://chat.zulip.org/#narrow/channel/58-translation