Pilot 2 - Work Overview
From wiki.gpii
Revision as of 16:44, 6 November 2013 by Bsheytanov (talk | contribs) (→Pilot Scenario:: Updating status of Astea's tasks)
Contents
- 1 Relevant documents:
- 2 PILOT 2 PANIC LIST/PLAN
- 2.1 Pilot Scenario:
- 2.1.1 STEP 1 - User uses platform A (either Windows or Linux) and the PMT (launched via a desktop shortcut) to create a new GPII account and insert preferences
- 2.1.2 STEP 2 - User saves and applies their preferences, which saves the preferences (to the preferences server), and system automatically applies them to the system, generates a token and shows the user what their new token is
- 2.1.3 STEP 3 - Facilitator puts the token on USB or NFC/RFID
- 2.1.4 STEP 4 - Facilitator using a desktop icon takes a snapshot of the settings for purposes of logging of the solutions we are testing: Orca, NVDA, Supernova, Maavis, built in Windows and Linux a11y features
- 2.1.5 STEP 4 - User closes the PMT which brings up the PCP. User modifies settings and immediately sees the changes on the system. User then saves the changes.
- 2.1.6 STEP 5B - User manually modifies settings in the ATs. 6. Facilitator takes a snapshot of the settings for purposes of logging - in case of manually modified settings in step 5b, the snapshotted settings are uploaded to the prefs server
- 2.1.7 STEP 7. Facilitator selects a matchmaker using a desktop icon.
- 2.1.8 STEP 8. User logs out of Platform A
- 2.1.9 STEP 9. User logs into platform B (Windows, Linux, Android, Simple phone, Windows tablet)
- 2.1.10 STEP 10. Facilitator takes a snapshot of the settings for the purposes of logging of the solutions we are testing: platform A solutions, Android built in a11y features, Mobile Accesibility (android), Java phones built in features and conf call app, smarthouse, eCtouch , eC mobile, Sociable, Google Chrome
- 2.1.11 STEP 11. User manually tweaks settings in the application(s)
- 2.1.12 STEP 12. Facilitator takes another snapshot of the settings (using the logging tool or manually, depending on the SP3 application)
- 2.1.13 STEP 13a. User logs out of the system Continuing scenario for Non-sighted users:
- 2.1.14 STEP 14b. User logs into platform A with multiple screen readers installed - Supernova and NVDA
- 2.1.15 STEP 15c.The system displays a message that the facilitator reads to the user.
- 2.1.16 STEP 13b. User logs into a platform X which is (simulated) lockdown mode with only browser available
- 2.1.17 GENERAL
- 2.2 Demos at the pilots:
- 2.3 SP3 Implementations:
- 2.4 Other:
- 2.1 Pilot Scenario:
Relevant documents:
- See full list of Pilot 2 JIRAs at: http://issues.gpii.net/issues/?filter=10001
- Based on Pilot Scenario description at: https://docs.google.com/document/d/1f4s6EUpLRR9ZMqQyJufmwx0l7HfzxdSNYusZa8vysSc/edit
- SP3 Responsibles: https://docs.google.com/document/d/1SFKCBIrr2il59mZtySqGMxjvuFEOPszNLAyk8xrCdyc/edit#heading=h.qvwpuw1649w0
PILOT 2 PANIC LIST/PLAN
Pilot Scenario:
STEP 1 - User uses platform A (either Windows or Linux) and the PMT (launched via a desktop shortcut) to create a new GPII account and insert preferences
- launching and creating account:
- DESIGN: Ensure that the PMT tool allows creation of new accounts - JESS **CLOSED **
- Write up instructions on how to make a shortcut for PMT windows and linux - CHRIS P **OPEN**
- Devise a means by which Preferences Editors can communicate with a locally-installed Flow Manager - ANTRANIG **OPEN**
- Implement: Ensure that the PMT tool allows creation of new accounts - CHRIS P **OPEN**
- Preference editor frame and usage
- Implement preview-per-setting - - CHRIS P **IN PROGRESS**
- Implement the preferences editors frames for iteration 2 - ALEXANDER **OPEN**
- Allow i18n of the preferences editors - CHRIS P **OPEN**
- Make PMT available online - KASPER **OPEN**
- Need an indicator showing that the user is logging in/logging out - ALEXANDER **OPEN**
- Adjuster Implementation:
- Implement the Speak Text adjuster group - ALEXANDER '**IN PROGRESS**'
- Implement the Increase Size adjuster group - CHRIS P **IN PROGRESS**
- Implement the Add Contrast adjuster group - CHRIS P **OPEN**
- Design: Define remaining adjusters for PCP/PMT for pilot 2 terms - JESS **CLOSED **
- Implement: remaining adjusters for PCP/PMT for pilot 2 terms - ALEXANDER '**IN PROGRESS**'
STEP 2 - User saves and applies their preferences, which saves the preferences (to the preferences server), and system automatically applies them to the system, generates a token and shows the user what their new token is
- Saving Preferences to the preferences server:
- Design: Ensure that PMT/PCP can save settings to the preferences server - JESS **CLOSED **
- Implementation: Ensure that PMT/PCP can save settings to the preferences server - ALEXANDER **OPEN**
- Token Generation and Display:
- Design: Display user token somewhere in big letters on 'user' creation - JESS **CLOSED **
- Implement: Display user token somewhere in big letters on 'user' creation - YURA **OPEN**
- Applying Settings from the PMT
- Design: It should be possible to apply settings to system/login from the PMT - JESS **CLOSED **
- Implementation: It should be possible to apply settings to system/login from the PMT - CHRIS **OPEN**
- Set up device reporter payloads for each pilot scenario - ELENI **OPEN**
- Core support for new common terms
- Update code to conform with decision on supporting both highContrastTheme and highContrastOn - KASPER **OPEN**
- Update core framework to support the new common terms and update any changed common term - KASPER **OPEN**
- Implement fluid.transforms.quantize transform function - KASPER **OPEN**
- The UI Options Mammals demo fails to start and is no longer necessary - KASPER **OPEN**
STEP 3 - Facilitator puts the token on USB or NFC/RFID
- Create description on how to create an NFC/USB for facilitators - KASPER **OPEN**
STEP 4 - Facilitator using a desktop icon takes a snapshot of the settings for purposes of logging of the solutions we are testing: Orca, NVDA, Supernova, Maavis, built in Windows and Linux a11y features
- Implement snapshotter - KASPER **OPEN**
- Improve logging functionality of the framework - YURA **OPEN**
STEP 4 - User closes the PMT which brings up the PCP. User modifies settings and immediately sees the changes on the system. User then saves the changes.
- Add support for live updates of the system settings - YURA **OPEN**
- Define presets for PCP for all pilot 2 common terms - JESS **CLOSED **
- Implement presets for PCP for all pilot 2 common terms - BOYAN **RESOLVED AS DUPLICATE**
- Find out how the PCP should be launched - JESS **CLOSED **
- Implement functionality for the system to report the currently logged in user on request - YURA **OPEN**
- Change capabilities transformation of highContrast [Boolean] - CLAUDIA **OPEN**
STEP 5B - User manually modifies settings in the ATs. 6. Facilitator takes a snapshot of the settings for purposes of logging - in case of manually modified settings in step 5b, the snapshotted settings are uploaded to the prefs server
- Mechanism for uploading snapshotted settings to the Preferences Server - KASPER **OPEN**
- Need method to save snapshotted settings to log
STEP 7. Facilitator selects a matchmaker using a desktop icon.
- Matchmaker strategy should be selectable via a desktop shortcut - KASPER **OPEN**
- Implement: Ensure that matchmaker strategy can be selected from user NP set as opposed to config file - YURA **OPEN**
STEP 8. User logs out of Platform A
- Figure out a mechanism for users to log out if they're not logged in using a classic listener - JESS **CLOSED **
STEP 9. User logs into platform B (Windows, Linux, Android, Simple phone, Windows tablet)
- General:
- The RFID User Listener is broken on Linux - STEVE HENS **OPEN**
- Include support for volume in windows - COLIN **OPEN**
- Statistical MatchMaker:
- Ensure that Statistical Matchmaker works with the rest of the system - ANDY **OPEN**
- Rules Based MatchMaker
- Ensure that Rules Based Matchmaker works with the rest of the system - CLAUDIA **OPEN**
- Complete the general rules on selecting solutions required for the second round of pilots - CLAUDIA **OPEN**
- RB-MM Webservice integration tests - CLAUDIA **OPEN**
- Complete constraint based rules required for the second round of pilots - CLAUDIA **OPEN**
STEP 10. Facilitator takes a snapshot of the settings for the purposes of logging of the solutions we are testing: platform A solutions, Android built in a11y features, Mobile Accesibility (android), Java phones built in features and conf call app, smarthouse, eCtouch , eC mobile, Sociable, Google Chrome
- Figure out how to log settings for those platforms where snapshotting isnt supported - Christophe **OPEN**
STEP 11. User manually tweaks settings in the application(s)
STEP 12. Facilitator takes another snapshot of the settings (using the logging tool or manually, depending on the SP3 application)
STEP 13a. User logs out of the system Continuing scenario for Non-sighted users:
STEP 14b. User logs into platform A with multiple screen readers installed - Supernova and NVDA
STEP 15c.The system displays a message that the facilitator reads to the user.
- Rule Based Matchmakers feedback mechanism for pilot should be implemented - CLAUDIA **OPEN**
- Need to create the device reporter payload for the multiple solutions scenario - CLAUDIA **OPEN**
STEP 13b. User logs into a platform X which is (simulated) lockdown mode with only browser available
- Device a mechanism for a machine to give information about it being locked down - CLAUDIA **OPEN**
GENERAL
- We need acceptance tests that cover the entirety of the pilots - IGNACIO **OPEN**
Demos at the pilots:
1. Context Awareness Support
- Context Awareness support - create demo for the pilots - JAVI **OPEN**
2. Advanced PMT wireframes
- Prepare advanced PMT wireframes for Pilot 2 - JAN - PAUL **OPEN**
SP3 Implementations:
SuperNova:
- Create basic solution entry for solution for SuperNova - NIKOS **OPEN**
- Define and Write transformations for all relevant settings for SuperNova - NIKOS **OPEN**
- Write acceptance tests for SuperNova - NIKOS **OPEN**
Smarthouse
- Do initial integration of the SmartHouses online simulation - BOYAN **OPEN**
- Create basic solution entry for solution for SmartHouse - BOYAN **OPEN**
- Define and Write transformations for all relevant settings for SmartHouse - BOYAN **OPEN**
- Write acceptance tests for SmartHouse - BOYAN **OPEN**
- Implement Greek translation of Smarthouse - BOYAN **OPEN**
- Implement German translation of Smarthouse - BOYAN **OPEN**
Linux:
- Default GNOME on-screen keyboard misnamed as Caribou - KASPER **OPEN**
- Finalize settings, transformations of Linux for pilots - JAVI **OPEN**
- Provide a mechanism to deal with system's volume on GNU/Linux using ALSA - JAVI **OPEN**
Windows:
- setting invert for Windows Magnifier is mapped to common term invertImage but invertColours might be a better match. - KASPER **OPEN**
- Remove everything font-size from windows - COLIN **OPEN**
- Finalize transformations for Windows - KASPER **OPEN**
- Windows magnifier relaunches on onscreen keyboard - COLIN **OPEN**
- Taskkill.exe cannot kill processes when the user is not administrator unless they lower their notification settings - COLIN **OPEN**
Sociable:
- Create basic solution entry for solution for Sociable - THANOS **OPEN**
- Define and Write transformations for all relevant settings for Sociable - THANOS **OPEN**
- Write acceptance tests for Sociable - THANOS **OPEN**
Google Chrome:
- Create basic solution entry for solution for Google Chrome - IGNACIO **OPEN**
- Define and Write transformations for all relevant settings for Google Chrome - IGNACIO **OPEN**
- Write acceptance tests for Google Chrome - IGNACIO **OPEN**
Android:
- Create a Settings Handler for Android's Settings.System and Settings.Secure - TOMAS **IN PROGRESS**
- Provide start and stop capabilities to Android - TOMAS **REVIEW**
- Create basic solution entry and implementation for Android - JAVI **OPEN**
- Define and Write transformations for all relevant settings for Android OS - JAVI **OPEN**
- Write acceptance tests for Android OS - JAVI **OPEN**
- Build failed due to missing jtar dependency - JAVI **OPEN**
- Improve Android's GPII Activity UI - JAVI **OPEN**
- The Android repository contains autogenerated files that aren't necessary - COLIN **OPEN**
- The realtime framework fails to build with the Android 18 SDK - COLIN **OPEN**
- The Android version of the realtime framework fails to run - JAVI **CLOSED **
Maavis:
- Checking settings can be set for Maavis and Windows platform - KASPER **OPEN**
- Maavis to be translatable - STEVE **OPEN**
- Define and test common terms transformation settings for Maavis - STEVE **OPEN**
- Write acceptance tests for Maavis - STEVE **OPEN**
- Implement Spanish translation of Maavis - STEVE **OPEN**
- Implement Greek translation of Maavis - STEVE **OPEN**
- Implement German translation of Maavis - STEVE **OPEN**
Mobile Accessibility:
- Create basic solution entry and implementation for Mobile accessibility - FERRAN **OPEN**
- Define and Write transformations for all relevant settings for Mobile Accessibility - FERRAN **OPEN**
- Write acceptance tests for Mobile Accessibility - FERRAN **OPEN**
- Implement Greek translation of Mobile Accessibility - FERRAN **OPEN**
- Implement German translation of Mobile Accessibility - FERRAN **CLOSED **
- Create Mobile Accessibility for Cloud4All prototype in Spanish - FERRAN **CLOSED **
- Add GPII support for Mobile Accessibility - FERRAN **OPEN**
- Provide example preference sets for Mobile Accessibility - FERRAN **OPEN**
Java Mobile:
- Create basic solution entry and implementation for Java Mobile - KOSTAS K **OPEN**
- Provide full list of settings for Java Mobile / Symbian - KOSTAS K **OPEN**
- Define and Write transformations for all relevant settings for Java Mobile - KOSTAS K **OPEN**
- Write acceptance tests for Java Mobile - KOSTAS K **OPEN**
NVDA:
- Finalize transformations for NVDA - KASPER **OPEN**
WebAnywhere:
- Finalize transformations for Webanywhere - KASPER **OPEN**
eCTouch and eCMobile:
- Create basic solution entry and implementation for eCTouch - CHRISTOFFER **OPEN**
- Create basic solution entry and implementation for eCMobile - CHRISTOFFER **OPEN**
- Provide full list of settings for eCTouch - CHRISTOFFER **OPEN**
- Provide full list of settings for eCMobile - CHRISTOFFER **OPEN**
- Define and Write transformations for all relevant settings for eCMobile - CHRISTOFFER **OPEN**
- Define and Write transformations for all relevant settings for eCTouch - CHRISTOFFER **OPEN**
- Write acceptance tests for eCmobile - CHRISTOFFER **OPEN**
- Write acceptance tests for eCtouch - CHRISTOFFER **OPEN**
- Implement German translation of eCMobile and eCTouch - CHRISTOFFER **OPEN**
- Implement Greek translation of eCMobile and eCTouch - CHRISTOFFER **OPEN**
- Implement Spanish translation of eCMobile and eCTouch - CHRISTOFFER **OPEN**
Other:
Next Steps: Clarify with Claudia what the system can do in terms of the pilots. Find out if there is anyone else building other scenarios. Get estimates from Antranig, Boyan, Jess Create JIRAs for SP3 apps, based on: https://docs.google.com/document/d/1sU6e5Su5DUn928ZhBEfXQOsmaYjrEFP5FqHgXG6yQc8/edit#heading=h.g9ses598hi5c Consider Out of Scope
Applications that don't give us an API to make the modifications directly.
