Skip to content

Proposal for donation implementation #1503

@drjwbaker

Description

@drjwbaker

Following work on donation mechanisms #1457, membership #1405, and business models #1487 we propose to use this ticket to agree on implementing of donations to support our work. There are a number of strands to this work, so this is my attempt - on behalf of the Project Development Team - to pull together an actionable proposal.

  1. We propose Patreon as the primary mechanism for ongoing donation, the benefit of which being that it provides a sustainable income. We propose to implement the Patreon tiers listed at Patreon #916 (comment). Once agreed these are hard to change (adjusting the tiers means cancelling ongoing donations), so we need to get this right. This is all setup and ready to go.
  2. We propose Paypal as the primary mechanism for one off donations, the benefit of which is that Paypal is a widely used checkout mechanism. We will also accept bank transfer, cheque, and cash. This is all setup and ready to go.
  3. We propose that parts of the site be updated to generate donations. These include:
    a) Update to https://programminghistorian.org/en/support-us listing all possible donation routes. This is ready to go in English Add donation mechanism wording #1504 and will move to translation if/when agreed.
    b) Paypal and Patreon buttons in the site footer. This has been tested DO NOT MERGE patreon test #1502
    c) Some kind of banner, perhaps as a call out on all our lesson pages, where we can display donation info and our latest campaign. This is currently the least specified part of the proposal. We'd be grateful for input from @jenniferisasi on this, and how this might fit with comms (e.g. the twitter bot)

Under our Lazy Consensus model I move that we discuss this at our next Editorial Board meeting #1483 with a view to receiving all feedback no later than 4 November 2019.

Note, I think this affects everyone in some way, so please take a look. For example:

  • @jenniferisasi: this feeds into the comms strategy
  • @programminghistorian/technical-team: scoping design of 3c above will involve technical time.
  • @programminghistorian/french-team @programminghistorian/spanish-team @programminghistorian/english-team: editorial impacts here include workflows for copyediting English Language Copyediting #1381 using funds generated and translation labour.
  • @JMParr: impact on global team relating to capacity funds will hopefully create to spend money on activities that support audiences in the global south.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions