Supporting the Programming Historian The Programming Historian is a volunteer-driven project. We are committed to open source values and our content will not disappear behind a paywall. However, in order for it to grow, improve, and sustain our work, in 2018 the Editorial Board of The Programming Historian started to put in place financial and policy-based mechanisms for accepting sponsorship and donations. This enables us to: Maintain our infrastructure. Bring in professional services that enhance the quality of our publications. Improve our community outreach and internationalisation. Protect The Programming Historian from changes to service agreements of those ‘free’ services upon which we rely. Supporters The project is grateful for the following support: Our Institutional Partner Programme members: KU Leuven Libraries [2020-Present] Institute of Historical Research Wohl Library [2020-Present] University of Sussex Library [2020-Present] Centre for Data, Culture and Society, University of Edinburgh [2020-Present] Western University Library [2020-Present] DOI infrastructure is supported by the University of Sussex Library [2020-Present]. Web development is supported by the dSHARP lab at Carnegie Mellon University and the Andrew W. Mellon Foundation [2018-2020]. Ongoing hosting support from the Roy Rosenzweig Center for New Media (RRCHNM) [2011-Present]. Funding to support the project “The Programming Historian: developing and sustaining impact in the Global South” provided by the ESRC Impact Accelerator Account, University of Sussex . Funding to support the development of a style guide provided by the School of Humanities, University of Hertfordshire . Funding to support establishing the Programming Historian as a legal entity provided by the School of History, Art History and Philosophy, University of Sussex . Funding for a writing workshop in Bogota, Colombia, supported by the British Academy . Seed funding and project management support from the Network in Canadian History & Environment (NiCHE) [2011-2013]. Our founding Patreon subscribers Rachel Murphy (‘Subscriber’ tier), Miriam Posner (‘Sponsor’ tier), and Tim Hitchcock (‘Patron’ tier). We would particularly like to thank the following ‘Patron’ tier Patreon subscribers: Tim Hitchcock, Shawn Graham, Jeff Blackadar, Jodi Burkett, Michael Piotrowski, Mark Edwin Peterson, Nickoal Eichmann-Kalwara. Donate to Us Individual donors to the Programming Historian are vital to growing, improving, and sustaining our work. We welcome both one-time and ongoing donations: Ongoing donations by becoming a supporter of the Programming Historian via Patreon. One-time donations can be made to the Programming Historian via Paypal, bank transfer (Lloyds Bank account number 55263268, sort code 30-96-26), or cheque (made payable to ‘ProgHist Ltd’ and posted to ‘Dr James Baker, Arts A135, University of Sussex, United Kingdom, BN1 9RH’). For donations via bank transfer and cheque, we’d be grateful if you could write to us at [email protected] to let us know who you are and why you’ve chosen to support our work. Institutional Partner Programme The Programming Historian Institutional Partner Programme enables your library, university, or research centre to support the growth, development, and sustainability of our award winning open access publishing platform. By joining the Institutional Partner Programme you will receive the following benefits: An invitation to our ProgHist Ltd Annual General Meeting as an Advisory Member (one individual per Partner). An annual breakdown of ProgHist Ltd expenditure. Acknowledgement of your contribution on our ‘Supporters’ page. The right to use Programming Historian Institutional Partner Programme membership in marketing activities. Want advice on running an open access publication, implementing multilingual publishing workflows, or adapting Programming Historian articles for a workshop environment? Your IPP membership gives you access to ad hoc advice from our expert team (on request, not including formal consultancy). For library partners: a list of articles published by all Programming Historian journals (on request). Partnership rates for 2020 are set at £1,000 GBP (approximately $1,300 USD / €1,180 EUR) and £150 (approximately $195 USD / €175 EUR) for partners in ODA eligible countries. Rates are due annually from the date of first payment. Rates are published in January each year. To become a Institutional Partner, please email James Baker at [email protected] with “Institutional Partners Programme” in the subject line. Your email should include the following information: Your Name. Your Institution. Your Preferred Method of Payment (bank transfer, cheque, invoice, Paypal). Your Preferred Currency (if this is not listed, please ask). Note that upon email with the subject line “Institutional Partners Programme” you agree to the following conditions: You are authorized to commit to expenditure of the institution whose name you use. Once a method of payment is agreed and funds requested you will enter a legally binding agreement for the amounts specified. The Programming Historian Editorial Board reserves the right to reject funds from any organization or individual for any reason. The Programming Historian is an international volunteer-driven project whose financial activities are administered by ProgHist Limited, a Not for Profit Company Limited by Guarantee that is registered in England, Company Number 12192946. The purpose of the Programming Historian is to advance the education of the public in the humanities in particular in the use of digital tools and techniques and to promote research for the public benefit in all aspects of that subject and to publish the useful results. Sponsor Us If you represent an organisation or group who are interested in sponsoring The Programming Historian, please contact James Baker to discuss. Sponsorship can be financial, in-kind, or a combination of both. Sponsorship length and value are negotiable. All sponsorship is subject to agreement by the Editorial Board of The Programming Historian. In order to avoid perceived conflicts of interest, safeguard our peer review process, and ensure our academic integrity, the Editorial Board have agreed not to accept the following forms of sponsorship Headline Sponsorship. For example, ‘The Programming Historian in association with..’ or ‘The Programming Historian powered by..’. Individual or Selective Lesson Sponsorship. For example, your logo on a single lesson page or lessons pages about a single tool or set of approaches. Haven’t got any money? The Programming Historian runs on the far-from-endless energy of volunteers, and we want to hear from anyone who shares our interest in teaching digital methods, forging new processes of peer review, and building diversity in the digital humanities community. So if you are unwilling or unable to donate to The Programming Historian, but want to contribute in some way, please see our ‘Contribute to The Programming Historian’ page where we’ve outlined common ways to contribute. Management of Donations and Sponsorship Donations and sponsorship are managed by James Baker on behalf of the Editorial Board of The Programming Historian.