Engagement/Integrated Marketing/Getting Started/Communications

Hooray! You're almost there. Now that you what you are doing, who is involved, and when it will happen, you need to define where the project team and contributors are going to communicate and collaborate. Given that Mozilla is an open-source organization and we plan, build, and communicate in the open, your project and all the artifacts should also be open by default. We understand that some project legally and technically cannot be open by default, but you should strive to be as transparent and open as possible. Start by being open and then if necessary, you can be less-open in some areas.

You should start by defining the communication channels and positing them to your project hub. The following are some communication channels with pros and cons to help you select which channels you should use for your project communications.

Probing questions on a communications platform

• Does it support public and open communications?
• Does it support real-time communications?
• Can you have long-running threaded conversations?
• Can you join in on a conversation or do you have to be manually invited in by someone else?
• Do you legally have to keep your communications private?
• Do you prefer platforms that seem familiar or do you like to learn something new?
• Do you want to create a new island of communications or do you want to go where everyone else is at?

Optional Platforms

IRC

IRC is a chat-like communications platform for real-time discussions that is accessible by anyone in the world. You can chat privately with specific people or you can chat in rooms specific to a project or a team.

Pros: Open, free, real-time synchronous, private 1:1 communications, desktop+mobile.

Cons: Typically requires an additional program or application like Colloquy to run, understanding the commands to join a room or private message someone. Without additional technology or reviewing logs, old messages are not saved.

Bugzilla Comments

While Bugzilla is Mozilla's primary bug-tracking system, a "bug" can represent anything. A bug can be a collection of activities to perform, a specific requirement needed, a tracking bug, or pretty much anything else. Within each bug, you can conversations. You can reply to people, post questions/comments, and specifically ask for a comment from one or more people. If you don't like how Bugzilla looks, tt is also recommened that you install BugzillaJS and Bugzilla Tweaks add-ons that dramatically improve the user experience.

Pros: Open by default, private communications, integration with other tools, large existing population of users, notifications.

Cons: Some people find all of the features and options overwhelming. Comments have to exist within a bug itself and there is no generic project conversation forum.

Basecamp

Basecamp is a web-based communications and collaboration tool that is broken down into four main areas: conversations, content, files, and calendar entries. Basecamp is a service that Mozilla pays for and is mainly used by just the Engagement team.

Pros: Web-based, asynchronous communication as old messages are retained, simple to use.

Cons: Private/closed communications and someone on the project has to manually add additional people to collaborate, no version control on files.

Mailing List

Mozilla's mailman mailing list service provides Mozillians the ability to create public e-mail based mailing lists for their team and/or project.

Pros: Public and open, asynchronous communication, anyone can create a list, anyone can subscribe, admins can add/remove people from the list, no additional tools since everyone already uses emails.

Cons: You will need to use your email program or web-based e-mail to communication and you should set up filters to keep the messages self-contained.

Yammer

Yammer is very similar to basecamp in terms of functionality except that it has more of a Facebook-UI.

Pros: All Mozilla employees have an account by default, you can create custom groups to collaborate on a specific topic or project.

Cons: Yammer is closed to the outside world unless their email are manually added to the system.

Recommendation

• Be open unless 100% necessary to be closed. Being closed does not support the Million Mozillians organization goal.
• Limited the amount of communication channels that you use on your project or team. Mozilla already creates a lot of "noise" and it can be confusing on projects where to listen to.
• Use Bugzilla for conversations on specific actions or deliverables and don't shy away from the tool because it looks confusing. Install the add-ons mentioned above.
• Learn IRC since that is how the rest of the company communicates in real-time and helps unblock each other.
• Don't start using a new communication tool unless you have evaluated it with the criteria above.