New Publications Policy

The Programming Historian is controlled entirely by the central Project Team, comprised of all active members of the project team. In order to ensure that the project continues to thrive, we expect all language sub-teams (English, Spanish, French, etc.) to adhere to the following principles:

• The sub-team is required to adhere to the author, reviewer, editor, and technical guidelines at all times. These guidelines can only be amended by the central Project Team.
• The sub-team is required to adhere to the CC-BY license at all times.
• The sub-team is required to participate actively in the central Project Team.
• The central Project Team reserves the right to replace or amend the membership of a sub-team if it is becoming unsustainable or if it believes that the sub-team will not be able to continue the project to the level that we expect of The Programming Historian.

Translation is not purely a matter of converting lessons from English into another language. The Programming Historian is a multi-lingual project involving a large team, and so translation requires extensive teamwork and coordination across our editorial team. New language sub-teams joining the project to translate existing material and with an aim of producing original content should be prepared to adhere to the following additional principles/requirements:

• A team of at least 3 editors, from more than one country who are committed to the project for at least two years. At least one member should have substantial experience with translation. Please note that due to our Project Team diversity commitment, we may insist on a certain number of members from different countries, and of different genders. We advise getting in touch with us before attempting to put together any teams as we may know of other people considering a similar translation.
• A willingness of the team to engage productively with the existing multi-lingual Project Team, including contributing actively to monthly Skype meetings.
• A commitment to our peer review system using Github and peer review for all translations and new lessons, using the workflows adopted by the rest of the team.
• A commitment to translating and maintaining the translations of all non-lesson pages on the site as the project evolves and as policies change over time. This includes but is not limited to the following pages, which must be translated before any lessons can be hosted:

1. the Front Page
   

2. About Page
   

3. Author Guidelines
   

4. Contributor Guidelines
   

5. Reviewer Guidelines
   

6. Editor Guidelines
   

7. Lesson Retirement Policy
   

8. Project Team
   

9. Research Outputs
   

Some pages, text snippets, and messaging (particularly on the blog or social media channels) may include original messaging pertinent to a given language publication. These will be decided on a case-by-case basis, and will be used to encourage engagement with one's language community in appropriate ways, such as through marketing strategies tailored for different audiences.

Anyone interested in proposing a new translation initiative is invited to contact our Global Lead https://programminghistorian.org/en/project-team in the first instance to discuss the idea informally. We look forward to hearing from you.

--

Information for the Project Team board upon deciding whether or not to take on a new publication:

Agreed that new publications are great for the project but require a huge effort across all teams. Agreed that the remit for new publications falls with the Global Team but that all team leaders must sign off that their team can commit the necessary resources before any new publications are approved. This does not affect the Portuguese publication but will affect all future publications. Decision taken May 2020.