Slack was our main communication mechanism, and also served as a formal record of what has been discussed. After every meeting, we would post the meeting minutes on Slack. Thus, our #t3-dev channel contains the entire history of our project.

In addition, we added a GitHub integration to Slack, so activity (commit, pull request, issue) on any of our Git repositories would emit a message on our main channel. This made it much easier to see how the project is shaping up and to keep up to date with what other team members are doings.

For version control, we used Git, with our repositories hosted on GitHub. Since we had multiple repositories, we created an organisation. This way, all the repositories associated with the project are kept in a single place. This also made it easier to implement the GitHub integration for Slack.

You can see all our code, including the source for this website, at github.com/BitKariero

To store and share files between ourselves, we used Google Drive, as well as Slack's file sharing feature. In general, Slack was reserved for only output files (e.g. PDFs, SVGs), while Google Drive also stored the sources for these outputs (e.g. LaTeX sources).

For project management, we initially used Trello, although we abandoned it when we realized that it's less than ideal for our particular use-case (few tasks to keep track of). Eventually, we ended up using Slack to organise our tasks, as well.