== **Tatool** == 

**Description:** 

Tatool Web is an open-source software for running online and offline computer-based experiments. It has been developed by Claudia von Bastian (scientist) and Andre Locher (developer).
Tatool is conceptualized according to the requirements for running psychological experimental studies. In its original version, Tatool was developed as a Java-based open-source framework. But the process of learning such a complex programming language as Java is an obstacle for the majority of researchers. However, the vision of Tatool is that computer-based experiments should be an easy task to do - for more experienced researchers but also for students and research assistants.
The main goal of the new Tatool was therefore to make it easier. It is based on !JavaScript and HTML 5, both of which are very widely used technologies that are much easier and faster to learn.
Tatool provides options for running experiments both for programming novices and old hands. With the Experiment Editor, you can create an experiment quickly and easily without writing a single line of code. Or, you can dive deeper and develop completely new tasks in !JavaScript. There's no limit, as Tatool is open-source and hence offers the full range of flexibility.


**URL:** ​

[1] https://github.com/tatool/tatool-web 

[2] http://www.tatool-web.com/#/ 


== **Project Anatomy**==


**Community**

Tatool support the scientific community with an open-source

**Leadership**

Claudia von Bastian (scientist), Andre Locher (developer)

**Forking**

You can create your own fork of the central repository. First go to github, create an account and make a fork of the tatool repository. You can change your fork in any way you choose without it affecting the central project. You can also share your fork with others, including the central project.

**Communication**

You can ask a question on a forum: http://www.tatool.ch/forum/index.php or you  can communicate with them: https://www.google.com/recaptcha/mailhide/d?k=01QxKZo9rpozcn32fS6INR3Q==&c=bhVN7UDNOC6-tTzg17qtMw== 

**Roadmaps**

N/A

**Releases**

1. von Bastian, C. C., Locher, A., & Ruflin, M. (2013). Tatool: A Java-Based Open-Source Programming Framework for Psychological Studies. Behavior Research Methods, 45(1), 108-115. doi: 10.3758/s13428-012-0224-y

**Repositories**

The use of git allows people to contribute changes that can easily be incorporated back into the project, while maintaining order and consistency in the code. All changes should be tracked and reversible.

**Packaging**

N/A

**Upstream/downstream**

Only a couple of people have direct write-access to the tatool repository, but you can get your changes included in upstream by pushing your changes back to your github fork and then submitting a pull request.

**Version Control**

The last version was on September 17, 2016.

**Trackers**

You can track the changes on the folowing link: https://github.com/tatool/tatool-web/releases 

**Project Evaluation**

From the begining tatool is continually updated each year, containing new features and bug fixes.


== **Fieldtrips**== 


**Github:**

[1] https://github.com/tatool/tatool-web 

**Openhub:**

N/A

**Source Forge:**

N/A

== **Evaluation** ==

**Licensing**

GNU GPL v3.0

**Language**

HTML5, CSS, !JavaScript and node.js

**Activity**

Active

**Number of contributors**

TBD

For more informations you can see on the folowing page: http://www.tatool-web.com/#/doc/community-contribute.html

**Size**

For different versions see the size on this page: https://github.com/tatool/tatool-web/releases

**Issue tracker**

It has forum on which you can ask your question: http://www.tatool.ch/forum/index.php

**New contributor**

If you like Tatool and want to support its cause, there are multiple options to do so: 1.Code-Sharing; 2.Donations;

**Community norms**

You can create a fork of the central tatool repository. You can also create a local clone of that fork: for small changes(make the changes directly in the master branch, push back to your fork, submit a pull request to the central repository) and for substantial changes (create a branch, when finished run unit tests, when the unit tests pass merge changes back into the master branch, submit a pull request to the central repository).

**User base**

It has its own strong user base.