docs: Improve discussion of GitHub area teams.

The content in that paragraph had been written when GSoC was mainly
zulip/zulip.
This commit is contained in:
Tim Abbott 2019-05-19 16:19:47 -07:00
parent cd1ec37404
commit 119948022f
1 changed files with 13 additions and 5 deletions

View File

@ -86,11 +86,19 @@ materials](https://developers.google.com/open-source/gsoc/resources/manual).
stressed about something involving your mentor, bring it up with stressed about something involving your mentor, bring it up with
an organization admin. an organization admin.
- Join Zulip's GitHub teams that relate to your projects and/or interests, so - If you work in one a smaller Zulip project
that you see new issues and PRs coming in that are relevant to your work. (e.g. `zulip-terminal`), follow the project on GitHub so you can
You can browse the area teams here: keep track of what's happening there. For folks working in
https://github.com/orgs/zulip/teams (You need to be a member of `zulip/zulip`, doing that will send you too many notifications.
the Zulip organization to see them; ask Tim for an invite if needed). So instead, we recommend that you join Zulip's GitHub teams that
relate to your projects and/or interests, so that you see new
issues and PRs coming in that are relevant to your work. When we
label an issue or PR with one of our area labels, `zulipbot` will
automatically mention the relevant teams for that area,
subscribing you to those issues/PR threads. You can browse the
area teams here: https://github.com/orgs/zulip/teams (You need to
be a member of the Zulip organization to see them;
ask Tim for an invite if needed).
- Everyone's goal is to avoid students ending up blocked and feeling stuck. - Everyone's goal is to avoid students ending up blocked and feeling stuck.
There are lots of things that students can do (and mentors can help them to) There are lots of things that students can do (and mentors can help them to)