Changes between Version 4 and Version 5 of ProjectEhcaPage
- Timestamp:
- 03/22/18 15:41:12 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectEhcaPage
v4 v5 24 24 **Roadmaps**: 25 25 26 27 ''Original goal:'' 28 29 - 30 31 ''Future goals:'' 32 33 Short term: 34 - better variable management and getting rid of some annoying bugs 35 - an analysis suite to complement the existing experimental library 36 37 Long term: 38 - incorporate support for more eye trackers and support for even more obscure peripherals 39 - support for electroencephalography 40 41 Source: Interview with lead developer: https://opensource.com/life/15/12/pygaze-open-source-eye-tracking-toolkit 26 - N/A 42 27 43 28 **Releases**: … … 47 32 **Repositories**: 48 33 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/PyGazeAnalyser34 The main repository of !EHCA is: https://github.com/schw4b/ehca , where you can download the source code, clone it to desktop, or even make your own fork. 35 There is also a repository for !EHCA available at: svn checkout https://svn.code.sf.net/p/ehca/code/trunk ehca-code 51 36 52 37 **Packaging**: 53 38 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/39 This software is not organized into packages. 55 40 56 41 **Upstream/downstream**: 57 42 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.43 It is open for contributing for upstream, after of course your pull request is revised and approved. 59 44 60 45 **Version Control**: 61 46 62 version 0.6.0 (07-09-2017) - Latest version control47 (2012-05-29) - The inital date of release. There has no other version than that. 63 48 64 49 **Trackers**: 65 50 66 You can see commits and verified changes at this link: https://github.com/ esdalmaijer/PyGaze/commits/master51 You can see commits and verified changes at this link: https://github.com/schw4b/ehca/commits/master 67 52 68 53 == Project Evaluation == … … 71 56 === Fieldtrips === 72 57 73 Github: https://github.com/ esdalmaijer/PyGaze58 Github: https://github.com/schw4b/ehca 74 59 75 Openhub: / (! PyGazeis not listed here)60 Openhub: / (!EHCA is not listed here) 76 61 77 Source Forge: / (!PyGaze is not listed here)62 Source Forge: https://sourceforge.net/projects/ehca/ 78 63 79 64 === Evaluation === 80 65 81 **Licensing:** GNU Public License (version3)66 **Licensing:** GNU General Public License version 3.0 (GPLv3) 82 67 83 **Language:** Python68 **Language:** MATLAB 84 69 85 70 **Activity:** Active 86 71 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/72 **Number of contributors:** There is only one contibutor: https://github.com/schw4b/ehca/graphs/contributors 88 73 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/74 **Size:** There is no known information about the size. 90 75 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/issues76 **Issue tracker:** There is no issue tracker. 92 77 93 **New contributor:** If you want to be a contributor to ! PyGazeone way is through the !GitHub page, where you can make your own fork and pull request and wait for an approval.78 **New contributor:** If you want to be a contributor to !EHCA one way is through the !GitHub page, where you can make your own fork and pull request and wait for an approval. 94 79 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.80 **Community norms:** You can report an issue through the issue page on their GitHub page , help to fix it by forking in the !GitHub repository and commit fixes. The only condition to use this software is that you cite the authors paper. 96 81 97 **User base:** Their user base are the developers and the contributors: http://www.pygaze.org/contributors/82 **User base:** Their user base is the developer. 98 83