Changes between Version 32 and Version 33 of ProjectPyGazePage
- Timestamp:
- 03/19/18 18:42:08 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectPyGazePage
v32 v33 104 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:** 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/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 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:** If you want to be a contributor to PyGaze one way is through theGitHub page, where you can make your own fork and pull request and wait for an approval.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:** 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.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 114 **User base:** Their user base are the developers and the contributors: http://www.pygaze.org/contributors/