Fundraising tech/Chores

This page will list the repetitive and / or reactive ongoing work that members of the fr-tech team need to do.


 * Checking damaged message table
 * In CiviCRM, go to /damaged. Look at the stuff from this week. If the error looks like a database lock, please requeue the message. If it's a new type of failure, please file a phab ticket.
 * Following up on incoming failmail
 * Update the Failmail zoo if it's something common
 * File phab tasks with details of what we need to do so it stops failmailing.
 * Email team letting them know it's been documented
 * Log checking
 * On our centralized logging box, scan through the error logs from today and file phab tasks
 * Deployments
 * CentralNotice (not for long)
 * CiviCRM
 * Payments-wiki
 * SmashPig
 * CiviCRM Upgrades
 * Download latest civicrm code and swap out our civicrm folder with it.
 * Some custom code that will need to be ported over.
 * Documentation of custom code?
 * Vagrant updates
 * Note any persistent issues with vagrant, especially if they're coming up in standup and see if it can be fixed