| | 1 | = New Data Protection Procedures Proposal = |
| | 2 | |
| | 3 | These proposals are being made in response to the [wiki:julia-recovery data loss experienced on julia], based on the suggestions and proposals made a the [wiki:julia-recovery/notes-2011-04-13 April 13, 2011 members meeting] on the topic. |
| | 4 | |
| | 5 | * Regular human-run passphrase audits to ensure we always have all passphrases for all servers. |
| | 6 | |
| | 7 | * Regular automated backup audits. We currently receive an email alert when a backup returns an error. We need a second automatic audit, independent of the backup process that confirms they have run |
| | 8 | |
| | 9 | * Regular human-run backup audits. In addition to automatic audits, we need periodic human review of backups to ensure that what needs to be backed up is in fact being backed up. |
| | 10 | |
| | 11 | * Better tools and instructions for non-technical members empowering them to ensure they have a backup of their own data. These should include video tutorials and training meetings. |
| | 12 | |
| | 13 | * Discussion and recommendations on best practices for developers on how to incorporate full backups into the site development cycle. |
| | 14 | |
| | 15 | * Change language of membership agreement to reflect commitment to backing up and protecting data |
| | 16 | |
| | 17 | * New member monthly phone orientations to build member community |
| | 18 | |
| | 19 | * Recruit member ambassadors in multiple cities so more members can have face-to-face time with other MFPL members. |
| | 20 | |
| | 21 | * Audit all members to ensure everyone has paid and, for people who don't respond for a given period, disable their accounts. |
| | 22 | |
| | 23 | * Start ad-hoc group to review, finalize, seek approval from Leadership Committee and cary out proposals. |
