== **PEBL: The Psychology Experiment Building Language** == 

**Description:** 

PEBL (Psychology Experiment Building Language) is a new programming language developed especially for building psychology experiments involving human participants interacting with a computer. It is free psychology software for creating experiments which allows you to design your own experiments or use ready-made ones and lets you exchange experiments.  
Development and design of PEBL began in 2002. An initial limited release of PEBL 0.1 was made in 2003, with the first public release to the Sourceforge.net servers in January 2004. 
PEBL is designed to be easily used on multiple computing platforms. Its current implementation uses the SDL as its implementation platform, which is also a cross-platform library that compiles natively under Win32, Linux, and Macintosh Operating Systems.
PEBL is programmed primarily in C++, but also uses flex and bison to handle parsing.
PEBL is designed to be an open system, and is licensedunder the GNU Public License 2.0. This allows users to freelyinstall the software on as many computers as they wish, to sharetheir experiments with others without worrying about licenses,to distribute working experiments to other researchers or remote subjects without requiring special hardware locks, and to examineand improve the system itself when it does not suit one’s needs.


**URL:** ​

[1] http://pebl.sourceforge.net/ 

[2] http://obereed.net/docs/MuellerSCIP2004.pdf 

[3] https://sourceforge.net/projects/pebl/ 

[4] https://www.researchgate.net/publication/258853238_The_psychology_experiment_building_language_PEBL_and_PEBL_test_battery 

[5] http://www.superiorideas.org/projects/open-source-psychology-software 

== **Project Anatomy**==


**Community**

Python community 

**Leadership**

Dr. Mueller 

**Forking**

You can create your own fork of the central repository. First go to github, create an account and make a fork of the PEBL 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 contact the PEBL Project at: pebl-list@lists.sourceforge.net.

**Roadmaps**

N/A

**Releases**

Mueller, S. T. (2013). The Psychology Experiment !BuildingLanguage (Version 0.13) [Software]. Available from http://pebl.sourceforge.net 

**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 PEBL 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 update was on Julu 2017.

**Trackers**

You can track the changes on the folowing link: http://pebl.sourceforge.net/download.html

**Project Evaluation**

There are not so much new versoions of PEBL. Development and design of PEBL began in 2002. An initiallimited release of PEBL 0.1 was made in 2003, and the last one was made in 2017 as 2.0.


== **Fieldtrips**== 


**Github:**

[1] https://github.com/abhik/pebl 

**Openhub:**

[1] https://openhub.net/p/pebl 

**Source Forge:**

[1] https://sourceforge.net/projects/pebl/ 

== **Evaluation** ==

**Licensing**

GNU Public License 2.0

**Language**

C++, PHP, Python 

**Activity**

Active

**Number of contributors**

There are not much contributors. Abhik Shah is one of the contributors.

**Size**

N/A

**Issue tracker**

It has forum on which you can ask your question.

**New contributor**

N/A

**Community norms**

You can create a fork of the central PEBL 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.