Go to file
Tim Abbott c25b077224 settings: Extract settings.SHOW_OSS_ANNOUNCEMENT. 2016-07-19 15:28:41 -07:00
.tx Move locale to static/locale 2016-07-18 13:59:07 -07:00
analytics Wrap some lines with length greater than 120. 2016-07-06 14:35:16 -07:00
api Add support for client certs to the Python API. 2016-07-19 14:40:26 -07:00
assets Change shebangs from python2.7 to python. 2016-05-29 05:03:08 -07:00
bots Wrap some lines with length greater than 120. 2016-07-06 14:35:16 -07:00
confirmation Unique link generator for realm creation. 2016-06-30 15:52:41 -07:00
corporate Enable i18n support in URL configuration. 2016-05-19 08:33:30 -07:00
docs docs: Fix headings for possible testing issues. 2016-07-19 15:00:14 -07:00
frontend_tests 06-settings.js: Rearrange code for readability. 2016-07-19 08:57:42 -07:00
node_modules/.bin Remove the committed handlebars package and install it via npm. 2015-11-06 09:09:41 -08:00
puppet Patch httpoxy security issue. 2016-07-18 10:24:03 -07:00
requirements tools/provision.py: Install a python2 venv with twisted. 2016-07-19 14:15:35 -07:00
scripts Use stripped down version of Talon. 2016-07-13 11:24:18 -07:00
static settings: Extract settings.SAVE_FRONTEND_STACKTRACES. 2016-07-19 15:28:41 -07:00
templates settings: Extract settings.SHOW_OSS_ANNOUNCEMENT. 2016-07-19 15:28:41 -07:00
tools Run frontend and backend tests in python3 on Travis. 2016-07-19 14:15:35 -07:00
zerver settings: Extract settings.SHOW_OSS_ANNOUNCEMENT. 2016-07-19 15:28:41 -07:00
zilencer zilencer/management/commands/populate_db.py: Fix line with len > 120. 2016-07-18 14:42:39 -07:00
zproject settings: Extract settings.SHOW_OSS_ANNOUNCEMENT. 2016-07-19 15:28:41 -07:00
.coveralls.yml Generate mypy coverage report for travis + coveralls. 2016-06-04 13:01:19 -07:00
.gitattributes Update provisioning/release scripts to build `.mo` files. 2016-05-18 19:30:00 -07:00
.gitignore gitignore: Remove unnecessary files and dirs. 2016-07-18 14:13:33 -07:00
.npmignore Add proxy notes to new README.dev.md troubleshooting section. 2016-03-29 21:54:05 -07:00
.travis.yml Run frontend and backend tests in python3 on Travis. 2016-07-19 14:15:35 -07:00
Dockerfile Dockerfile: Create symlink in home folder for project. 2016-06-17 11:48:59 -07:00
LICENSE License disclosures and project licensing. 2015-09-25 00:44:19 -07:00
README.dev.md Split out generic UNIX developer install doc. 2016-07-19 14:57:07 -07:00
README.md Update links in README and integration guide. 2016-07-19 14:57:07 -07:00
README.prod.md Move prod postgres details to separate page. 2016-07-12 15:46:10 -07:00
THIRDPARTY Add codepointat.js, a polyfill for String.prototype.codePointAt(). 2016-06-30 15:48:02 -07:00
Vagrantfile Vagrantfile: Add option for setting the port used on the host. 2016-07-07 15:17:44 -07:00
manage.py Activate virtualenv in production Python code. 2016-06-27 19:55:35 -07:00
package.json [third] Upgrade jquery to version 1.8.3. 2016-07-08 11:09:54 -07:00
zulip_tools.py Annotate zulip_tools.py. 2016-07-12 10:10:22 -07:00

README.md

Zulip overview | Installing for dev | Installing for production | Ways to contribute | How to get involved | License

Zulip overview

Zulip is a powerful, open source group chat application. Written in Python and using the Django framework, Zulip supports both private messaging and group chats via conversation streams.

Zulip also supports fast search, drag-and-drop file uploads, image previews, group private messages, audible notifications, missed-message emails, desktop apps, and much more.

Further information on the Zulip project and its features can be found at https://www.zulip.org.

Build Status Coverage Status

Installing the Zulip Development environment

The Zulip development environment is the recommended option for folks interested in trying out Zulip. This is documented in the developer installation guide.

Running Zulip in production

Zulip in production only supports Ubuntu 14.04 right now, but work is ongoing on adding support for additional platforms. The installation process is documented at https://zulip.org/server.html and in more detail in the documentation.

Ways to contribute

Zulip welcomes all forms of contributions! The page documents the Zulip development process.

How to get involved with contributing to Zulip

First, subscribe to the Zulip development discussion mailing list.

The Zulip project uses a system of labels in our issue tracker to make it easy to find a project if you don't have your own project idea in mind or want to get some experience with working on Zulip before embarking on a larger project you have in mind:

  • Integrations. Integrate Zulip with another piece of software and contribute it back to the community! Writing an integration can be a great first contribution. There's detailed documentation on how to write integrations in the Zulip integration writing guide.

  • Bite Size: Smaller projects that might be a great first contribution.

  • Documentation: The Zulip project loves contributions of new documentation.

  • Help Wanted: A broader list of projects that nobody is currently working on.

  • Platform support: These are open issues about making it possible to install Zulip on a wider range of platforms.

  • Bugs: Open bugs.

  • Feature requests: Browsing this list can be a great way to find feature ideas to implement that other Zulip users are excited about.

  • 2016 roadmap milestone: The projects that are priorities for the Zulip project. These are great projects if you're looking to make an impact.

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 ask questions on how to best implement or debug your changes -- the Zulip maintainers are excited to answer questions to help you stay unblocked and working efficiently.

We also welcome suggestions of features that you feel would be valuable or changes that you feel would make Zulip a better open source project, and are happy to support you in adding new features or other user experience improvements to Zulip.

If you have a new feature you'd like to add, we recommend you start by opening a GitHub issue about the feature idea explaining the problem that you're hoping to solve and that you're excited to work on it. A Zulip maintainer will usually reply within a day with feedback on the idea, notes on any important issues or concerns, and and often tips on how to implement or test it. Please feel free to ping the thread if you don't hear a response from the maintainers -- we try to be very responsive so this usually means we missed your message.

For significant changes to the visual design, user experience, data model, or architecture, we highly recommend posting a mockup, screenshot, or description of what you have in mind to zulip-devel@ to get broad feedback before you spend too much time on implementation details.

Finally, before implementing a larger feature, we highly recommend looking at the new feature tutorial and coding style guidelines on ReadTheDocs.

Feedback on how to make this development process more efficient, fun, and friendly to new contributors is very welcome! Just send an email to the Zulip Developers list with your thoughts.

License

Copyright 2011-2015 Dropbox, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

The software includes some works released by third parties under other free and open source licenses. Those works are redistributed under the license terms under which the works were received. For more details, see the THIRDPARTY file included with this distribution.