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.
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.
We use this for a number of email discussion lists. It is hosted by C&CZ at http://mailman.science.ru.nl. Upon an email to the main FieldTrip mailing list, a tweet is send to http://twitter.com/fieldtriptoolbx. The Google search on the website also searches the email list archives.
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 often used in news messages on the start page.
We use http://twitter.com/fieldtriptoolbx to notify people about events. Commits of new code are automatically tweeted.
We use Bitly to automatically create short URLs that are included in the tweets.
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/webhook.
A copy of the git repository of the FieldTrip software is stored on BitBucket, although the primary site is on GitHub.
A copy of the git repository of the FieldTrip software is stored on Gitlab, although the primary site is on GitHub.
We use Bugzilla as an “issue tracker”. It allows us to maintain and distribute to-do lists and supports the follow up communication with users that report problems or suggestions. It is hosted at the DCCN, more details can be found here
We use Google to provide the search functionality on the website and discussion list archives. Furthermore, we use Google Analytics to collect usage statistics.
We use the DCCN ftp server to distribute a daily updated copy of the software and to distribute the tutorial data.
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.
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 quality dashboard. The code is hosted on github and the MATLAB interface is implemented in ft_test, which you can find in the utilities folder.
We are experimenting with MixPanel to track the software usage. More details are here.
We are experimenting with Slack as a messaging tool for the development team.
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.