Title: Continuous integration for MAT
Date: 2015-11-27 13:00

<style>
.post img {
	display: inline;
	margin-left:0;
	}
</style>

Five months ago, someone asked me why MAT wasn't on github.
It's for several reasons:

- The *official* [git repository]( https://gitweb.torproject.org/user/jvoisin/mat.git)
  is hosted on the [Tor project]( https://torproject.org) infrastructure,
  the [bug tracker]( https://labs.riseup.net/code/projects/mat ) is on
  [riseup]( https://riseup.net ), and the [official website](
  https://mat.boum.org ) on [boum.org]( https://boum.org ), maintained by people I know and trust.
  I don't want to ask user/contributors/translators to use websites that I
  don't trust, or know for sure that they won't deliberately harm them.
- Github had [issues with subjects important to me](
  https://github.com/blog/1826-follow-up-to-the-investigation-results ) in the past.
- MAT already has a bugtracker, a git repository, and a website for
  documentation, there is no need to duplicate this on a closed platform.

But I was curious, and I created a [mirror]( https://github.com/jvoisin/MAT )
on github, to see if I would gain contributors by doing so. So far, I only got
one, [Raphaël Vinot]( https://github.com/Rafiot ), who (patiently) gave me everything I
needed (code, snippets, ideas, motivation) to use [continuous integration](
https://en.wikipedia.org/wiki/Continuous_integration ) with MAT.

If you take a look at the [github]( https://github.com/jvoisin/MAT )
repository, you'll see new shiny badges:

- [![Travis-CI build status](
  https://travis-ci.org/jvoisin/MAT.svg?branch=master )](
  https://travis-ci.org/jvoisin/MAT ) indicates if the [testsuite]( https://gitweb.torproject.org/user/jvoisin/mat.git/tree/test ) is
  currently passing on the latest `master` branch thanks to [Travis](
  https://travis-ci.org/ ), which also test your pull requests.
- [![Coveralls status](
  https://coveralls.io/repos/jvoisin/MAT/badge.svg?branch=master&service=github
  )]( https://coveralls.io/github/jvoisin/MAT?branch=master ) and [![codecov.io
  status]( https://codecov.io/github/jvoisin/MAT/coverage.svg?branch=master )](
  https://codecov.io/github/jvoisin/MAT?branch=master ) are about the current
  percentage of coverage achieved by the testsuite.
- [![Landascape.io
  status](https://landscape.io/github/jvoisin/MAT/master/landscape.svg?style=flat)](https://landscape.io/github/jvoisin/MAT/master)
  and [![Codacy status](
  https://api.codacy.com/project/badge/grade/17830b47b8db4878ac0560906050809c
  )]( https://www.codacy.com/app/julien-voisin/MAT ) are looking at the code
  quality/cleanness.

As [said on the mailing list](
https://mailman.boum.org/pipermail/mat-dev/2015-November/000115.html ):

> I don't want to include the badges on the official website, because I
> don't want users to make requests to external websites when browsing
> MAT's one. And neither do I want to change the website to update badges
> for every commit.

I'm not using those services only to attract new contributors with shiny
colours, they are helping me keeping MAT in good shape, and improving the test
coverage. 

By the way, speaking of MAT, I'll **try** to do a new release by next year first
trimester :)