Integration between tools

For the documentation, communication and development of the FieldTrip project we use various tools. This page lists the tools and the integrations between them.

Jekyll

We use Jekyll for our website. The markdown documents are hosted on GitHub and use a webhook to trigger the rebuild of the static html files on the webserver. The webserver is hosted as a virtual machine at the DCCN.

Mailman

We use this for a number of email discussion lists. It is hosted by C&CZ at http://mailman.science.ru.nl. The Google search on the website also searches the email list archives.

Facebook

We use http://facebook.com/fieldtriptoolbox to announce events and to post photos and messages that relate to the social interaction between developers and users. The Facebook page is not used to provide support. People who like our Facebook page are displayed on the start page. Photos from Facebook albums are sometimes used in the news messages on the home page.

Twitter

We use http://twitter.com/fieldtriptoolbx to notify people about updates. Commits of new code are automatically tweeted.

Bitly

We use Bitly to automatically create short URLs that are included in the tweets.

YouTube

We use a YouTube video channel that contains video recordings of lectures. More details are here and here.

GitHub

We use Git and GitHub for version control of the software and of the website, and for managing external contributions. More details can be found here. We also maintain a copy of the repository on BitBucket and on Gitlab.

If changes are pushed to GitHub, a webhook is triggered. The code for that is maintained at http://github.com/fieldtrip/automation.

Bitbucket

A copy of the git repository of the FieldTrip software is maintained on https://bitbucket.org/fieldtriptoolbox/fieldtrip, although the primary site is on GitHub.

Gitlab

A copy of the git repository of the FieldTrip software is stored on https://gitlab.com/fieldtrip/fieldtrip, although the primary site is on GitHub.

Google

We use Google to provide the search functionality on the website and discussion list archives. Furthermore, we use Google Analytics to collect website usage statistics.

Ftp

We use the DCCN ftp server to distribute the software releases and tutorial data.

Central storage

At the DCCN we have a central storage system (i.e. a large and shared network drive) on which an up-to-date copy of the software is maintained. Also the test data used for development and regression testing with the dashboard is on central storage.

Dashboard

We have a set of MATLAB and Bash scripts for regression testing. This allows to do semi-automatic runs of all the test scripts on the DCCN compute cluster. We refer to this as the test dashboard. The code is hosted on GitHub and the MATLAB interface is implemented in ft_test, which you can find in the utilities folder.

Mixpanel

We are experimenting with MixPanel for software usage tracking. More details are here.

Slack

We are experimenting with Slack as a messaging tool for the development team.

Bugzilla - obsolete

In the past we used Bugzilla as an “issue tracker”. This allows to maintain and distribute to-do lists and supports the follow up communication with users that report problems or suggestions. Our bugzilla server is hosted at the DCCN and more details can be found here.

Dokuwiki - obsolete

In the past we used dokuwiki as the CMS system for our website.

SVN - obsolete

We used to do the development with Subversion (also known as SVN). As of February 2016 we have moved all development over to git and github.

Google Code - obsolete

We used to maintain a copy of the SVN repository with the software on Google Code but in 2015 Google stopped support for it. Right now there is only a link to the FieldTrip website.

Sourceforge - obsolete

We used to maintain a copy of the SVN repository with the software on SourceForge but are now not actively using it any more.