One of the best ways that you can support the JASP project is by citing it. Citations are an important measure of how widely software is used, and an important indicator to funding bodies of JASP’s relevance.

To cite JASP in publications use:

JASP Team (2017). JASP (Version 0.8.2)[Computer software].

And the BibTeX entry :

@MISC{JASP2017,
AUTHOR = {{JASP Team}, {The}},
TITLE = {{JASP (Version 0.8.2)[Computer software]}},
YEAR = {2017},
URL = {https://jasp-stats.org/}
}

In recognition of Bayesian pioneer Sir Harold Jeffreys, JASP stands for Jeffreys’s Amazing Statistics Program.

Yes — More importantly, it is released under an Open Source license, which means that even if we turn evil, we will not be able to take JASP away or prevent others from contributing to it, working on it, or distributing it freely. This excerpt from our license sums it up nicely:

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program — to make sure it remains free software for all its users.

JASP is currently supported by long-term, multi-million euro grants that help fund a team of motivated software developers, academics, and students. Our two main software developers and several core team members have tenured positions. The Psychological Methods Group at the University of Amsterdam is dedicated to long-term support for JASP. Finally, the JASP code is open-source and will always remain freely available online. In sum, JASP is here to stay.

The JASP application is written in C++, using the Qt toolkit. The analyses themselves are written in either R or C++. The display layer (where the tables are rendered) is written in javascript, and is built on top of jQuery UI and webkit.

Not without considerable effort. When JASP was first developed, our focus was on producing a GUI that would retain the desirable properties of syntax (such as reproducibility) without requiring or producing syntax itself. We believe we did a decent job on the GUI, but we recognize that some users still like easy access to the R code. We hope to add this functionality in a future version.