Loading...
About this episode
Summary
In modern work environments the email is being edged out by group chat as the preferred method of communication. The majority of the platforms used are commercial and closed source, but there is one project that is working to change that. Zulip is a project that aims to redefine how effective teams communicate and it is already gaining ground. This week Tim Abbott shares the story of how Zulip got started, how it is built, and why you might want to start using it.
Preface
- Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
- I would like to thank everyone who supports us on Patreon. Your contributions help to make the show sustainable.
- When you’re ready to launch your next project you’ll need somewhere to deploy it. Check out Linode at www.podastinit.com/linode?utm_source=rss&utm_medium=rss and get a $20 credit to try out their fast and reliable Linux virtual servers for running your awesome app.
- Visit the site to subscribe to the show, sign up for the newsletter, read the show notes, and get in touch.
- To help other people find the show please leave a review on iTunes, or Google Play Music, tell your friends and co-workers, and share it on social media.
- Your host as usual is Tobias Macey and today I’m interviewing Tim Abbott about Zulip, a powerful open source group chat platform
Interview
- Introductions
- How did you get introduced to Python?
- What is Zulip and what was the initial inspiration for creating it?
- Where does the name come from?
- My understanding is that the project was initally intended to be a commercial product. Can you share some of the history of the acquisition by Dropbox and the journey to open sourcing it?
- How has your experience at Dropbox influenced the evolution and implementation of the Zulip project?
- There are a large number of group chat platforms available, both commercial and open source. How does Zulip differentiate itself from other options such as Slack or Mattermost?
- Typically real-time communication is difficult to achieve in a WSGI application. How is Zulip architected to allow for interactive communication?
- What have been the most challenging aspects of building and maintaining the Zulip project?
- What is involved in installing and running a Zulip server?
- For a large installation, what are the options for scaling it out to handle greater load?
- There is a large and healthy community that has built up around the Zulip project. What are some of the methods that you and others have used to foster that growth and engagement?
- What has been the most unexpected aspect of working on Zulip, whether technically or in terms of the community around it?
- What do you have planned for the future of Zulip?
Keep In Touch
Picks
Links
- Zulip
- Ksplice
- Electron
- React Native
- IFTTT
- Zapier
- Zephyr
- Barn Owl
- MyPy
- Tornado
- Django
- Zulip Tornado Documentation
- MySQL
- PostGreSQL
- ElasticSearch
- Code Triage
- Emoji
- Podcast.__init__ Zulip Chat
The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra / CC BY-SA
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
