From wiki.gpii
Revision as of 20:46, 17 December 2014 by GreggVan (talk | contribs)
Jump to: navigation, search

For each solution to be integrated the following steps will be performed by the Tiger Team

  1. Identify key contact person(s) and contact them.
    1. Permissions - ownership - mgmt etc
    2. Technical (launch - settings access - meaning of settings)
  2. Redesign the way a product handles settings (optional)
    1. Saves preferences to better match the GPII
    2. Uses settings -- to allow live use of externally changed settings
  3. Create a translation/un-packing tool (as required)
    1. to convert binary and other compressed settings files into GPII inferrable/adjustable/transformable form.
  4. Register and align the preferences/settings in the product with the Preference Terms Definitions Registry
    1. mfgr might do -- but we should offer since MUCH MUCH easier for us to do because we know what is in Registry and what they are called
    2. mfgr should participate because they know what their term mean
  5. Launch and Setting handlers
    1. Create/adapt/select
    2. Can we do “live” settings change for context etc?
  6. Document
    1. Solution specific notes
    2. Generic documentation for others