Changes between Version 30 and Version 31 of ProjectPyGazePage
- Timestamp:
- 03/19/18 18:38:43 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectPyGazePage
v30 v31 88 88 === Fieldtrips === 89 89 90 Github: 90 Github: https://github.com/esdalmaijer/PyGaze 91 91 92 Openhub: 92 Openhub: / (PyGaze is not listed here) 93 93 94 Source Forge: 94 Source Forge: / (PyGaze is not listed here) 95 95 96 96 === Evaluation === 97 97 98 Licensing 98 Licensing: GNU Public License (version 3) 99 99 100 Language 100 Language: Python 101 101 102 Activity 102 Activity: Active 103 103 104 Number of contributors 104 Number of contributors: There are two developers and a couple of official contributors. They are listed on this page: http://www.pygaze.org/contributors/ 105 105 106 Size 106 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/ 107 107 108 Issue tracker 108 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/issues 109 109 110 New contributor 110 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. 111 111 112 Community norms 112 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. 113 113 114 User base 114 User base: Their user base are the contributors: http://www.pygaze.org/contributors/ 115 115