Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

README: Fix some formatting and add some links in final section. 

The `<foo>` was rendering empty, I think because the Markdown
processor was interpreting it as a malformed attempt at HTML,
so that it read 'our "area:" convention'.
This commit is contained in:
Greg Price 2017-06-07 13:37:10 -07:00 committed by Tim Abbott
parent 1e478bb50f
commit b805f21f80
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -209,14 +209,12 @@ mind:
These are great projects if you're looking to make an impact. 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 Another way to find issues in Zulip is to take advantage of our
"area:<foo>" convention in separating out issues. We partition all of `area:<foo>` convention in separating out issues. We partition all of
our issues into areas like admin, compose, emoji, hotkeys, i18n, our issues into areas like admin, compose, emoji, hotkeys, i18n,
onboarding, search, etc. You can see this here: onboarding, search, etc. Look through our
[list of labels](https://github.com/zulip/zulip/labels), and click on
<https://github.com/zulip/zulip/labels> some of the `area:` labels to see all the tickets related to your
areas of interest.
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, make sure to claim If you're excited about helping with an open issue, make sure to claim
the issue by commenting the following in the comment section: the issue by commenting the following in the comment section:
@ -254,8 +252,10 @@ get broad feedback before you spend too much time on implementation
details. details.
Finally, before implementing a larger feature, we highly recommend Finally, before implementing a larger feature, we highly recommend
looking at the new feature tutorial and coding style guidelines on looking at the
ReadTheDocs. [new feature tutorial](http://zulip.readthedocs.io/en/latest/new-feature-tutorial.html)
and [coding style guidelines](http://zulip.readthedocs.io/en/latest/code-style.html)
on ReadTheDocs.
Feedback on how to make this development process more efficient, fun, Feedback on how to make this development process more efficient, fun,
and friendly to new contributors is very welcome! Just send an email and friendly to new contributors is very welcome! Just send an email