Communication Team

In order to improve the communication strategies of The Programming Historian a new role was created in April 2019. The Communication Manager's role is defined as "Responsible for managing and developing communication channels".

In order to ensure that the Communication Manager process is smooth and organized, this page provides details that the team should consult each time a new communication or outreach process is incorporated or a handover is due to take place.

The Communication Manager is in charge of:

• The @ProgHist Twitter account
• Adding new editorial members as team members in the Twitter account
• Thinking about ways to do outreach beyond Twitter
• Sending an informational email to DH mailing lists twice a year
• Helping the team understand how to promote the project better
• Finding funds to have stickers and other things for conferences
• Having ownership of the blog to:
  • decide how regularly we publish
  • publish a post with updates every three months
  • improve its usability
• Ensure the multilingual setup of the communication strategies
• Edit The Programming Historian Wikipedia page

We have traditionally made this a 1-year role, from April to April. The following people have acted as Communication Manager and may be consulted for advice:

• Jennifer Isasi (2019- )