Fundraising tech

Documentation for a fundraising tech audience is being moved to https://wikitech.wikimedia.org/wiki/Fundraising

This document should explain or link to everything needed for fundraising tech development.

About Fundraising Tech edit

Fundraising Tech is responsible for the security, stability, and development of the Wikimedia Foundation’s online donation systems. Millions of relatively small donations make up the majority of the Wikimedia Foundation’s operating budget every year. The donation systems created and maintained by Fundraising Tech were built specifically to make the small donor model a reality, across as many localities as possible to further ensure the continued independence of our mission.

We do not write banners or run tests, we support the people and software that run them.

Systems edit

International payment processing edit

  • 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 edit

We use Open Source CRM CiviCRM to manage our donor data

Tools to create, manage, and deliver online fundraising campaigns edit

  • 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 edit

Team edit

Who we are edit

  • 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 edit

How to find us edit

Timeline edit

Current Work edit

Phabricator task board: #fundraising-backlog

Roadmap edit

fr-tech's detailed Roadmap

Rhythm and code freeze edit

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.

Payment Processors edit


Useful Links edit

Subpages: