Changes between Version 2 and Version 3 of ProjectOpenSesamePage


Ignore:
Timestamp:
09/20/17 16:03:28 (7 years ago)
Author:
Chichakovska Katerina
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectOpenSesamePage

    v2 v3  
    3838
    3939'''Community'''
     40Python community
    4041
    4142'''Leadership'''
     43Sebastiaan Mathôt
    4244
    4345'''Forking'''
     46You can create your own fork of the central repository. First go to github, create an account and make a fork of the OpenSesame 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.
    4447
    4548'''Communication'''
     49It has forum on which you can communicate with everyone. For the forum you must create a new account or sign in with your CogSci, Facebook, Google, or Twitter account. (http://forum.cogsci.nl/index.php?p=/discussions)
    4650
    4751'''Roadmaps'''
    4852
    4953'''Releases'''
     541. Mathôt, S., Schreij, D., & Theeuwes, J. (2012). OpenSesame: An open-source, graphical experiment builder for the social sciences. Behavior Research Methods, 44(2), 314-324. doi:10.3758/s13428-011-0168-7
     55And if you make extensive use of modules such as SciPy/ NumPy, PsychoPy, or Expyriment, please also cite the respective authors which you can see on this site: http://osdoc.cogsci.nl/3.1/publications/
    5056
    5157'''Repositories'''
     58The 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.
    5259
    5360'''Packaging'''
    5461
    5562'''Upstream/downstream'''
     63Only a couple of people have direct write-access to the psychopy 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.
    5664
    5765'''Version Control'''
     66OpenSesame 3.1.9 Jazzy James is the ninth maintenance released on August 19, 2017. It contains bug fixes and minor improvements.
    5867
    5968'''Trackers'''
     69Trackers You can track the changes on the folowing link:http://osdoc.cogsci.nl/3.1/notes/notes/
    6070
    6171'''''Project Evaluation'''''
     72From the begining OpenSesame is continually updated each year, containing new features and bug fixes.
    6273
    6374
     
    6778'''''Fieldtrips'''''
    6879
    69 ----
    7080
    7181'''Github:'''
     821. https://github.com/smathot/OpenSesame
    7283
    7384'''Openhub:'''
     851. https://openhub.net/p/opensesame-cogsci
    7486
    7587'''Source Forge:'''
     881. https://sourceforge.net/directory/os:windows/?q=OpenSesame
    7689
    7790
     
    8194
    8295'''Licensing'''
     96GNU General Public License 3
     97(https://www.gnu.org/licenses/gpl.txt)
    8398
    8499'''Language'''
     100Python, XML
    85101
    86102'''Activity'''
     103Active
    87104
    88105'''Number of contributors'''
     106OpenSesame is mainly developed by a loose collection of individuals. But anyone is welcome to contribute!
     1071. Sebastiaan Mathôt - Project manager and lead developer
     1082. Daniel Schreij - Developer
     1093. Lotje van der Linden - Documentation and support
     1104. Edwin Dalmaijer - Developer
     1115. Eduard Ort - Documentation and support
     1126. Joshua Snell - Documentation and support
    89113
    90114'''Size'''
     115For different versions see the size on this page: https://github.com/smathot/OpenSesame/releases
    91116
    92117'''Issue tracker'''
     118It has forum on which you can ask your question.
    93119
    94120'''New contributor'''
     121On the GitHub provides a straightforward way for collaborating on a project.
     122More information how to contrabute you can see on the folowing page: http://osdoc.cogsci.nl/3.1/dev/howtocontribute/
    95123
    96124'''Community norms'''
     125You can create a fork of the central OpenSesame 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).
    97126
    98127'''User base'''
     128It has its own strong user base.