chat zulip

Go to file

Nathan Florea 5fe9076631 Remove some mutable default arguments. These ones don't fix any bugs, because the mutable arg is never passed outside of the callable or mutated. But it's good practice to not use them in case those invariants are changed in the future.		2016-06-03 09:16:56 -07:00
.tx	[third] Integrate i18next with Handlebars	2016-05-19 22:58:25 -07:00
analytics	Replace python2.7 by python everywhere.	2016-05-29 05:03:08 -07:00
api	api: Remove some mutable default arguments.	2016-06-03 09:16:52 -07:00
assets	Change shebangs from python2.7 to python.	2016-05-29 05:03:08 -07:00
bots	Replace python2.7 by python everywhere.	2016-05-29 05:03:08 -07:00
confirmation	confirmation: Fix trailing whitespace.	2016-05-09 16:49:33 -07:00
corporate	Enable i18n support in URL configuration.	2016-05-19 08:33:30 -07:00
docs	Docs: Fix typos in docs.	2016-06-02 10:31:41 -07:00
frontend_tests	Refresh page when message with /me is edited.	2016-05-31 08:29:07 -07:00
locale	Change instances of 'coworkers' to 'users'.	2016-06-02 16:05:27 -07:00
node_modules/.bin	Remove the committed handlebars package and install it via npm.	2015-11-06 09:09:41 -08:00
puppet	Replace python2.7 by python everywhere.	2016-05-29 05:03:08 -07:00
scripts	Fix hanging nc and 'invalid wait time' error on Trusty.	2016-06-02 18:02:13 -07:00
static	Change instances of 'coworkers' to 'users'.	2016-06-02 16:05:27 -07:00
templates	Change instances of 'coworkers' to 'users'.	2016-06-02 16:05:27 -07:00
tools	Remove some mutable default arguments.	2016-06-03 09:16:56 -07:00
zerver	Remove some mutable default arguments.	2016-06-03 09:16:56 -07:00
zilencer	Type annotation of zerver/models.py	2016-06-02 23:28:34 -07:00
zproject	Harden extraction of AUTH_LDAP_BIND_PASSWORD.	2016-05-31 15:06:43 -07:00
.gitattributes	Update provisioning/release scripts to build `.mo` files.	2016-05-18 19:30:00 -07:00
.gitignore	Move tools/emoji_dump to tools/setup/.	2016-05-26 18:28:14 +05:00
.npmignore	Add proxy notes to new README.dev.md troubleshooting section.	2016-03-29 21:54:05 -07:00
.travis.yml	Add code to clean the venv cache of old venvs.	2016-05-03 15:04:03 -07:00
Dockerfile	Add support for a development environment with Docker.	2015-12-14 18:22:56 -08:00
LICENSE	License disclosures and project licensing.	2015-09-25 00:44:19 -07:00
README.dev.md	Improve first-time contributor docs.	2016-05-31 07:47:45 -07:00
README.md	Add anchor tags to README.md.	2016-05-31 11:27:21 -07:00
README.prod.md	README.prod.md: Remove redundant unpacking of the tarball.	2016-06-02 10:32:52 -07:00
THIRDPARTY	Move tools/emoji_dump to tools/setup/.	2016-05-26 18:28:14 +05:00
Vagrantfile	Reduce development environment RAM requirements by 750MB.	2016-05-12 16:12:43 -07:00
manage.py	Change shebangs from python2.7 to python.	2016-05-29 05:03:08 -07:00
package.json	[third] Integrate i18next with Handlebars	2016-05-19 22:58:25 -07:00
provision.py	Fix most redownloading in 'vagrant reload --provision'.	2016-06-02 22:32:56 -07:00
requirements.txt	requirements: Add ipython dependencies.	2016-05-19 22:55:55 -07:00
zulip_tools.py	Change shebangs from python2.7 to python.	2016-05-29 05:03:08 -07:00

README.md

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.

Installing the Zulip Development environment

The Zulip development environment is the recommended option for folks interested in trying out Zulip. This is documented in README.dev.md.

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 README.prod.md.

Ways to contribute

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

Pull requests. Before a pull request can be merged, you need to to sign the Dropbox Contributor License Agreement. Also, please skim our commit message style guidelines.
Testing. The Zulip automated tests all run automatically when you submit a pull request, but you can also run them all in your development environment following the instructions in the testing docs.
Developer Documentation. Zulip has a growing collection of developer documentation on Read The Docs. Recommended reading for new contributors includes the directory structure and new feature tutorial. You can also improve Zulip.org.
Mailing lists and bug tracker. Zulip has a development discussion mailing list and uses GitHub issues . There are also lists for the Android and iOS apps. Feel free to send any questions or suggestions of areas where you'd love to see more documentation to the relevant list! Please report any security issues you discover to zulip-security@googlegroups.com.
App codebases. This repository is for the Zulip server and web app (including most integrations); the desktop, Android, and iOS apps, are separate repositories, as is our experimental React Native iOS app.
Glue code. We maintain a Hubot adapter and several integrations (Phabricator, Jenkins, Puppet, Redmine, and Trello), plus node.js API bindings, and a full-text search PostgreSQL extension, as separate repos.
Translations. Zulip is in the process of being translated into 10+ languages, and we love contributions to our translations. See our translating documentation if you're interested in contributing!

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

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.