mirror of https://github.com/zulip/zulip.git
docs: Update `docs/outreach/` files to use channel.
Updates descriptive text that refer to Zulip channels in the `docs/outreach` files to use channel instead of stream. Part of the stream to channel rename project.
This commit is contained in:
parent
80511ea8ba
commit
0d175174b5
|
@ -66,7 +66,7 @@ We recommend taking the following steps before diving into the issue tracker:
|
||||||
|
|
||||||
- Join the [Zulip development
|
- Join the [Zulip development
|
||||||
community](https://zulip.com/development-community/), and introduce yourself
|
community](https://zulip.com/development-community/), and introduce yourself
|
||||||
in the stream for the program you are participating in
|
in the channel for the program you are participating in
|
||||||
([#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
|
([#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
|
||||||
[#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)). Before you
|
[#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)). Before you
|
||||||
jump in, be sure to review the [Zulip community
|
jump in, be sure to review the [Zulip community
|
||||||
|
@ -181,7 +181,7 @@ give you feedback and help you improve your proposal.
|
||||||
context.
|
context.
|
||||||
|
|
||||||
- Please post a link to your draft in the Zulip development community
|
- Please post a link to your draft in the Zulip development community
|
||||||
stream dedicated to your program (e.g.,
|
channel dedicated to your program (e.g.,
|
||||||
[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
|
[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
|
||||||
[#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)). Use
|
[#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)). Use
|
||||||
`Your name - project proposal` as the topic.
|
`Your name - project proposal` as the topic.
|
||||||
|
|
|
@ -53,7 +53,7 @@ mentorship program will:
|
||||||
- Receive lots of feedback and mentorship from others in the Zulip development
|
- Receive lots of feedback and mentorship from others in the Zulip development
|
||||||
community, in code reviews on pull requests, and by posting
|
community, in code reviews on pull requests, and by posting
|
||||||
[questions](../contributing/asking-great-questions.md) and ideas in public
|
[questions](../contributing/asking-great-questions.md) and ideas in public
|
||||||
streams.
|
channels.
|
||||||
|
|
||||||
Mentors and contributors should stay in close contact. We recommend setting up a
|
Mentors and contributors should stay in close contact. We recommend setting up a
|
||||||
weekly check-in call to make sure you stay on track and have a regular
|
weekly check-in call to make sure you stay on track and have a regular
|
||||||
|
@ -80,9 +80,9 @@ to get a feel for what they are working on and share ideas!
|
||||||
### Getting feedback and advice
|
### Getting feedback and advice
|
||||||
|
|
||||||
We strongly encourage all Zulip contributors to post their questions and ideas
|
We strongly encourage all Zulip contributors to post their questions and ideas
|
||||||
in public streams in the [Zulip development
|
in public channels in the [Zulip development
|
||||||
community](https://zulip.com/development-community/). When you post in a public
|
community](https://zulip.com/development-community/). When you post in a public
|
||||||
stream, you give everyone the opportunity to help you out, and to learn from
|
channel, you give everyone the opportunity to help you out, and to learn from
|
||||||
reading the discussion.
|
reading the discussion.
|
||||||
|
|
||||||
Examples of topics you might ask about include:
|
Examples of topics you might ask about include:
|
||||||
|
@ -104,7 +104,7 @@ to ask your questions effectively.
|
||||||
A check-in is a regular update that you post in the Zulip development community.
|
A check-in is a regular update that you post in the Zulip development community.
|
||||||
You can find many examples in the
|
You can find many examples in the
|
||||||
[#checkins](https://chat.zulip.org/#narrow/stream/65-checkins) and
|
[#checkins](https://chat.zulip.org/#narrow/stream/65-checkins) and
|
||||||
[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) streams.
|
[#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) channels.
|
||||||
|
|
||||||
- **Frequency**: _Regular check-ins are a required for all program
|
- **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
|
participants._ If you are working 20+ hours per week, post a check-in at least
|
||||||
|
@ -112,7 +112,7 @@ You can find many examples in the
|
||||||
per week, post a check-in at least once a week.
|
per week, post a check-in at least once a week.
|
||||||
|
|
||||||
- **Where to post**: Unless your mentor or program administrator requests
|
- **Where to post**: Unless your mentor or program administrator requests
|
||||||
otherwise, post your check-ins in the stream for your program
|
otherwise, post your check-ins in the channel for your program
|
||||||
(e.g., [#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
|
(e.g., [#GSoC](https://chat.zulip.org/#narrow/stream/14-GSoC) or
|
||||||
[#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)), using your
|
[#Outreachy](https://chat.zulip.org/#narrow/stream/391-Outreachy)), using your
|
||||||
name as the topic.
|
name as the topic.
|
||||||
|
@ -136,9 +136,9 @@ You can find many examples in the
|
||||||
separate message to make it convenient to quote-and-reply to address it.
|
separate message to make it convenient to quote-and-reply to address it.
|
||||||
Note that discussions about your work will happen in all the usual places
|
Note that discussions about your work will happen in all the usual places
|
||||||
(#**frontend**, #**backend**, #**design**, etc.), and those are the
|
(#**frontend**, #**backend**, #**design**, etc.), and those are the
|
||||||
streams where you should be _starting_ conversations. Your check-ins are a
|
channels where you should be _starting_ conversations. Your check-ins are a
|
||||||
place to point out where you're feeling stuck, e.g., there was some
|
place to point out where you're feeling stuck, e.g., there was some
|
||||||
discussion in a stream or on GitHub, but it seems to have petered out
|
discussion in a channel or on GitHub, but it seems to have petered out
|
||||||
without getting to a decision, and you aren't sure what to do.
|
without getting to a decision, and you aren't sure what to do.
|
||||||
|
|
||||||
- What you've been **actively working** on since your last check-in.
|
- What you've been **actively working** on since your last check-in.
|
||||||
|
|
|
@ -160,7 +160,7 @@ Django, TypeScript/JavaScript, and CSS.
|
||||||
open-source projects. Much of the basic design, API structure, and scaffolding
|
open-source projects. Much of the basic design, API structure, and scaffolding
|
||||||
is complete, but there is a lot of work that remains to complete this vision.
|
is complete, but there is a lot of work that remains to complete this vision.
|
||||||
The project can likely support a couple students; there is considerable work
|
The project can likely support a couple students; there is considerable work
|
||||||
to be done on the settings UI, both for user groups and for stream and
|
to be done on the settings UI, both for user groups and for channel and
|
||||||
organization-level settings, dozens of existing settings to migrate, and [many
|
organization-level settings, dozens of existing settings to migrate, and [many
|
||||||
new settings][organization-settings-label] that users have long requested that
|
new settings][organization-settings-label] that users have long requested that
|
||||||
we've delayed adding in order to avoid having to migrate them. 175 or 350
|
we've delayed adding in order to avoid having to migrate them. 175 or 350
|
||||||
|
@ -171,19 +171,19 @@ Django, TypeScript/JavaScript, and CSS.
|
||||||
Experts: Sahil Batra
|
Experts: Sahil Batra
|
||||||
|
|
||||||
- Improve the framework and UI in **Zulip's overlays for managing
|
- Improve the framework and UI in **Zulip's overlays for managing
|
||||||
streams and groups**. These two components have very parallel design
|
channels and groups**. These two components have very parallel design
|
||||||
patterns and implementations (the groups one is quite new!). Coupled
|
patterns and implementations (the groups one is quite new!). Coupled
|
||||||
with the user groups permissions migration, the goal of this project
|
with the user groups permissions migration, the goal of this project
|
||||||
is to make these important settings panels ergonomic for the large
|
is to make these important settings panels ergonomic for the large
|
||||||
number of new settings that we expect to migrate or add via the
|
number of new settings that we expect to migrate or add via the
|
||||||
groups migration. See the [user groups
|
groups migration. See the [user groups
|
||||||
settings][group-settings-issues] and [stream
|
settings][group-settings-issues] and [channel
|
||||||
settings][stream-settings-issues] area labels for starter projects.
|
settings][channel-settings-issues] area labels for starter projects.
|
||||||
|
|
||||||
Experts: Purushottam Tiwari, Sahil Batra
|
Experts: Purushottam Tiwari, Sahil Batra
|
||||||
|
|
||||||
[group-settings-issues]: https://github.com/zulip/zulip/issues?q=is%3Aissue+is%3Aopen+label%3A%22area%3A+settings+%28user+groups%29%22
|
[group-settings-issues]: https://github.com/zulip/zulip/issues?q=is%3Aissue+is%3Aopen+label%3A%22area%3A+settings+%28user+groups%29%22
|
||||||
[stream-settings-issues]: https://github.com/zulip/zulip/issues?q=is%3Aopen+is%3Aissue+label%3A%22area%3A+stream+settings%22
|
[channel-settings-issues]: https://github.com/zulip/zulip/issues?q=is%3Aopen+is%3Aissue+label%3A%22area%3A+stream+settings%22
|
||||||
[user-group-permissions]: https://github.com/zulip/zulip/issues/19525
|
[user-group-permissions]: https://github.com/zulip/zulip/issues/19525
|
||||||
[organization-settings-label]: https://github.com/zulip/zulip/issues?q=is%3Aopen+is%3Aissue+label%3A%22area%3A+settings+%28admin%2Forg%29%22
|
[organization-settings-label]: https://github.com/zulip/zulip/issues?q=is%3Aopen+is%3Aissue+label%3A%22area%3A+settings+%28admin%2Forg%29%22
|
||||||
|
|
||||||
|
|
|
@ -48,7 +48,7 @@ participants.
|
||||||
Zulip operates under a **group mentorship** model. While you will have an
|
Zulip operates under a **group mentorship** model. While you will have an
|
||||||
assigned mentor, you will also get lots of feedback from other members of the
|
assigned mentor, you will also get lots of feedback from other members of the
|
||||||
[Zulip development community](https://zulip.com/development-community/) by
|
[Zulip development community](https://zulip.com/development-community/) by
|
||||||
posting your questions and ideas in public streams. We encourage outreach
|
posting your questions and ideas in public channels. We encourage outreach
|
||||||
program participants to help each other out as well!
|
program participants to help each other out as well!
|
||||||
|
|
||||||
Program participants work on a variety of issues in their areas of interest,
|
Program participants work on a variety of issues in their areas of interest,
|
||||||
|
|
Loading…
Reference in New Issue