Contribute to the Programming Historian

The Programming Historian runs on the energy of volunteers, and we welcome contributions from the community. Please consider the following ways to get involved, or let us know about other ideas you have for broadening participation.

Write a new lesson

We welcome submissions of new lessons from authors!

Writing a tutorial is one of the best ways to teach yourself particular skills and actively engage in the digital humanities community.

We don’t simply accept or reject articles like traditional journals. Our editors collaborate with you to help craft and hone your topic and approach, as well as to make your tutorial as clear and as useful as possible. Our peer review process helps improve your lessons even further, as well as improve your technical writing skills. Please read more about our submission process.

If you’d like to propose a lesson (for you or for someone else to write), email Jeri Wieringa.

Join our team of reviewers

Academic peer review is essential for producing trusted high-quality resources. The Programming Historian, holds peer review in the highest regard, and we take an open and collaborative approach in which reviewers get full and public credit for their work. For more on our review philosophy and procedures, please see the Guidelines for Reviewers.

We hope you’ll consider joining our team of reviewers. The time commitment is flexible, and you’ll be contributing to helping us maintain high academic standards for this community resource. Please email Jeri Wieringa to introduce yourself and let us know about the specific skills, tools, topics, and technologies that you’d like to be involved with so that we can send you the most appropriate lessons to review.

Do Editorial Work

Our editorial board members help facilitate peer review and work with authors closely to make improvements to their lessons. Our guidelines for editors is meant to ensure that everyone, from authors to reviewers to members of the wider community, receive a fair and consistent experience during peer review.

From time to time we may advertise that we are seeking more editors.

Provide feedback and report problems

We welcome feedback on any aspect of the Programming Historian. Let us know what we can do to make the project better!

We are especially grateful for tips about lessons that seem to be broken. As URLs change and as new versions of software and platforms are released, lessons develop glitches over time. Please help us keep the Programming Historian up to date by letting us know about these when you come across them in the course of your reading.

Add us to your Library Catalogue

This project is our attempt to demonstrate what open access academic publishing can and should be. Please help us spreading the message and providing the widest possible access to this resource by asking your librarian to include the project in your library catalogue.

The Programming Historian has a listing in WorldCat (with thanks to the University of Purdue library and Amanda Visconti) and is indexed by the Directory of Open Access Journals.

Or Get in Touch

No matter how you’d like to be involved, you can always email Jeri Wieringa with any comments, questions, complaints, or suggestions. We endeavor to respond to all emails promptly.

Thanks for your help in improving The Programming Historian!