Changes between Version 2 and Version 3 of ProjectiTracePage
- Timestamp:
- 03/23/18 19:45:33 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ProjectiTracePage
v2 v3 11 11 - C++ compiler: g++ on UNIX or Microsoft Visual Studio on Microsoft Windows 12 12 - Java native interface (JNI) headers 13 14 iTrace has the following features: 15 16 - Session Creation 17 - Calibration 18 - Displacement Adjustment 19 - Source Code Entity Level Tracking 20 - Coarse-grained tracking on text files 21 - Raw Data Exports in an easy to understand format 22 - Fixation Exports 13 23 14 24 **URL:** … … 29 39 **Roadmaps**: 30 40 41 N/A 42 31 43 **Releases**: 32 44 33 1. 45 1. Shaffer, T., Wise, J., Walters, B., Müller, S., Falcone, M., Sharif B., (2015) “iTrace: Enabling Eye Tracking on Software Artifacts Within the IDE to Support Software Engineering Tasks”, 10th Joint Meeting of the European Software Engineering 46 Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering (ESEC/FSE 2015), Tool Track, Bergamo, Italy, August 30 – September 4, 4 pages to appear (preprint) 47 2. Kevic, K., Walters, B., Shaffer, T., Sharif B., Fritz, T., Shepherd, D., (2015) “Tracing Software Developers’ Eyes and Interactions for Change Tasks”, 10th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT 48 Symposium on the Foundations of Software Engineering (ESEC/FSE 2015), Bergamo, Italy, August 30 – September 4, 12 pages to appear 49 3. Walters, B., Shaffer, T., Sharif, B., and Kagdi, H. (2014), “Capturing Software Traceability Links from Developers’ Eye Gazes”, International Conference on Program Comprehension (ICPC’14), ERA track, Hyderabad, India, June 2 – June 3 2014, pp. 50 201-204 (Replication package) — Used an earlier version of iTrace 51 4. Walters, B., Falcone, M., Shibble, A., Sharif. B., (2013), “Towards an Eye-tracking Enabled IDE for Software Traceability Tasks”, 7th International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE 2013). San Francisco, 52 CA, May 19 2013. pp 51-54 34 53 35 54 **Repositories**: 36 55 37 The main repository of is: , where you can download the source code, clone it to desktop, or even make your own fork. 38 56 iTrace's repository is found at: https://github.com/trshaffer/iTrace , where you can download the source code, clone it to desktop, or even make your own fork. 39 57 40 58 **Packaging**: 41 59 60 N/A 42 61 43 62 **Upstream/downstream**: 44 63 45 64 To collaborate on this project you can contact Bonita Sharif at bsharif@ysu.edu, or you can make your own fork and wait for pull request approval (if you want to develop, you should develop all new features as a new branch, master is reserved for stable code.) 46 65 47 66 **Version Control**: 48 67 68 v0.1.0 on Jul 30, 2014 49 69 50 70 **Trackers**: 51 71 52 72 You can see commits and verified changes at this link: https://github.com/trshaffer/iTrace/commits/master 53 73 54 74 == Project Evaluation == … … 57 77 === Fieldtrips === 58 78 59 Github: 79 Github: https://github.com/trshaffer/iTrace 60 80 61 Openhub: 81 Openhub: This project is not listed here. 62 82 63 Source Forge: 83 Source Forge: This project is not listed here. 64 84 65 85 === Evaluation === 66 86 67 **Licensing:** 87 **Licensing:** GNU GENERAL PUBLIC LICENSE Version 2, June 1991, https://github.com/trshaffer/iTrace/blob/master/LICENSE.md 68 88 69 **Language:** 89 **Language:** Java 70 90 71 91 **Activity:** Active 72 92 73 **Number of contributors:** 93 **Number of contributors:** There are 6 student contributors and one project supervisor, listed on this page: http://seresl.csis.ysu.edu/iTrace/index.php/people/ . On GitHub 7 people has contibuted with commits: https://github.com/trshaffer/iTrace/graphs/contributors 74 94 75 **Size:** 95 **Size:** N/A 76 96 77 **Issue tracker:** 97 **Issue tracker:** The issue tracker at !github is used to keep track of new features and bugs. 78 98 79 **New contributor:** 99 **New contributor:** If you want to be a contributor you can make your own fork and wait for pull request approval (you should develop all new features as a new branch, master is reserved for stable code.) 80 100 81 **Community norms:** 101 **Community norms:** You can report an issue through the issue page on !GitHub, help to fix it by forking in the GitHub repository and commit fixes and if you prefer to work via different channels you can contact Bonita Sharif at bsharif@ysu.edu. 82 102 83 **User base:** 103 **User base:** The user base are the student contributors and the project superviser, http://seresl.csis.ysu.edu/iTrace/index.php/people/ 84 104