Communication

General Idea

It is important for all project-related communication to be logged for the sake of progress tracking. Our main methods of contacting each other should be the company mailing list and the GitHub issue tracker. The GitHub issue tracker should be used as much as possible, even when your intended contact is sitting right next to you.

No Spam Policy

Please don't spam your co-workers. Issues and emails sent to company mailing lists should be at least 10 words long (not counting signatures and formalities), have meaningful content and contain no disrespectful speech towards anyone.

Example Scenario: Modifying the class diagram/database schema

Suppose you wish to make a modification to the database schema/class diagram. You should raise an issue using GitHub and assign it to the class diagram owner and database owner. You must be as descriptive and as detailed as possible.

Example Scenario: Fixing a bug in an old story

Suppose you found a bug in code related to an old story. If this bug isn't yours, you should notify that story's assignee using the issue tracker.