jspsych 6.3.1 → 7.1.2

package/code-of-conduct.md

@@ -1,56 +0,0 @@
-# jsPsych Code of Conduct
-
-## Community
-jsPsych aims to provide a productive, helpful, and agile community that:
-* Welcomes new users and ideas
-* Seeks to improve the jsPsych library for all users
-* Works toward best scientific practices
-* Ensures that jsPsych remains as accessible as possible
-
-We hope that this community will encourage collaboration between users/groups with different needs, interests, and skills.
-
-jsPsych was created with the goal of making web-based behavioral experiments as easy as possible for those who do not have a background in web development or any other kind of computer programming. Thus, novice users are an essential part of this community. The involvement of beginner programmers is not only welcome, but critical for the continued success of the project. 
-
-Similarly, a core aim of the jsPsych project is to make web-based behavioral experiments accessible to anyone who wishes to utilize them. We can better achieve this goal with diverse voices guiding the project, and we value participation from those who bring different perspectives to our community. We actively encourage participation from those who come from historically underrepresented groups in software development and STEM.
-
-### Core principles
-* **Be friendly and patient**: Remember that you might not be communicating in someone else's primary spoken or programming language, and that we don’t all have the same background knowledge and experience. 
-* **Be helpful**: Offer constructive feedback on others’ ideas and code.
-* **Be collaborative**: Collaboration improves the efficiency and quality of our work. We aim to understand the needs of other users, and to work transparently with others to coordinate our efforts. 
-* **Be considerate and respectful**: There is no excuse for disrespectful behavior. When making comments in public spaces, we should consider the potential impact on the whole community. For instance, jokes/teasing may seem harmless among users who are familiar with one another, but this can be intimidating and off-putting for other community members.
-* **Ask for help and seek feedback**: We’re all learning, and no one is expected to be perfect. Asking questions and seeking feedback early on can help us work efficiently and avoid bigger problems in the future. 
-* **Take responsibility for your actions**: We all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to improve our behavior.
-* **Value decisiveness, clarity, and consensus**: We hope that jsPsych contributors can resolve disagreements constructively, using clear rationale for their perspective, and with humility. When they cannot, the project leader can offer clarity and direction.
-
-### Scope
-The community’s core principles apply to all private and public spaces where the jsPsych project is officially managed, promoted, or discussed. Examples include all of the jsPsych-related GitHub repos (issues, commit messages, pull requests, etc.), the jsPsych Google Group, and anyone acting as a representative of the project, whether in person or online, including via social media and email. We expect this Code of Conduct to be honoured by everyone in the jsPsych community. 
-
-## Leadership
-We encourage all participants in the jsPsych community to feel empowered to lead, to take action, and to experiment when they feel that innovation could improve the project. There is no need to wait for delegation or permission - leadership can be exercised by anyone simply by taking action.
-
-Although we strive to make jsPsych as open and collaborative as possible, it’s important to have a project leader in order to ensure that jsPsych remains (1) as accessible as possible for all users, (2) stable and reliable, (3) easy to maintain, (4) internally consistent, etc.
-
-Such leadership occasionally requires decisions that are in the best interest of the project but may not be understood by or beneficial to everyone. These decisions are important because they keep the project on track, and enable it to move forward faster than if we required complete consensus. Any major decisions taken by the project leader should be mindful of the challenges they may present for others. We expect the project leader to communicate major decisions/changes early on, and to provide their reasoning.
-
-### Contributions
-We invite anyone to contribute to any aspect of the project. You can find more information about contributing here: https://www.jspsych.org/about/contributing/
-
-Because changes to the jsPsych library can have a huge potential for impact on all users, any proposed changes to the library have to be considered very carefully. For this reason, it is always a good idea to check with the project leader about whether your proposed contribution would likely be merged into the jsPsych library. Keep in mind that, even if your work isn’t suitable for merging into the jsPsych library, you can still use it in your own projects and share it publicly with others, e.g. via a separate GitHub repository.
-
-Contributors are acknowledged in the contributors.md file in the jsPsych GitHub repo, and in the notes for each release. If you feel that your contribution has been overlooked, please contact Josh de Leeuw (josh.deleeuw@gmail.com). We also encourage opening a pull request to modify the contributors.md file.
-
-### Conflicts of Interest
-We expect jsPsych users and developers to be aware when they are conflicted due to employment or other projects they are involved in, and to abstain or delegate decisions that may be seen to be self-interested. We expect that everyone who participates in the jsPsych community does so with the goal of improving the library for all of its users.
-
-## Reporting Code of Conduct Issues
-In the event that a Code of Conduct issue cannot be resolved among users, please feel free to report your concerns to Josh de Leeuw (josh.deleeuw@gmail.com). If Josh de Leeuw is involved in the issue, you can report it to Becky Gilbert instead (beckyannegilbert@gmail.com). In your report, please include as much information as possible about what occurred, including any relevant links/attachments.
-
-All reports will be reviewed by a multi-person team and will result in a response that is deemed necessary and appropriate to the circumstances. Where additional perspectives are needed, the team may seek insight from others with relevant expertise or experience. The confidentiality of the person reporting the incident will be kept at all times. Involved parties are never part of the review team. Anyone asked to stop unacceptable behavior is expected to comply immediately. If an individual engages in unacceptable behavior, the review team may take any action they deem appropriate, including a permanent ban from the community.
-
-This code is not exhaustive or complete. It serves to capture our common understanding of a welcoming, productive, and collaborative environment. We expect the code to be followed in spirit as much as in the letter.
-
-## References
-This document was based on, or inspired by, the following Codes of Conduct:
-* Ubuntu https://ubuntu.com/community/code-of-conduct
-* Microsoft https://opensource.microsoft.com/codeofconduct/
-* Contributor Covenant https://www.contributor-covenant.org/version/1/4/code-of-conduct

package/contributors.md

@@ -1,61 +0,0 @@
-The following people have contributed to the development of jsPsych by writing code, documentation, and/or suggesting improvements (in alphabetical order):
-* alisdt - https://github.com/alisdt
-* Antonia - https://github.com/Ahoidal
-* aucuparia - https://github.com/aucuparia
-* Xiaolu Bai - https://github.com/lbai001
-* bjoluc - https://github.com/bjoluc
-* Christian Brickhouse - https://github.com/chrisbrickhouse
-* Teon L Brooks - https://github.com/teonbrooks
-* Eamon Caddigan - https://github.com/eamoncaddigan
-* Jason Carpenter
-* Steve Chao - https://github.com/stchao
-* Zhanwen "Phil" Chen - https://github.com/zhanwenchen
-* cthorey - https://github.com/cthorey
-* Guy Davidson - https://github.com/guydav
-* Kristin Diep - https://github.com/kristiyip
-* Ari Dyckovsky - https://github.com/aridyckovsky
-* Etienne Gaudrain - https://github.com/egaudrain
-* Jon Gauthier - https://github.com/hans
-* Robert Gibboni - https://github.com/r-b-g-b
-* Becky Gilbert - https://github.com/becky-gilbert
-* Mark Gorenstein - https://github.com/mgorenstein
-* Rui Han - https://github.com/hrcn
-* Andy Heusser - https://github.com/andrewheusser
-* Angus Hughes - https://github.com/awhug
-* Gustavo Juantorena - https://github.com/GEJ1
-* Chris Jungerius - https://github.com/cjungerius
-* George Kachergis - https://github.com/kachergis
-* Yul Kang - https://github.com/yulkang
-* Spencer King - https://github.com/spencerking
-* Jana Klaus - https://github.com/janakl4us
-* Arnold Kochari - https://github.com/akochari
-* Peter Jes Kohler - https://github.com/pjkohler 
-* kupiqu - https://github.com/kupiqu
-* Daiichiro Kuroki - https://github.com/kurokida
-* Jonas Lambers
-* madebyafox - https://github.com/madebyafox
-* Shane Martin - https://github.com/shamrt
-* Vijay Marupudi - https://github.com/vijaymarupudi
-* Adrian Oesch - https://github.com/adrianoesch
-* Benjamin Ooghe-Tabanou - https://github.com/boogheta
-* Dillon Plunkett - https://github.com/dillonplunkett
-* Junyan Qi - https://github.com/GavinQ1
-* Sivananda Rajananda - https://github.com/vrsivananda
-* Dan Rivas - https://github.com/rivasd
-* Werner Sævland - https://github.com/wernersa
-* Marian Sauter - https://github.com/mariansauter
-* Ellen Shapiro - https://github.com/designatednerd
-* Jan Simson - https://github.com/jansim
-* Hannah Small - https://github.com/hesmall
-* sprengholz - https://github.com/sprengholz
-* Dominik Strohmeier - https://github.com/onkeltom
-* Nabeel Sulieman - https://github.com/nabsul
-* Hitoshi Tominaga - https://github.com/tbrotherm
-* Tim Vergenz - https://github.com/vergenzt
-* Matteo Visconti di Oleggio Castello - https://github.com/mvdoc
-* Ilya Vorontsov - https://github.com/VorontsovIE
-* Wolfgang Walther - https://github.com/wolfgangwalther
-* Erik Weitnauer - https://github.com/eweitnauer
-* Rob Wilkinson - https://github.com/RobAWilkinson
-* Andy Woods - https://github.com/andytwoods
-* Reto Wyss - https://github.com/retowyss

