- Firefox is proposed as the cross-platform browser. Chrome, the other potential alternative, has some issues (such as grid certificates) which would make it problematic at this time. Reviewing this choice could be envisaged every two years or so.
- This choice should not mean that applications should only be developed with Firefox in mind. Web standards should still be used even if Firefox testing is added.
- While automated software distribution has its benefits, the resources and forced software management implications are such that this should not be a pre-requisite to a standard browser roll-out. It would be desirable to have an entry in CMF which would list applications such as firefox where there is IT support to encourage users to choose these solutions rather than random equivalent ones from the Internet.
- The security mails for firefox should be adjusted such that it informs the user where to get the updates from and to restart the browser.
- If 3rd level engineering cannot find a solution to a support call, the problem should be documented and submitted to bugzilla. The link should then be posted into the ticket and the case can be closed as ‘cannot fix’. The user (or other interested parties) can then follow up on the solution with the firefox community.
Follow up actions:
- Tim to discuss with Derek Mathieson (GS/AIS) and Tim Smith (IT/UDS) on a formal statement and necessary testing for firefox
- Tim to review the helpdesk and engineering support for firefox and investigate modifications to CMF to support the links to external applications
- Tim to make a proposal to the ITSRM following the IT Program of Work meeting if all parties are in agreement
There are minutes attached to this event.
Show them.