Thanks ! Gregg C Vanderheiden [email protected]
> On Jan 23, 2017, at 7:29 AM, Steve Lee <[email protected]> wrote: > > In previous discussion on the subject of installers in the context of > the LGS project we came up with a couple of extra points > > 1) General Installer - should be accessible - at least usable without > sighted assistance by VI users. > > 2) Sysops installer - in the case of the Windows installer IT depts > often expect a MSI module (not interactive declarative). These list > all actions so can be reviewed for security etc and also can be merged > with other deployments scripts > > Hope that helps > > Steve Lee > OpenDirective http://opendirective.com > > > On 21 January 2017 at 18:21, Gregg C Vanderheiden <[email protected]> wrote: >> ACTION REQUESTED: >> >> Technical team - provide any issues identified on this to Sandra >> Other Teams - provide any issues identified on this to Gregg >> >> WHEN: By Monday Jan 30th >> >> >> >> After talking with Sandra (who checked with a couple others) I am calling a >> tentative decision as follows. >> >> >> NOTE: >> >> Tentative decision means that it is a decision that is posted widely for >> stated period (in this case 1 week) - to be sure that nothing was missed in >> the process of coming to the decision. >> >> After that time it moves to Decision. >> >> Decisions can be reversed later with new data or circumstance — but are not >> reversed without good cause. >> >> >> We are working on documentation on when things need formal decision - and >> how and where they will be recorded. >> >> One criteria will be decisions that must be relied upon by others or other >> groups >> One place there will always be a link to the decision will be in the project >> folder (or JIRA Thread) where the work is being done. >> >> (a LINK rather than a copy of the decision is proposed to avoid a situation >> where a decision is changed — but random copies of old decision still lie >> around to confuse.) >> >> >> 1-Week Tentative Decision >> There will be two versions of the installer >> >> General or Regular Installer >> >> There is NO screen displaying or allowing the choice of components to >> install >> There is NO screen to determine where it would be installed >> The language on all of the installer screens will be very “low-tech-user >> friendly” >> Will be implemented soon - (as soon as screen texts are ready) so that it is >> available for user testing >> >> SysOp Installer >> >> Includes a listing of the components to be installed >> MAY allow installers to OPT OUT of SOME of the components (e.g. a listener) >> MAY or MAY NOT use the very “low-tech-user friendly” text on some or all >> of its screens. >> >> To be determined through tech team advice, pilot team info from pilot >> sysops, and user testing with Sys-ops >> (use of same language on screens has efficiency if it is not problematic for >> SysOps >> >> Will be implemented when there is a call for it - and we have better info on >> what should be included >> >> Tech-Build team can decide WHEN to build SysOp - and that may be NOW if it >> good to have something to discuss with SysOps — or if needed for HDWR >> testing — or for other reason. >> >> >> Rationale >> >> Non technical users will be installing the GPII on computers - such as their >> home computer >> The screen showing component causes some to worry because they don’t >> understand what it means - or what they are to do. It stops others. >> Having non-technical people chose where to install can have bad consequences >> — and may make support and troubleshooting more difficult. >> Sys-Ops on the other hand may want to know what is being installed — or may >> NEED to be able to not install certain optional components >> SysOps may NEED to change the location of installation for some reason >> SysOp version is to be implemented when needed — so we don’t implement if >> not needed — and so we are more fully informed when we do. But decision >> left to Tech-Build team so they can coordinate >> >> >> >> >> Technical team - provide any issues identified on this to Sandra >> Other Teams - provide any issues identified on this to Gregg >> >> thanks >> >> Gregg >> >> Gregg C Vanderheiden >> [email protected] >> >> >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> http://lists.gpii.net/mailman/listinfo/architecture >> > > _______________________________________________ Architecture mailing list [email protected] http://lists.gpii.net/mailman/listinfo/architecture
