wx
/
zulip
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Sayam Samal 2024-06-07 01:18:31 +05:30 committed by Tim Abbott
parent 16f2c4195b
commit a7772f86a2
34 changed files with 109 additions and 109 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CONTRIBUTING.md
View File

@ -81,7 +81,7 @@ to help.
paying special attention to the
[community norms](https://zulip.com/development-community/#community-norms).
If you'd like, introduce yourself in
[#new members](https://chat.zulip.org/#narrow/stream/95-new-members), using
[#new members](https://chat.zulip.org/#narrow/channel/95-new-members), using
your name as the topic. Bonus: tell us about your first impressions of
Zulip, and anything that felt confusing/broken or interesting/helpful as you
started using the product.
@ -95,7 +95,7 @@ to help.
- [Install the development environment](https://zulip.readthedocs.io/en/latest/development/overview.html),
getting help in
[#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help)
[#provision help](https://chat.zulip.org/#narrow/channel/21-provision-help)
if you run into any troubles.
- Familiarize yourself with [using the development environment](https://zulip.readthedocs.io/en/latest/development/using.html).
- Go through the [new application feature
@ -117,7 +117,7 @@ to help.
Git](https://zulip.readthedocs.io/en/latest/git/index.html) if you
are unfamiliar with Git or Zulip's rebase-based Git workflow,
getting help in [#git
help](https://chat.zulip.org/#narrow/stream/44-git-help) if you run
help](https://chat.zulip.org/#narrow/channel/44-git-help) if you run
into any troubles. Even Git experts should read the [Zulip-specific
Git tools
page](https://zulip.readthedocs.io/en/latest/git/zulip-tools.html).
@ -235,7 +235,7 @@ GitHub issue or pull request.
To get early feedback on any UI changes, we encourage you to post screenshots of
your work in the [#design
stream](https://chat.zulip.org/#narrow/stream/101-design) in the [Zulip
stream](https://chat.zulip.org/#narrow/channel/101-design) in the [Zulip
development community](https://zulip.com/development-community/)
For more advice, see [What makes a great Zulip
@ -377,7 +377,7 @@ to:
A link to your organization's website?
You can contact us in the [#feedback stream of the Zulip development
community](https://chat.zulip.org/#narrow/stream/137-feedback) or
community](https://chat.zulip.org/#narrow/channel/137-feedback) or
by emailing [support@zulip.com](mailto:support@zulip.com).
## Outreach programs

2
api_docs/client-libraries.md
View File

@ -37,7 +37,7 @@ topic][integrations-thread] in
or submit a pull request [updating this
page](https://zulip.readthedocs.io/en/latest/documentation/api.html).
[integrations-thread]: https://chat.zulip.org/#narrow/stream/127-integrations/topic/API.20client.20libraries/
[integrations-thread]: https://chat.zulip.org/#narrow/channel/127-integrations/topic/API.20client.20libraries/
### Outdated

2
api_docs/incoming-webhooks-walkthrough.md
View File

@ -501,7 +501,7 @@ pushing the code to your fork and submitting a pull request to zulip/zulip:
clear commit message.
If you would like feedback on your integration as you go, feel free to post a
message on the [public Zulip instance](https://chat.zulip.org/#narrow/stream/integrations).
message on the [public Zulip instance](https://chat.zulip.org/#narrow/channel/integrations).
You can also create a [draft pull request](
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) while you
are still working on your integration. See the

2
docs/contributing/code-reviewing.md
View File

@ -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.

2
docs/contributing/code-style.md
View File

@ -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

14
docs/contributing/design-discussions.md
View File

@ -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

10
docs/contributing/reporting-bugs.md
View File

@ -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

10
docs/contributing/suggesting-features.md
View File

@ -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

2
docs/development/request-remote.md
View File

@ -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

4
docs/development/setup-advanced.md
View File

@ -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.

8
docs/development/setup-recommended.md
View File

@ -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).

2
docs/development/setup/vagrant-up.md
View File

@ -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.

2
docs/development/setup/vagrant-update.md
View File

@ -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.

2
docs/documentation/helpcenter.md
View File

@ -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

12
docs/outreach/apply.md
View File

@ -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

8
docs/outreach/experience.md
View File

@ -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:

8
docs/outreach/gsoc.md
View File

@ -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

2
docs/production/security-model.md
View File

@ -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

2
docs/production/troubleshooting.md
View File

@ -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

2
docs/production/upgrade.md
View File

@ -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

2
docs/subsystems/release-checklist.md
View File

@ -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)

4
docs/translating/french.md
View File

@ -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

2
docs/translating/hindi.md
View File

@ -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 _चैनल प्रबंधन_.

4
docs/translating/translating.md
View File

@ -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

2
scripts/setup/reindex-textual-data
View File

@ -129,7 +129,7 @@ There is no generalized tool to fix these duplicate rows, but in most cases
the database can be repaired with some manual work. We are using
this chat.zulip.org for support around such repairs:
https://chat.zulip.org/#narrow/stream/31-production-help/topic/database.20corruption
https://chat.zulip.org/#narrow/channel/31-production-help/topic/database.20corruption
This tool has regenerated all database indexes that do not have duplicate rows.
Once you have manually repaired duplicate rows, you can rerun this command

2
templates/corporate/case-studies/tum-case-study.md
View File

@ -84,5 +84,5 @@ and [research](/for/research/)!
[tum-ranking]: https://www.in.tum.de/en/the-department/profile-of-the-department/facts-figures/facts-and-figures-2020/
[czo-patch-thread]: https://chat.zulip.org/#narrow/stream/3-backend/topic/Tornado.20performance/near/1111686
[czo-patch-thread]: https://chat.zulip.org/#narrow/channel/3-backend/topic/Tornado.20performance/near/1111686
[zulip-4-blog]: https://blog.zulip.com/2021/05/13/zulip-4-0-released/

78
templates/corporate/development-community.md
View File

@ -38,7 +38,7 @@ feedback.
## Getting started
- Send test messages to [#test
here](https://chat.zulip.org/#narrow/stream/7-test-here) or as a PM
here](https://chat.zulip.org/#narrow/channel/7-test-here) or as a PM
to yourself to avoid disturbing others.
- Start a [new topic](/help/introduction-to-topics) unless you’re replying
to an existing conversation. If you see a new user talking about
@ -46,7 +46,7 @@ feedback.
appropriate new topic](/help/move-content-to-another-topic).
- If you’re not sure where to start, introduce yourself and your
interests in [#new
members](https://chat.zulip.org/#narrow/stream/95-new-members),
members](https://chat.zulip.org/#narrow/channel/95-new-members),
using your name as the topic to create a dedicated space.
- Follow the community [code of
conduct](https://zulip.readthedocs.io/en/latest/code-of-conduct.html).
@ -90,121 +90,121 @@ topic to a different channel](/help/move-content-to-another-channel).
## Channels for everyone
- [#feedback](https://chat.zulip.org/#narrow/stream/137-feedback) is
- [#feedback](https://chat.zulip.org/#narrow/channel/137-feedback) is
for posting feedback on Zulip, including feature requests, suggestions for
improvements to the UI or existing features, or anything else! We also
appreciate hearing about how Zulip is used in your organization.
- [#integrations](https://chat.zulip.org/#narrow/stream/127-integrations)
- [#integrations](https://chat.zulip.org/#narrow/channel/127-integrations)
is for bug reports or questions about integrations.
- [#issues](https://chat.zulip.org/#narrow/stream/9-issues) is for reporting
- [#issues](https://chat.zulip.org/#narrow/channel/9-issues) is for reporting
bugs (or possible bugs) in the Zulip web app or server implementation.
- [#mobile](https://chat.zulip.org/#narrow/stream/48-mobile),
[#desktop](https://chat.zulip.org/#narrow/stream/16-desktop), and
[#zulip-terminal](https://chat.zulip.org/#narrow/stream/206-zulip-terminal)
- [#mobile](https://chat.zulip.org/#narrow/channel/48-mobile),
[#desktop](https://chat.zulip.org/#narrow/channel/16-desktop), and
[#zulip-terminal](https://chat.zulip.org/#narrow/channel/206-zulip-terminal)
are the best places to post bug reports or questions about Zulip's apps. Note
that [#desktop](https://chat.zulip.org/#narrow/stream/16-desktop) should only
that [#desktop](https://chat.zulip.org/#narrow/channel/16-desktop) should only
be used for issues specific to the desktop app, which shares most of its UI
and implementation with the web app.
- Everyone is welcome to introduce themselves in [#new
members](https://chat.zulip.org/#narrow/stream/95-new-members). Posting
members](https://chat.zulip.org/#narrow/channel/95-new-members). Posting
here with your name as the topic is a great option if you’re
uncertain where to start a conversation.
- [#test here](https://chat.zulip.org/#narrow/stream/7-test-here) is
- [#test here](https://chat.zulip.org/#narrow/channel/7-test-here) is
for sending test messages without inconveniencing other users :). We
recommend muting this channel when not using it.
## Channels for Zulip users and administrators
- [#user questions](https://chat.zulip.org/#narrow/stream/138-user-questions) is
- [#user questions](https://chat.zulip.org/#narrow/channel/138-user-questions) is
for questions about how to configure your Zulip organization, and accomplish
your goals with Zulip. You can also refer to the [Zulip help center](/help)
for detailed documentation.
- [#production help](https://chat.zulip.org/#narrow/stream/31-production-help) is
- [#production help](https://chat.zulip.org/#narrow/channel/31-production-help) is
for all questions related to [self-hosting
Zulip](/self-hosting/).
- [#zulip
cloud](https://chat.zulip.org/#narrow/stream/387-zulip-cloud) is for
cloud](https://chat.zulip.org/#narrow/channel/387-zulip-cloud) is for
all conversations about the [Zulip Cloud](https://zulip.com/plans/)
service.
## Channels for code contributors
- [#development
help](https://chat.zulip.org/#narrow/stream/49-development-help) is
help](https://chat.zulip.org/#narrow/channel/49-development-help) is
for asking for help with any Zulip server/web app development work
(use the app channels #mobile, #desktop, or #zulip-terminal for help
working on one of the apps).
- [#provision
help](https://chat.zulip.org/#narrow/stream/21-provision-help) is
help](https://chat.zulip.org/#narrow/channel/21-provision-help) is
for help specifically on setting up the server/web app development
environment. [#tools](https://chat.zulip.org/#narrow/stream/18-tools)
environment. [#tools](https://chat.zulip.org/#narrow/channel/18-tools)
is other conversations about the server/web app developer tooling.
- [#git help](https://chat.zulip.org/#narrow/stream/44-git-help) is
- [#git help](https://chat.zulip.org/#narrow/channel/44-git-help) is
for help with using Git.
- [#code review](https://chat.zulip.org/#narrow/stream/91-code-review)
- [#code review](https://chat.zulip.org/#narrow/channel/91-code-review)
is for getting feedback on your work. We encourage all developers to
comment on work posted here, even if you’re new to the Zulip
project; reviewing other PRs is a great way to develop experience,
and even just manually testing a proposed new feature and posting
feedback is super helpful. Note that GitHub is our primary system
for managing code reviews.
- [#backend](https://chat.zulip.org/#narrow/stream/3-backend),
[#frontend](https://chat.zulip.org/#narrow/stream/6-frontend),
[#documentation](https://chat.zulip.org/#narrow/stream/19-documentation),
- [#backend](https://chat.zulip.org/#narrow/channel/3-backend),
[#frontend](https://chat.zulip.org/#narrow/channel/6-frontend),
[#documentation](https://chat.zulip.org/#narrow/channel/19-documentation),
and app-specific channels
([#mobile](https://chat.zulip.org/#narrow/stream/48-mobile), etc.)
([#mobile](https://chat.zulip.org/#narrow/channel/48-mobile), etc.)
are the right place for general conversations about work in those
areas (including design discussions, questions, updates on a
project, or anything else).
- [#automated
testing](https://chat.zulip.org/#narrow/stream/43-automated-testing)
testing](https://chat.zulip.org/#narrow/channel/43-automated-testing)
is primarily used for automated notifications about [CI
failures](https://zulip.readthedocs.io/en/latest/testing/continuous-integration.html),
but is also a good place to discuss projects to improve Zulip’s
automated testing infrastructure.
- [#api design](https://chat.zulip.org/#narrow/stream/378-api-design)
- [#api design](https://chat.zulip.org/#narrow/channel/378-api-design)
is a low-traffic channel for discussing and coordinating changes to
the [Zulip API](https://zulip.com/api/rest), with all stakeholders
present.
## Channels for translators
- [#translation](https://chat.zulip.org/#narrow/stream/58-translation)
- [#translation](https://chat.zulip.org/#narrow/channel/58-translation)
is for discussing [Zulip’s
translations](https://zulip.readthedocs.io/en/latest/translating/translating.html).
- Some languages have channels named like
[#translation/fr](https://chat.zulip.org/#narrow/stream/371-translation.2Ffr)
[#translation/fr](https://chat.zulip.org/#narrow/channel/371-translation.2Ffr)
and
[#translation/zh_tw](https://chat.zulip.org/#narrow/stream/377-translation.2Fzh_tw)
[#translation/zh_tw](https://chat.zulip.org/#narrow/channel/377-translation.2Fzh_tw)
to coordinate translation work for that language.
## Channels for anyone spending time in the community
- [#announce](https://chat.zulip.org/#narrow/stream/1-announce) is our
- [#announce](https://chat.zulip.org/#narrow/channel/1-announce) is our
low-traffic channel for project announcements (releases, etc.).
- [#checkins](https://chat.zulip.org/#narrow/stream/65-checkins) is
- [#checkins](https://chat.zulip.org/#narrow/channel/65-checkins) is
for progress updates on what you’re working on and its status;
usually folks post with their name as the topic. Everyone is welcome
to participate!
- [#design](https://chat.zulip.org/#narrow/stream/101-design) is where
- [#design](https://chat.zulip.org/#narrow/channel/101-design) is where
we discuss UI and feature design and collect feedback on potential
design changes. We love feedback, so don’t hesitate to speak up!
Note that
[#feedback](https://chat.zulip.org/#narrow/stream/137-feedback) is
[#feedback](https://chat.zulip.org/#narrow/channel/137-feedback) is
usually the best place for end users to start a topic about a
proposed design change;
[#design](https://chat.zulip.org/#narrow/stream/101-design) is
[#design](https://chat.zulip.org/#narrow/channel/101-design) is
primarily intended for discussing changes the community is actively
working on.
- [#discussions](https://chat.zulip.org/#narrow/stream/277-discussions)
- [#discussions](https://chat.zulip.org/#narrow/channel/277-discussions)
is where we do fun community conversations like “Ask Me Anything”
Q&A sessions with project members.
- [#documentation](https://chat.zulip.org/#narrow/stream/19-documentation)
- [#documentation](https://chat.zulip.org/#narrow/channel/19-documentation)
is where we discuss improving Zulip’s user, sysadmin, API, and
developer documentation.
- [#general](https://chat.zulip.org/#narrow/stream/2-general) is for
- [#general](https://chat.zulip.org/#narrow/channel/2-general) is for
all topics of general interest.
- [#learning](https://chat.zulip.org/#narrow/stream/92-learning) is
- [#learning](https://chat.zulip.org/#narrow/channel/92-learning) is
for posting great learning resources one comes across.
- [#off topic](https://chat.zulip.org/#narrow/stream/97-off-topic) is
- [#off topic](https://chat.zulip.org/#narrow/channel/97-off-topic) is
is for occasional conversations not related to Zulip, usually things
of general interest to open-source communities.
@ -253,7 +253,7 @@ to issue 1234 in the main Zulip project repositories:
We [continuously test out new features or ideas][release-lifecycle] on
chat.zulip.org before rolling them out to Zulip Cloud or including
them in a Zulip Server release (or deciding not to!). Please report in
[#issues](https://chat.zulip.org/#narrow/stream/9-issues) anything you
[#issues](https://chat.zulip.org/#narrow/channel/9-issues) anything you
notice that seems broken! It’s likely you’ve found a bug in an upcoming
feature.

4
templates/corporate/try-zulip-part1.md
View File

@ -13,9 +13,9 @@ You can:
[**channel**](/help/introduction-to-channels) on the left to open a
list of recent conversation topics. For example, you can explore discussions
of changes to the design of the Zulip app in
[#design](https://chat.zulip.org/#narrow/stream/101-design), or see ongoing
[#design](https://chat.zulip.org/#narrow/channel/101-design), or see ongoing
issue investigations in
[#issues](https://chat.zulip.org/#narrow/stream/9-issues).
[#issues](https://chat.zulip.org/#narrow/channel/9-issues).
- **Click on each topic** in a channel to view conversations one at a time.
Notice how Zulip makes it easy to have many conversations at once, without
them getting in each other’s way.

2
templates/corporate/try-zulip-part2.md
View File

@ -4,7 +4,7 @@ development community. You’ll be able to send messages, experience the
convenience of going through your unread messages, and much more. Please be
sure to follow [community guidelines](/development-community/), and send any
test messages to the [#test
here](https://chat.zulip.org/#narrow/stream/7-test-here) channel.
here](https://chat.zulip.org/#narrow/channel/7-test-here) channel.
You can also view <a href="/plans/">plans and pricing</a>, or create a <a
href="/new/">new organization</a>.

2
tools/setup/emoji/build_emoji
View File

@ -402,7 +402,7 @@ def generate_map_files(cache_path: str, emoji_catalog: Dict[str, List[str]]) ->
# switch to that which would allow us to drop the existing file. But
# we'll probably instead do #18121 which will make this file obsolete.
# So this is a temporary solution. CZO discussion:
# https://chat.zulip.org/#narrow/stream/378-api-design/topic/currently.20supported.20emoji/near/1394598
# https://chat.zulip.org/#narrow/channel/378-api-design/topic/currently.20supported.20emoji/near/1394598
EMOJI_API_FILE_PATH = os.path.join(cache_path, "emoji_api.json")
with open(EMOJI_API_FILE_PATH, "wb") as emoji_api_file:
emoji_api_file.write(

4
web/e2e-tests/admin.test.ts
View File

@ -165,11 +165,11 @@ async function test_organization_permissions(page: Page): Promise<void> {
await page.click("li[data-section='organization-permissions']");
// Test temporarily disabled 2024-02-07 due to nondeterminsitic failures.
// See https://chat.zulip.org/#narrow/stream/43-automated-testing/topic/main.20failing/near/1733342
// See https://chat.zulip.org/#narrow/channel/43-automated-testing/topic/main.20failing/near/1733342
console.log("Skipping", test_changing_create_streams_and_invite_to_stream_policies);
// Test temporarily disabled 2024-02-25 due to nondeterminsitic failures.
// See https://chat.zulip.org/#narrow/stream/43-automated-testing/topic/main.20failing/near/1743361
// See https://chat.zulip.org/#narrow/channel/43-automated-testing/topic/main.20failing/near/1743361
console.log("Skipping", test_set_new_user_threshold_to_three_days);
console.log("Skipping", test_set_new_user_threshold_to_N_days);
}

2
web/shared/src/poll_data.js.flow
View File

@ -5,7 +5,7 @@
*
* In reality these are more specific than this type. But they're currently
* completely undocumented in the API:
* https://chat.zulip.org/#narrow/stream/412-api-documentation/topic/.60.2Esubmessages.60.20on.20message.20objects/near/1358493
* https://chat.zulip.org/#narrow/channel/412-api-documentation/topic/.60.2Esubmessages.60.20on.20message.20objects/near/1358493
* so we don't attempt to go any further here.
*/
type PollEvent = {...};

2
web/src/hashchange.js
View File

@ -140,7 +140,7 @@ function show_home_view() {
// empty hash (like a stream narrow) will
// introduce a bug that user will not be able to
// go back in browser history. See
// https://chat.zulip.org/#narrow/stream/9-issues/topic/Browser.20back.20button.20on.20RT
// https://chat.zulip.org/#narrow/channel/9-issues/topic/Browser.20back.20button.20on.20RT
// for detailed description of the issue.
window.location.hash = user_settings.web_home_view;
}

2
web/tests/message_list_view.test.js
View File

@ -333,7 +333,7 @@ test("muted_message_vars", () => {
(function test_hidden_message_variables() {
// We want to have no search results, which apparently works like this.
// See https://chat.zulip.org/#narrow/stream/6-frontend/topic/set_find_results.20with.20no.20results/near/1414799
// See https://chat.zulip.org/#narrow/channel/6-frontend/topic/set_find_results.20with.20no.20results/near/1414799
const empty_list_stub = $.create("empty-stub", {children: []});
$("<message-stub-1>").set_find_results(".user-mention:not(.silent)", empty_list_stub);
$("<message-stub2>").set_find_results(".user-mention:not(.silent)", empty_list_stub);