IT Development/Progress meetings/Minutes 09 May 2013

Attendance and Apologies

1. KB - Katherine Bavage (User:Katherine Bavage (WMUK))
2. MP - Mike Peel (User:Mike Peel)
3. DT - Doug Taylor (User:RexxS)
4. EE - Emmanuel Engelhart (User:Kelson)
5. TM - Tom Morton (User:ErrantX)

Updates on Actions from previous meeting

Where outstanding actions were also substantive items on the main agenda they were discussed there

Item No	Assigned to	Action	Update
1. 210113 - Item 3.1 - Issue Tracking	KB/TM	Work with TM to set up a parallel bugzilla install with a project management extension, and test by end of Feb.	Doing... Bugzilla and Tech Wiki created. Need to agree access control for staff and community
2. 210113 - Item 3.3 - Backups	KB	Research costs of fireproof safe to inform a decision about on and off site back ups	Doing... KB will try and work with RS to secure by end of May '13
3. 210113 Item 3.4.1 - Security Audit	KB	KB to work on some straightforward guidance for trustees as a simple overview/checklist MP to review - perhaps in collaboration with the community or Tech Committee (can certainly draft on-wiki)	Doing... Volunteer and Trustee Security checklist - To be completed and circulated to Tech@ for commend by end of May '13. To be shared with new Trustees post AGM.
4. 210113 Item 3.4.1 - Security Audit	KB/TM	Review registration of data protection details in light of changed staffing and systems. KB to factor this in to ongoing security review work with TM.	Doing... Need to see input from engaged members of the community for suggested changes, and submit details of changes after QRpedia arrangements in place - hopefully by end of July '13.
5. 210113 Item 3.4.2 - CiviCRM	KB	Log feature requests and bug requests in RT to mirror a global development page on wiki (rework the existing 'shopping list' page)	Done TM migrated all bugs to RT but not comments. Will move all across and clost RT by end of July '13 (not urgent)
6. 280213 Item 2.4 - Updates on Actions	MP	Shut down elements on the server and take a final backup	Doing... MP will bring to office on 11th May. MP has copied backup data onto hard drive, needs to take a new backup before bringing to office.
7. 280213 Item 2.6 - Updates on Actions	KB/TM	Log 'backup manager process for Rackspace' as a job on rt. TM and propose solutions for March meeting.	Doing... Proposed process will be discussed by Tech Committee at the AGM.
8 280213 Item 2.6 - Updates on Actions	KB/MP	KB to liaise with MP on the purchase of a physical external hard drive (either MP to purchase in Manchester and claim for, or KB to purchase and arrange for it to be posted to MP) to transfer the holding of backups to the office.	Done
9. 280213 Item 2.8 - Updates on Actions	KB/TM/EE	Add 'Backup routine' to agenda for April meeting of Technical Committee and work on recommendations with TM/EE	Done
10. 280213 Item 2.13 - Updates on Actions	KB/EE	Catch up in Mid march to discuss implementation times of Civi CRM	Doing... KB has started this work but not had time to progress it post SF. Will schedule for w/c 13th May and liaise with EE. This is quite urgent now.
11. 280213 Item 2.13 - Updates on Actions	KB	Put EE in touch with Civi developer community.	Done KB attended Civi CRM March meetup and we may well be hosting the May meetup in Development house!

Operational

Issue tracker

KB reported she was happy with the joint implementation of Bugzilla and a supporting Wiki for planning. However, tasks were now not being logged through those processes. Need to get to the point where other people are using so all project and community requests go through there.

In discussion the following points were noted:

There were not currently any bugzilla requests from volunteers yet because the system hadn't been opened up.

• A concern that if a lots of varied requests would lead to difficulty prioritising.
• A need to be a system for people who were not used to bugzilla to receive support or log requests.
• A concern that lots of ideas and queries would use lots of developer time - this is something the office would have to manage in terms of costs
• Would have to develop backlogs - lower priority bugs would take longer to be dealt with - this is something the office would have to manage in terms of expectations for delivery times
• The long term aim had always been to make this something anyone could use to log ideas/bugs/requests with users just requesting an account

DT asked TM and EE if their workload was manageable currently? The consensus was that it was, and so it was worth moving on with opening up access and keeping under review if a problem develops.

ACTION:

• KB to refer the question to Tech committee 'Should we make bugzilla available to the community to log bugs' - can then provide as recommendation to the board.
• KB to work on language for the wiki page with TM to introduce people on how to use

The purpose and remit of the Tech@ mailing list was discussed. It was noted this had been initially used to coordinate bug reporting and other decision making/reporting, but this was becoming increasingly obsolete with the advent of Bugzilla and Techwiki. It might be better to open the list up, away from operational planning/delivery and more towards a forum for suggestions, questions, discussions and decisions for Tech Committee and interested community members. Different from other lists with a similar remit in that specifically to address UK Chapter involvement and work?

ACTION:

• KB review list archives for anything sensitive (i.e. passwords), deal with as necessary (i.e. change passwords)
• KB to invite identified members of the community interested in Tech Comm issues - Harry Burt, Rich Farnborough, Tom Morris, Charles Matthews, Gordon Joly etc - to tech@
• KB to start on-list discussion to decide mailing list policy i.e. open/closed, who to invite, aim of list (what topics) etc.
• DT to highlight tech work to Lua event attendees on the 19th May

QRpedia

KB summarised timeline for proceeding - Board to discuss on Saturday and decide whether to proceed - if they do, transfer of the domain could happen as early as w/c 13th May. However, it would depend on the manner of proceeding with transfer and any arrangements the board wished to put in place before doing so.

KB queried again that IP address data would be masked if the visitor stats page was public - EE confirmed this was the case and circulate the link to the test implementation.

Plan is transfer the domain, then re-direct visitors to the installation on our servers.

ACTION: Tom to contact Fasthosts about the migration process and any potential delay in transfer of the DNS ACTION: Emmanuel will ask the WMF to host code+tracker, official web page will be put on Meta ACTION: Roger and KB to work on list of users to contact and change in service and inform of date transfer when established.

Rackspace Backups

KB noted that by the Technology Committee meeting at the AGM the severs should be ready to go with a proposed backup software solution the Tech Committee will hopefully approve

ACTION; KB/TM to set up a day in the office to work through physical side of process after the Tech Committee meeting in June

Security audit

KB noted that ideally TM would speak with new staff, and there would be a whole-staff presence for an ICO half-day visit to the office in the summer. There would also need to be a security audit and policy review in September.

ACTION:

• KB to book TM to speak with new staff, possibly in conjunction with visit to set up servers, if not, by Skype or Google hangout
• KB to schedule ICO day (possibly with Trustees too i.e. before a board meeting?)
• KB to schedule policy review and audit in September

CiviCRM

KB explained her lack of availability in bug testing the installation on the Drupal platform EE had put in place.

ACTION:

• KB schedule and complete for w/c 13th May.
• KB/EE Following this work, plan migration timetable

SAGE server

KB noted that RS had decided to prefer to use networked computers in the office, so the Charity's accounts will not be accessible remotely. To come off future agendas.