mirror of https://github.com/zulip/zulip.git
Document our "area:" labeling convention in README.md.
This commit is contained in:
parent
9afc130f21
commit
6a482a65d4
10
README.md
10
README.md
|
@ -172,6 +172,16 @@ mind:
|
||||||
* [2016 roadmap milestone](http://zulip.readthedocs.io/en/latest/roadmap.html): The
|
* [2016 roadmap milestone](http://zulip.readthedocs.io/en/latest/roadmap.html): The
|
||||||
projects that are [priorities for the Zulip project](https://zulip.readthedocs.io/en/latest/roadmap.html). These are great projects if you're looking to make an impact.
|
projects that are [priorities for the Zulip project](https://zulip.readthedocs.io/en/latest/roadmap.html). These are great projects if you're looking to make an impact.
|
||||||
|
|
||||||
|
Another way to find issues in Zulip is to take advantage of our
|
||||||
|
"area:<foo>" convention in separating out issues. We partition all of
|
||||||
|
our issues into areas like admin, compose, emoji, hotkeys, i18n,
|
||||||
|
onboarding, search, etc. You can see this here:
|
||||||
|
|
||||||
|
[https://github.com/zulip/zulip/labels]
|
||||||
|
|
||||||
|
Click on any of the "area:" labels and you will see all the tickets
|
||||||
|
related to your area of interest.
|
||||||
|
|
||||||
If you're excited about helping with an open issue, just post on the
|
If you're excited about helping with an open issue, just post on the
|
||||||
conversation thread that you're working on it. You're encouraged to
|
conversation thread that you're working on it. You're encouraged to
|
||||||
ask questions on how to best implement or debug your changes -- the
|
ask questions on how to best implement or debug your changes -- the
|
||||||
|
|
Loading…
Reference in New Issue