Changes between Version 5 and Version 6 of ProjectGazeBoard
- Timestamp:
- 05/12/18 16:32:22 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectGazeBoard
v5 v6 41 41 **Releases**: 42 42 43 1. Behavior Research Methods, December 2014, Volume 46, Issue 4, pp 913–921 | Cite as !PyGaze: An open-source, cross-platform toolbox for minimal-effort programming of eyetracking experiments - https://link.springer.com/article/10.3758/s13428-013-0422-2 44 2. Edwin S. Dalmaijer, Sebastiaan Mathôt, Stefan Van der Stigchel, 2013 - http://www.pygaze.org/resources/downloads/Dalmaijer_Mathot_Stigchel_2013_PyGaze_manuscript.pdf 45 3. Dalmaijer, E.S., Mathôt, S., & Van der Stigchel, S. (2013). !PyGaze: an open-source, cross-platform toolbox for minimal-effort programming of eye tracking experiments. Behaviour Research Methods. doi:10.3758/s13428-013-0422-2 43 N/A 46 44 47 45 **Repositories**: 48 46 49 The main repository of !PyGaze is: https://github.com/esdalmaijer/PyGaze , where you can download the source code, clone it to desktop, or even make your own fork. 50 There is also a repository for !PyGazeAnalizer available at: https://github.com/esdalmaijer/PyGazeAnalyser 47 The main repository of !GazeBoard is: https://sourceforge.net/p/gazeboard/code/ref/master/ , where you can make your own fork. 51 48 52 49 **Packaging**: 53 50 54 Different packages for ! PyGaze, including Windows, Linux and Mac OS X packages can be found at the downloads page of !PyGaze: http://www.pygaze.org/downloads/51 Different packages for !GazeBoard can be found at the downloads page of !GazeBoard at: https://sourceforge.net/projects/gazeboard/files/ 55 52 56 53 **Upstream/downstream**: 57 54 58 So far, from 2013 when it was originaly published, !PyGaze has 12 contibutors, and it is open for contributing for upstream, after of course your pull request is revised and approved.55 There is no known information for contributing. 59 56 60 57 **Version Control**: 61 58 62 version 0.6.0 (07-09-2017) - Latest version control59 version 1.2 Beta (2016-12-11) - Latest version control 63 60 64 61 **Trackers**: 65 62 66 You can see commits and verified changes at this link: https://github.com/esdalmaijer/PyGaze/commits/master63 There aren't available trackers. 67 64 68 65 == Project Evaluation == … … 71 68 === Fieldtrips === 72 69 73 Github: https://github.com/esdalmaijer/PyGaze70 Github: / (!GazeBoard is not listed here) 74 71 75 Openhub: / (! PyGazeis not listed here)72 Openhub: / (!GazeBoard is not listed here) 76 73 77 Source Forge: / (!PyGaze is not listed here)74 Source Forge: https://sourceforge.net/projects/gazeboard/ 78 75 79 76 === Evaluation === 80 77 81 **Licensing:** GNU Public License (version 3)78 **Licensing:** N/A (Other license) 82 79 83 **Language:** Python80 **Language:** N/A 84 81 85 82 **Activity:** Active 86 83 87 **Number of contributors:** There are two developers and a couple of official contributors. They are listed on this page: http://www.pygaze.org/contributors/84 **Number of contributors:** N/A 88 85 89 **Size:** There aren't any official releases on !GitHub, you can find out the size of the packages from the download page after you download them. http://www.pygaze.org/downloads/86 **Size:** Information about the size of the packages can be seen in the downloads page: https://sourceforge.net/projects/gazeboard/files/?source=navbar 90 87 91 **Issue tracker:** There is a forum where you can write about an issue: http://forum.cogsci.nl/index.php?p=/categories/pygaze and there is the issue tracker on !GitHub: https://github.com/esdalmaijer/PyGaze/issues88 **Issue tracker:** There is a forum for general discussion where you can write about an issue: https://sourceforge.net/p/gazeboard/discussion/?source=navbar and this is the closest to issue tracker they have. 92 89 93 **New contributor:** If you want to be a contributor to !PyGaze one way is through the !GitHub page, where you can make your own fork and pull request and wait for an approval.90 **New contributor:** There aren't any information for new contributors. 94 91 95 **Community norms:** You can report an issue through the forum page , help to fix it by forking in the !GitHub repository and commit fixes and if you prefer to work via different channels (contact form, or via carrier pigeon), that’s fine too.92 **Community norms:** N/A 96 93 97 **User base:** Their user base are the developers and the contributors: http://www.pygaze.org/contributors/94 **User base:** Their user base is the developer. 98 95 99 96 [ProjectReviewPyGaze ...Review]