International payment processing

• The majority of donations run through integrations with 6 payment processors. We are also integrated with several other processors for accessibility, location and fundraising event uses. These integrations enable us to support online fundraising campaigns in approximately 30 countries each year.

CiviCRM - our donor database

We use Open Source CRM CiviCRM to manage our donor data

Tools to create, manage, and deliver online fundraising campaigns

• We are the primary developers and maintainers of the CentralNotice system, which delivers banner notices to the wikipedias and the sister projects. Historically, banners on the wikis have been the primary method by which we entice users to donate.
• We use SWAP to query banner data.
• Note: We partner with the Advancement department, Major Gifts, Banner and Email teams, operations and Donor services. Fundraising tech provides stable platforms and tools to Advancement, and they create specific fundraising campaigns and other donor-facing messaging and content.

Documentation - Monitoring, Testing, Deploying

• Monitoring with Grafana dashboards
• Essential systems - what to watch
• Software components - how they work

• Installing locally, testing, and deploying - how to fix it
  

Who we are

• Director: Greg Grossmeier
• Engineering Manager: Dylan Kozlowski
• Tech Lead: Elliott Eggleston
• Software Engineers: Andrew Green, Eileen McNaughton, Jack Gleeson, Christine Stone, Damilare Adedoyin, Wenjun Fan
• Ops Engineers: Jeff Green, Dallas Wisehaupt
• Senior Product Manager: Anil Kanji

How we work

• Roles/Responsibilities: Fundraising tech/Roles and Responsibilities
• Team training matrix: Fundraising tech/Training
• Regular meetings and their agendas Fundraising tech/FR-tech Meetings

How to find us

• You can find our engineering team on the #wikimedia-fundraising ^connect IRC channel. Include "fr-tech" in your message to make sure we see it.
• I found a bug!

Current Work

Phabricator task board: #fundraising-backlog

Roadmap

fr-tech's detailed Roadmap

Rhythm and code freeze

We have a special yearly window of not deploying major changes to some critical systems starting in the fall, in preparation for the Big English drive.  Game on again in mid-January, assuming we haven't emitted a puff of smoke in early December.

This code freeze gives our development an annual cadence, with each season seeing similar types and intensities of work, year-over-year.  Any long-running FR-tech project should take this into account.