package/docs/CNAME

@@ -1 +0,0 @@
-www.jspsych.org

package/docs/about/about.md

@@ -1,18 +0,0 @@
-# About jsPsych
-
-jsPsych was created by [Josh de Leeuw](http://www.twitter.com/joshdeleeuw). There have been [many other contributors](https://github.com/jodeleeuw/jsPsych/blob/master/contributors.md) to the library; thanks to all of them!
-
-### Citation
-
-If you use jsPsych for academic work please cite the following paper.
-
-de Leeuw, J. R. (2015). jsPsych: A JavaScript library for creating behavioral experiments in a web browser. _Behavior Research Methods_, _47_(1), 1-12. doi:10.3758/s13428-014-0458-y.
-
-### Response times
-
-Wondering if jsPsych can be used for research that depends on accurate response time measurement? For most purposes, the answer is yes. Response time measurements in jsPsych (and JavaScript in general) are comparable to those taken in standard lab software like Psychophysics Toolbox and E-Prime. Response times measured in JavaScript tend to be a little bit longer (10-40ms), but have similar variance. See the following references for extensive work on this topic.
-
-* [de Leeuw, J. R., & Motz, B. A. (2016). Psychophysics in a Web browser? Comparing response times collected with JavaScript and Psychophysics Toolbox in a visual search task. *Behavior Research Methods*, *48*(1), 1-12.](http://link.springer.com/article/10.3758%2Fs13428-015-0567-2)
-* [Hilbig, B. E. (2016). Reaction time effects in lab- versus web-based research: Experimental evidence. *Behavior Research Methods*, *48*(4), 1718-1724.](http://dx.doi.org/10.3758/s13428-015-0678-9)
-* [Pinet, S., Zielinski, C., Mathôt, S. et al. (in press). Measuring sequences of keystrokes with jsPsych: Reliability of response times and interkeystroke intervals.  *Behavior Research Methods*.](http://link.springer.com/article/10.3758/s13428-016-0776-3)
-* [Reimers, S., & Stewart, N. (2015). Presentation and response time accuracy in Adobe Flash and HTML5/JavaScript Web experiments. *Behavior Research Methods*, *47*(2), 309-327.](http://link.springer.com/article/10.3758%2Fs13428-014-0471-1)

package/docs/about/contributing.md

@@ -1,43 +0,0 @@
-# Contributing to jsPsych
-
-Contributions to jsPsych are welcome! All of the code is managed through the GitHub repository.
-
-## Steps for modifying the code
-
-#### Discuss the proposed change
-
-If you have a specific modification in mind -- for instance, a new feature or bug fix -- please open a [new issue via GitHub](https://github.com/jspsych/jsPsych/issues/new). Describe the proposed change and what functionality it adds to the library and/or what problem it solves. If you are interested in adding a new plugin to the library, it helps if you post an example of the plugin in use and describe the different use cases of the plugin (for more guidance, see the "Writing new plugins" section below).
-
-If you are thinking about proposing a change but not at the point where you have a specific modification to the code base in mind, then it might be helpful to discuss the issue first on [GitHub Discussions](https://github.com/jspsych/jsPsych/discussions). Discussion posts can be useful for sharing code and getting feedback before requesting a change to the library.
-
-#### Fork the library and modify the code
-
-To make changes to the code, you should fork the jsPsych library via GitHub and make modifications on your fork. You may find it useful to make modifications on branches, so that you can keep your proposed changes separate from any other unrelated changes you might want to make on your fork.
-
-#### Submit a pull request
-
-Once your modification is complete, submit a pull request to merge your changes into the `master` branch of the main repository. Pull requests will be reviewed by the project team.
-
-## Writing new plugins
-
-New plugins are welcome additions to the library. Plugins can be distributed independently of the main library or added to the GitHub repository via a pull request, following the process described above. If you want to add your plugin to the main library then there are a few guidelines to follow.
-
-#### Make the plugin as general as possible
-
-Plugins are most useful when they are flexible. Avoid fixing the value of parameters that could be variables. This is especially important for any text that displays on the screen in order to facilitate use in multiple languages.
-
-#### Use the jsPsych.pluginAPI module when appropriate
-
-The [pluginAPI module](../core_library/jspsych-pluginAPI.md) contains functions relevant to plugin development. Avoid duplicating the functions defined within the library in your plugin, and instead use the pluginAPI whenever possible. If you have a suggestion for improving pluginAPI methods, then go ahead and submit a pull request to modify it directly.
-
-#### Document your plugin
-
-When submitting a pull request to add your plugin, make sure to include a documentation page in the same style as the other docs pages. Documentation files exist in the `docs` directory.
-
-#### Include an example file
-
-Write a short example HTML file to include in the `examples` directory. This should demonstrate the basic use cases of the plugin as clearly as possible.
-
-#### Include a testing file
-
-Automated code testing for jsPsych is implemented with [Jest](https://facebook.github.io/jest/). To run the tests, install Node and npm. Run `npm install` in the root jsPsych directory. Then run `npm test`. Plugins should have a testing file that validates the behavior of all the plugin parameters. See the `/tests/plugins` directory for examples.

package/docs/about/license.md

@@ -1,25 +0,0 @@
-# License
-
-jsPsych is licensed under the MIT license.
-
->The MIT License (MIT)
->
->Copyright (c) 2019 Joshua R. de Leeuw
->
->Permission is hereby granted, free of charge, to any person obtaining a copy
->of this software and associated documentation files (the "Software"), to deal
->in the Software without restriction, including without limitation the rights
->to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
->copies of the Software, and to permit persons to whom the Software is
->furnished to do so, subject to the following conditions:
->
->The above copyright notice and this permission notice shall be included in all
->copies or substantial portions of the Software.
->
->THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
->IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
->FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
->AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
->LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
->OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
->SOFTWARE.

package/docs/about/support.md

@@ -1,7 +0,0 @@
-# Support
-
-For questions about jsPsych the preferred method of support is via [GitHub Discussions](https://github.com/jspsych/jsPsych/discussions). Questions are most likely to be answered when they include a reproducible example of the problem. If you can make your code available online and link to the experiment, that will make the question easier to answer.
-
-If you have identified a problem with jsPsych, such as a bug in the code or an error in the documentation, please [open a new issue](https://github.com/jspsych/jsPsych/issues/new) on the GitHub site. And if you have a suggestion for fixing the problem, feel free to propose a modification by following the steps in the [Contribuitng to jsPsych](contributing.md) page.
-
-Inquiries for paid consultation to develop experiments using jsPsych or to create new custom jsPsych features can be sent to [josh.deleeuw@gmail.com](mailto:josh.deleeuw@gmail.com).