Changes between Version 31 and Version 32 of ProjectPyGazePage


Ignore:
Timestamp:
03/19/18 18:41:03 (7 years ago)
Author:
Monika Rizova
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProjectPyGazePage

    v31 v32  
    9090Github: https://github.com/esdalmaijer/PyGaze
    9191
    92 Openhub: / (PyGaze is not listed here)
     92Openhub: / (!PyGaze is not listed here)
    9393
    94 Source Forge: / (PyGaze is not listed here)
     94Source Forge: / (!PyGaze is not listed here)
    9595
    9696=== Evaluation ===
    9797
    98 Licensing: GNU Public License (version 3)
     98**Licensing:** GNU Public License (version 3)
    9999
    100 Language: Python
     100**Language:** Python
    101101
    102 Activity: Active
     102**Activity:** Active
    103103
    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/
     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/
    105105
    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/
    107107
    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
     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
    109109
    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.
     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.
    111111
    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.
    113113
    114 User base: Their user base are the contributors: http://www.pygaze.org/contributors/
     114**User base:** Their user base are the developers and the contributors: http://www.pygaze.org/contributors/
    115115