mirror of https://github.com/zulip/zulip.git
docs: Remove paragraph about getting help finding issues in contributing.
Removes a paragraph about posting in the new members stream to get help finding issues to work on from the first contribution part of the contributing guide. Also updates the remaining section about posting to new members as a way to introduce yourself with a link to the community norms and offering positive feedback as well as constructive criticism.
This commit is contained in:
parent
c2bcfb52aa
commit
53ed7d5ce2
|
@ -76,12 +76,13 @@ to help.
|
||||||
|
|
||||||
- First, make an account on the
|
- First, make an account on the
|
||||||
[Zulip community server](https://zulip.com/development-community/),
|
[Zulip community server](https://zulip.com/development-community/),
|
||||||
paying special attention to the community norms. If you'd like, introduce
|
paying special attention to the
|
||||||
yourself in
|
[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/stream/95-new-members), using
|
||||||
your name as the topic. Bonus: tell us about your first impressions of
|
your name as the topic. Bonus: tell us about your first impressions of
|
||||||
Zulip, and anything that felt confusing/broken as you started using the
|
Zulip, and anything that felt confusing/broken or interesting/helpful as you
|
||||||
product.
|
started using the product.
|
||||||
- Read [What makes a great Zulip contributor](#what-makes-a-great-zulip-contributor).
|
- Read [What makes a great Zulip contributor](#what-makes-a-great-zulip-contributor).
|
||||||
- [Install the development environment](https://zulip.readthedocs.io/en/latest/development/overview.html),
|
- [Install the development environment](https://zulip.readthedocs.io/en/latest/development/overview.html),
|
||||||
getting help in
|
getting help in
|
||||||
|
@ -146,14 +147,6 @@ Note that you are _not_ claiming an issue while you are iterating through steps
|
||||||
1-4. _Before you claim an issue_, you should be confident that you will be able to
|
1-4. _Before you claim an issue_, you should be confident that you will be able to
|
||||||
tackle it effectively.
|
tackle it effectively.
|
||||||
|
|
||||||
If the lists of issues are overwhelming, you can post in
|
|
||||||
[#new members](https://chat.zulip.org/#narrow/stream/95-new-members) with a
|
|
||||||
bit about your background and interests, and we'll help you out. The most
|
|
||||||
important thing to say is whether you're looking for a backend (Python),
|
|
||||||
frontend (JavaScript and TypeScript), mobile (React Native), desktop (Electron),
|
|
||||||
documentation (English) or visual design (JavaScript/TypeScript + CSS) issue, and a
|
|
||||||
bit about your programming experience and available time.
|
|
||||||
|
|
||||||
Additional tips for the [main server and web app
|
Additional tips for the [main server and web app
|
||||||
repository](https://github.com/zulip/zulip/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22):
|
repository](https://github.com/zulip/zulip/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22):
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue