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

README.md: Add mention of our blog and tweak intro.

This commit is contained in:
Tim Abbott 2016-10-19 12:18:51 -07:00
parent 3b74ed20fa
commit 08729d35ad
1 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -29,13 +29,16 @@ One of those places is our [public Zulip instance](https://zulip.tabbott.net/).
You can go through the simple signup process at that link, and then you You can go through the simple signup process at that link, and then you
will soon be talking to core Zulip developers and other users. To get will soon be talking to core Zulip developers and other users. To get
help in real time, you will have the best luck finding core developers help in real time, you will have the best luck finding core developers
roughly between 16:00 UTC and 23:59 UTC. Most questions get answered roughly between 16:00 UTC and 23:59 UTC. Most questions get a reply
within a day. within minutes to a few hours, depending on time of day.
We have a [Google mailing list](https://groups.google.com/forum/#!forum/zulip-devel) We have a
that is currently pretty low traffic. It is where we do things like [Google mailing list](https://groups.google.com/forum/#!forum/zulip-devel)
announce public meetings or major releases. You can also use it to that is currently pretty low traffic because a lot of discussions
ask questions about features or possible bugs. happen in our public Zulip instance. We use it to announce Zulip
developer community gatherings and ask for feedback on technical or
design decisions. You can use it to ask questions about features or
possible bugs. Zulip also has a [blog](https://blog.zulip.org/).
Last but not least, we use [GitHub](https://github.com/zulip/zulip) to Last but not least, we use [GitHub](https://github.com/zulip/zulip) to
track Zulip-related issues (and store our code, of course). track Zulip-related issues (and store our code, of course).