diff --git a/docs/contributing/code-style.md b/docs/contributing/code-style.md index f40a74b739..36868d4ed0 100644 --- a/docs/contributing/code-style.md +++ b/docs/contributing/code-style.md @@ -28,7 +28,8 @@ Look at the surrounding code, or a similar part of the project, and try 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 [chat.zulip.org](https://chat.zulip.org). +When in doubt, ask in +[#development help](https://chat.zulip.org/#narrow/stream/49-development-help). ## Lint tools diff --git a/docs/contributing/gsoc-ideas.md b/docs/contributing/gsoc-ideas.md index fd028ea1e1..67a5d7c150 100644 --- a/docs/contributing/gsoc-ideas.md +++ b/docs/contributing/gsoc-ideas.md @@ -80,8 +80,8 @@ tasks that are great for first-time contributors. Use [our first-time Zulip developer guide](../overview/contributing.html#your-first-codebase-contribution) to get your Zulip development environment set up and to find your first issue. If you have any trouble, please speak up in -[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) on -[the Zulip development community server](https://zulip.com/developer-community/) +[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) in +[the Zulip development community server][development-community] (use your name as the topic). ## Application tips, and how to be a strong candidate @@ -126,8 +126,8 @@ application deadline. We are more interested in candidates if we see them submitting good contributions to Zulip projects, helping other applicants on GitHub -and on -[chat.zulip.org](https://zulip.com/developer-community/), +and in +[the Zulip development community][development-community], learning from our suggestions, [trying to solve their own obstacles and then asking well-formed questions](https://blogs.akamai.com/2013/10/you-must-try-and-then-you-must-ask.html), @@ -170,14 +170,16 @@ projects. We usually decide who will mentor which projects based in part on who is a good fit for the needs of each student as well as technical expertise as well as who has available time during the summer. You can reach us via -[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) on [the Zulip -development community server](https://zulip.com/developer-community/), +[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) in +[the Zulip development community server][development-community], (compose a new stream message with your name as the topic). Zulip operates under group mentorship. That means you should -generally post in public streams on chat.zulip.org, not send private +generally post in public streams in +[the Zulip development community][development-community], not send private messages, for assistance. Our preferred approach is to just post in -an appropriate public stream on chat.zulip.org and someone will help +an appropriate public stream in +[the Zulip development community][development-community] and someone will help you. We list the Zulip contributors who are experts for various projects by name below; they will likely be able to provide you with the best feedback on your proposal (feel free to @-mention them in @@ -196,11 +198,12 @@ few contributions! Everyone makes mistakes getting started. Just make sure you don't make the same mistakes next time). Once you have several PRs merged (or at least one significant PR -merged), you can start discussing with the Zulip development community +merged), you can start discussing with +[the Zulip development community][development-community] the project you'd like to do, and developing a specific project plan. -We recommend discussing what you're thinking in public streams on -chat.zulip.org, so it's easy to get quick feedback from whoever is -online. +We recommend discussing what you're thinking in public streams in +[the Zulip development community][development-community], +so it's easy to get quick feedback from whoever is online. ## Project ideas @@ -588,7 +591,9 @@ Where should you publish your draft? We prefer Dropbox Paper or Google Docs, since those platforms allow people to look at the text without having to log in or download a particular app, and you can update the draft as you improve your idea. In either case, you should -post the draft for feedback in chat.zulip.org. +post the draft for feedback in [the Zulip development community][development-community]. + +[development-community]: https://zulip.com/developer-community/ Rough is fine! The ideal first draft to get feedback from the community on should include primarily (1) links to your contributions diff --git a/docs/contributing/summer-with-zulip.md b/docs/contributing/summer-with-zulip.md index 492378d524..59343d585c 100644 --- a/docs/contributing/summer-with-zulip.md +++ b/docs/contributing/summer-with-zulip.md @@ -34,8 +34,10 @@ materials](https://developers.google.com/open-source/gsoc/resources/manual). - Mentors and students should stay in close contact, both with each other and the rest of the Zulip community. We recommend the following: - - Daily checkins on #checkins on chat.zulip.org; ideally at some time of day - you can both be online, but when not possible, async is better than nothing! + - Daily checkins on #checkins in + [the Zulip development community](https://zulip.com/developer-community/); ideally + at some time of day you can both be online, but when not + possible, async is better than nothing! - We prefer checkins in public streams, since it makes easier for other contributors to keep track of what everyone else is @@ -54,9 +56,9 @@ materials](https://developers.google.com/open-source/gsoc/resources/manual). need help learning, and time-saving tricks. - If you need feedback from the community / decisions made, ask in the - appropriate public stream on [chat.zulip.org](https://chat.zulip.org). Often - someone can provide important context that you need to succeed in your - project. + appropriate public stream in + [the Zulip development community](https://zulip.com/developer-community/). Often + someone can provide important context that you need to succeed in your project. - Communicate clearly, especially in public places! You'll get much more useful feedback to a well-written Zulip message or GitHub issue comment than diff --git a/docs/development/setup-advanced.md b/docs/development/setup-advanced.md index be831ea171..8fdce3cf51 100644 --- a/docs/development/setup-advanced.md +++ b/docs/development/setup-advanced.md @@ -301,8 +301,8 @@ 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) -on chat.zulip.org, and a core team member can help guide you through -adding support for the platform. +in [the Zulip development community](https://zulip.com/developer-community/), +and a core team member can help guide you through adding support for the platform. [zulip-rtd-git-cloning]: ../git/cloning.html#step-1b-clone-to-your-machine [zulip-rtd-git-connect]: ../git/cloning.html#step-1c-connect-your-fork-to-zulip-upstream diff --git a/docs/production/requirements.md b/docs/production/requirements.md index adf41136e8..743e267f66 100644 --- a/docs/production/requirements.md +++ b/docs/production/requirements.md @@ -197,8 +197,8 @@ installing Zulip with a dedicated database server. subscribed (like on chat.zulip.org), add 20GB per (1000 user accounts) per (1M messages to public streams). -- **Example:** When the - [chat.zulip.org](https://zulip.com/developer-community/) community server +- **Example:** When + [the Zulip development community](https://zulip.com/developer-community/) server had 12K user accounts (~300 daily actives) and 800K messages of history (400K to public streams), it was a default configuration single-server installation with 16GB of RAM, 4 cores (essentially diff --git a/docs/production/settings.md b/docs/production/settings.md index f6c36bfe27..1f90b77ca0 100644 --- a/docs/production/settings.md +++ b/docs/production/settings.md @@ -32,8 +32,8 @@ to each new major release. [settings-py-template]: https://github.com/zulip/zulip/blob/main/zproject/prod_settings_template.py Since Zulip's settings file is a Python script, there are a number of -other things that one can configure that are not documented; ask on -[chat.zulip.org](https://zulip.com/developer-community/) +other things that one can configure that are not documented; ask in +[the Zulip development community](https://zulip.com/developer-community/) if there's something you'd like to do but can't figure out how to. ## Specific settings diff --git a/docs/production/upgrade-or-modify.md b/docs/production/upgrade-or-modify.md index 31b1e808fb..4b254d8e85 100644 --- a/docs/production/upgrade-or-modify.md +++ b/docs/production/upgrade-or-modify.md @@ -589,8 +589,8 @@ If you do modify Zulip and then report an issue you see in your modified version of Zulip, please be responsible about communicating that fact: -- Ideally, you'd reproduce the issue in an unmodified version (e.g. on - [chat.zulip.org](https://zulip.com/developer-community/) or +- Ideally, you'd reproduce the issue in an unmodified version (e.g. in + [the Zulip development community](https://zulip.com/developer-community/) or on [zulip.com](https://zulip.com)). - Where that is difficult or you think it's very unlikely your changes are related to the issue, just mention your changes in the issue report. diff --git a/docs/subsystems/performance.md b/docs/subsystems/performance.md index 1c3ee76817..f60ee1a126 100644 --- a/docs/subsystems/performance.md +++ b/docs/subsystems/performance.md @@ -34,7 +34,7 @@ of load profiles: etc. have large numbers of users, many of whom are idle. (Many of the others likely stopped by to ask a question, got it answered, and then didn't need the community again for the next year). Our own - [chat.zulip.org](https://zulip.com/developer-community/) is a good + [Zulip development community](https://zulip.com/developer-community/) is a good example for this, with more than 15K total user accounts, of which only several hundred have logged in during the last few weeks. Zulip has many important optimizations, including [soft diff --git a/docs/tutorials/new-feature-tutorial.md b/docs/tutorials/new-feature-tutorial.md index 5b15848384..c9fc4febcb 100644 --- a/docs/tutorials/new-feature-tutorial.md +++ b/docs/tutorials/new-feature-tutorial.md @@ -574,7 +574,8 @@ in. For example in this case of `mandatory_topics` it will lie in "Other settings" (`other_settings`) subsection. _If you're not sure in which section your feature belongs, it's -better to discuss it in the [community](https://chat.zulip.org/) +better to discuss it in +[the Zulip development community](https://zulip.com/developer-community/) before implementing it._ Note that some settings, like `realm_msg_edit_limit_setting`, diff --git a/templates/zerver/api/client-libraries.md b/templates/zerver/api/client-libraries.md index fd34cda0f0..cad0d6c6f0 100644 --- a/templates/zerver/api/client-libraries.md +++ b/templates/zerver/api/client-libraries.md @@ -32,9 +32,9 @@ Contributing to improve language libraries is appreciated, as is writing new ones. If you actively maintain a Zulip language binding and would like it to be listed here (or would like to collaborate with us in making it an official library), post in [this -topic][integrations-thread] on -[chat.zulip.org](/developer-community/) or submit a pull request -[updating this +topic][integrations-thread] in +[the Zulip development community](https://zulip.com/developer-community/) +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/ diff --git a/templates/zerver/api/running-bots.md b/templates/zerver/api/running-bots.md index 392c0bf1d5..eaf2dcc748 100644 --- a/templates/zerver/api/running-bots.md +++ b/templates/zerver/api/running-bots.md @@ -12,7 +12,7 @@ https://github.com/zulip/python-zulip-api/tree/main/zulip_bots/zulip_bots/bots). You'll need: * An account in a Zulip organization - (e.g. [chat.zulip.org](/developer-community/), + (e.g. [the Zulip development community](https://zulip.com/developer-community/), `.zulipchat.com`, or a Zulip organization on your own [development](https://zulip.readthedocs.io/en/latest/development/overview.html) or [production](https://zulip.readthedocs.io/en/latest/production/install.html) server). diff --git a/templates/zerver/for/communities.md b/templates/zerver/for/communities.md index 3e27258645..1ef66b7693 100644 --- a/templates/zerver/for/communities.md +++ b/templates/zerver/for/communities.md @@ -116,8 +116,8 @@ Zulip’s topic-based threading model solves the problems described above: ## Try Zulip today! -You can see Zulip in action in our own [chat.zulip.org -community](/developer-community/), which sends +You can see Zulip in action in our own +[Zulip development community](https://zulip.com/developer-community/), which sends thousands of messages a week. We often get feedback from contributors around the world that they love how responsive Zulip’s project leaders are in public Zulip conversations. We are able to achieve this despite diff --git a/templates/zerver/help/contact-support.md b/templates/zerver/help/contact-support.md index 58f39c4f67..c4c98fc2fa 100644 --- a/templates/zerver/help/contact-support.md +++ b/templates/zerver/help/contact-support.md @@ -3,7 +3,7 @@ General and technical support for Zulip is available through three channels: -* [chat.zulip.org][chat-zulip-org], the Zulip development community. +* [The Zulip development community][development-community]. Depending on the time of day/week of your query and the complexity of your question, you may get complete responses immediately or up to a couple days later, but Zulip's threading makes it easy for us @@ -17,15 +17,16 @@ channels: app](https://github.com/zulip/zulip-mobile/issues/new), [desktop app](https://github.com/zulip/zulip-desktop/issues/new). If you aren't able to provide a clear bug report or are otherwise - uncertain, it can be helpful to discuss in chat.zulip.org first to - help create a better GitHub issue. + uncertain, it can be helpful to discuss in + [the Zulip development community][development-community] + first to help create a better GitHub issue. * We don't offer phone support except as part of enterprise contracts. We love hearing feedback! Please reach out if you have feedback, questions, or just want to brainstorm how to make Zulip work for your organization. -[chat-zulip-org]: /developer-community/ +[development-community]: https://zulip.com/developer-community/ ## Billing and commercial questions