-
Notifications
You must be signed in to change notification settings - Fork 229
Communication Team
In order to improve the communication strategies of The Programming Historian the Communications Team was created in June 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
- The form and content of the website
The Team Development Manager is the human resources wing of the project, responsible for ensuring that everyone on the team is well supported and able to contribute actively in a way that works for them. This person will be responsible for "onboarding" new members of the team (except for new publications, which are the remit of the 'new publications manager'), and for helping them find tasks that let them build their autonomy and contribute to the project. They are also responsible for ensuring no member has more than two "roles" within the project.
They will also be responsible for managing sabbatical checklists, re-integration after sabbaticals, and transitioning people off of the project due to retirement.
The role of the Project Manager at Large is to keep the team focused on achieving its goals. In practical terms this involves running the bi-monthly Skype calls of the project team, and ensuring open tickets are actioned efficiently and in a reasonable time span. Their job includes identifying a need for extra support or assigning unassigned tickets to someone on the team for actioning. This vital role ensures that we continue to meet our objectives and work efficiently as a team. This is a monthly task.
The Education Manager is responsible for the overall educational aspects of The Programming Historian. This includes:
- ensuring the educational character of the project
- assessing and addressing the educational needs of diverse users and communities of practice
- ensuring a creative, supportive, diverse and inclusive educational environment
- enhancing the integration of its lessons into existing curricula
- network The Programming Historian with other open educational initiatives
We have traditionally made these 1-year roles, from June to June. The following people have acted in the signaled capacity in the Communications Team and may be consulted for advice:
- Communication Manager
- Jennifer Isasi (April 2019- )
- Education Manager
- Anna-Maria Sichani (June 2019- )
- Team Development Manager
- Adam Crymble (2019-2020)
- Abolished from 2021
- Project Manager at Large
- Maria José Afanador Llach
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Funding
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees