Changes between Version 4 and Version 5 of ProjectGazePointer


Ignore:
Timestamp:
05/24/18 01:01:35 (7 years ago)
Author:
Monika Rizova
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ProjectGazePointer

    v4 v5  
    3535**Leadership**: user: szydej, link: ​https://sourceforge.net/u/szydej/profile/, linkedin profile: ​https://www.linkedin.com/in/szymon-deja-6aba614a/
    3636
    37 **Forking**: Fork your own copy at this address https://github.com/esdalmaijer/PyGaze, for which you will need a !GitHub account.
     37**Forking**: Fork your own copy: git clone https://git.code.sf.net/p/gazeboard/code gazeboard-code
    3838
    39 **Communication**: There are a couple of ways for communicating with !PyGaze developers, one is their support forum accessible from http://forum.cogsci.nl/index.php?p=/categories/pygaze and the other is a contact form found at http://www.pygaze.org/contact/ (in case you do not want to create a forum account)
     39**Communication**: There is a forum for general discussion available at: https://sourceforge.net/p/gazeboard/discussion/general/, and the also have a facebook page: https://www.facebook.com/gazerecorder/.
    4040
    4141**Roadmaps**:
    4242 
    43 
    44 ''Original goal:''
    45  
    46   - bundles of code for a large range of different eye trackers from different manufacturers into a single interface.
    47   - open-source based on excisting libraries
    48 
    49 ''Future goals:''
    50 
    51   Short term:
    52   - better variable management and getting rid of some annoying bugs
    53   - an analysis suite to complement the existing experimental library
    54 
    55   Long term:
    56   - incorporate support for more eye trackers and support for even more obscure peripherals
    57   - support for electroencephalography
    58  
    59   Source: Interview with lead developer: https://opensource.com/life/15/12/pygaze-open-source-eye-tracking-toolkit
     43  The goal of the !GazeBoard project is to develop a gaze-based AAC system that supports and facilitates fast text entry, as the primary AAC tool for users.
    6044
    6145**Releases**:
    6246
    63   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
    64   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
    65   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
     47  N/A
    6648
    6749**Repositories**:
    6850 
    69   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.
    70   There is also a repository for !PyGazeAnalizer available at: https://github.com/esdalmaijer/PyGazeAnalyser
     51  The main repository of !GazeBoard is: https://sourceforge.net/p/gazeboard/code/ref/master/ , where you can make your own fork.
    7152
    7253**Packaging**:
    7354
    74    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/
     55   Different packages for !GazeBoard can be found at the downloads page of !GazeBoard at: https://sourceforge.net/projects/gazeboard/files/
    7556
    7657**Upstream/downstream**:
    7758
    78    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.
     59   There is no known information for contributing.
    7960 
    8061**Version Control**:
    8162
    82    version 0.6.0 (07-09-2017) - Latest version control
     63   version 1.2 Beta (2016-12-11) - Latest version control
    8364
    8465**Trackers**:
    8566
    86    You can see commits and verified changes at this link: https://github.com/esdalmaijer/PyGaze/commits/master
     67   There aren't available trackers.
    8768
    8869== Project Evaluation ==
    … …  
    9172=== Fieldtrips ===
    9273
    93 Github: https://github.com/esdalmaijer/PyGaze
     74Github: / (!GazeBoard is not listed here)
    9475
    95 Openhub: / (!PyGaze is not listed here)
     76Openhub: / (!GazeBoard is not listed here)
    9677
    97 Source Forge: / (!PyGaze is not listed here)
     78Source Forge: https://sourceforge.net/projects/gazeboard/
    9879
    9980=== Evaluation ===
    10081
    101 **Licensing:** GNU Public License (version 3)
     82**Licensing:** N/A (Other license)
    10283
    103 **Language:** Python
     84**Language:** N/A
    10485
    10586**Activity:** Active
    10687
    107 **Number of contributors:** There are two developers and a couple of official contributors. They are listed on this page: http://www.pygaze.org/contributors/
     88**Number of contributors:** N/A
    10889
    109 **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/
     90**Size:** Information about the size of the packages can be seen in the downloads page: https://sourceforge.net/projects/gazeboard/files/?source=navbar
    11091
    111 **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
     92**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.
    11293
    113 **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.
     94**New contributor:** There aren't any information for new contributors.
    11495
    115 **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.
     96**Community norms:** N/A
    11697
    117 **User base:** Their user base are the developers and the contributors: http://www.pygaze.org/contributors/
    118 
    119 [ProjectReviewPyGaze ...Review]
    120 
    121    
     98**User base:** Their user base is the developer.