chat zulip

Go to file

Steve Howell 2a07b204bf css parser: Show line numbers for errors. This is a fairly major overhaul of the CSS parser to support line numbers in error messages. Basically, instead of passing "slices" of tokens around, we pass indexes into the token arrays to all of our sub-parsers, which allows them to have access to previous tokens in certain cases. This is particularly important for errors where stuff is missing (vs. being wrong). In testing this out I found a few more places to catch errors.		2017-02-01 10:02:03 -08:00
.tx	Remove extra new lines at the ends of Zulip authoried files.	2016-09-26 21:05:24 -07:00
analytics	analytics: Add graphs of usage statistics on /stats.	2017-01-31 22:18:54 -08:00
api	Replace references to zulip.com/dist with zulip.org/dist.	2017-01-28 17:56:25 -08:00
bots	lint: Clean up E126 PEP-8 rule.	2017-01-23 22:06:13 -08:00
confirmation	Remove use of mailer.send_mail from all files.	2017-01-19 16:28:29 -08:00
contrib_bots	contrib_bots: Fix typos and repetitions in the readme.	2017-01-27 16:39:19 -08:00
corporate	docs: Remove obsolete terms-enterprise page.	2017-01-28 18:12:19 -08:00
docs	docs: Update release checklist to mention GitHub.	2017-02-01 09:48:00 -08:00
frontend_tests	Fix for TravisCI + casper.js race condition.	2017-01-31 17:53:20 -08:00
pgroonga	Support full text search for all languages using pgroonga.	2016-08-26 21:04:03 -07:00
puppet	puppet: Use SIGINT to restart uwsgi.	2017-01-28 22:26:12 -08:00
requirements	requirements: Add comment explaining why CommonMark can't be upgraded.	2017-01-24 14:22:06 -08:00
scripts	upgrade: Don't require authors updates deploying from Git.	2017-01-23 23:00:09 -08:00
static	analytics: Add graphs of usage statistics on /stats.	2017-01-31 22:18:54 -08:00
templates	analytics: Add graphs of usage statistics on /stats.	2017-01-31 22:18:54 -08:00
tools	css parser: Show line numbers for errors.	2017-02-01 10:02:03 -08:00
zerver	Add ping event handling to github webhook integration.	2017-02-01 00:38:16 +01:00
zilencer	Add a new community realm to our test databases.	2017-01-26 19:25:34 -08:00
zproject	analytics: Add graphs of usage statistics on /stats.	2017-01-31 22:18:54 -08:00
.coveralls.yml	Generate mypy coverage report for travis + coveralls.	2016-06-04 13:01:19 -07:00
.editorconfig	Update .editorconfig to use 4 spaces for handlebars/html.	2017-01-06 09:31:01 -08:00
.eslintignore	lint: Remove old jslint linter.	2016-12-02 18:49:42 -08:00
.eslintrc.json	build_emoji: Generate emoji names and codepoints from emoji_map.	2017-01-28 17:05:32 -08:00
.gitattributes	Force LF line-endings except for binary file types.	2016-10-17 20:19:55 -07:00
.gitignore	Add /authors page.	2017-01-17 13:35:55 -08:00
.npmignore	Add proxy notes to new README.dev.md troubleshooting section.	2016-03-29 21:54:05 -07:00
.travis.yml	travis-ci: add production Python 3 test suite.	2016-10-11 14:19:03 -07:00
Dockerfile	docker: Revert Docker development to original instructions.	2016-11-27 10:15:37 -08:00
LICENSE	License disclosures and project licensing.	2015-09-25 00:44:19 -07:00
README.md	docs: Wrap a bunch of long lines.	2017-01-05 14:31:34 -08:00
Vagrantfile	Add wrapper and log file output for provisioning.	2017-01-17 14:23:28 -08:00
manage.py	Activate virtualenv in production Python code.	2016-06-27 19:55:35 -07:00
package.json	Revert "deps: Upgrade and move `jquery-mousewheel` from `static/third` to `npm`"	2017-01-26 13:42:00 -08:00
version.py	build_emoji: Generate emoji names and codepoints from emoji_map.	2017-01-28 17:05:32 -08: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.

Community

There are several places online where folks discuss Zulip.

One of those places is our public Zulip instance. 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 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 a reply within minutes to a few hours, depending on time of day.

For Google Summer of Code students and applicants, we have a mailing list for help, questions, and announcements.

We have a public mailing list that is currently pretty low traffic because most discussions happen in our public Zulip instance. We use it to announce Zulip developer community gatherings and ask for feedback on major technical or design decisions. It has several hundred subscribers, so you can use it to ask questions about features or possible bugs, but please don't use it ask for generic help getting started as a contributor (e.g. because you want to do Google Summer of Code). The rest of this page covers how to get involved in the Zulip project in detail.

Zulip also has a blog.

Last but not least, we use GitHub to track Zulip-related issues (and store our code, of course). Anybody with a GitHub account should be able to create Issues there pertaining to bugs or enhancement requests. We also use Pull Requests as our primary mechanism to receive code contributions.

The Zulip community has a Code of Conduct.

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 supports Ubuntu 14.04 Trusty and Ubuntu 16.04 Xenial. 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.

Pull requests. Before a pull request can be merged, you need 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. You can also try out our new desktop client, which is in alpha; we'd appreciate testing and feedback.
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 are our experimental React Native iOS app and alpha Electron desktop app.
Glue code. We maintain a Hubot adapter and several integrations (Phabricator, Jenkins, Puppet, Redmine, and Trello), plus node.js API bindings, an isomorphic JavaScript library, 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!

Google Summer of Code

We participated in GSoC last year and hope to do so again in 2017. For guidance, please read our GSoC instructions and ideas page and feel free to email our GSoC mailing list.

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.

Another way to find issues in Zulip is to take advantage of our "area:" 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 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 docs/THIRDPARTY file included with this distribution.