Open a wiki page documenting how to start up a new language section

[mdlincoln]

• copying existing directory tree for a language to a new named branch
• how to update the snippets file
• adding logos
• ...?

[amsichani]

In order to work more efficiently on this, I think it's wiser to create at least three subcategories at this wiki page , mainly corresponding to different teams within the project. The lead of each team should have an overview of the process and check in with the New Publications manager (@JoshuaGOB ) and the managing editor/ contact person of the new publication.
This is a living document and we will update it constantly.

• administrative tasks (team development team) - data mainly from Portuguese Title Checklist #1710

• register an ISSN with the British Library.

• translate all core pages.

• onboard all new publication members - see https://github.com/programminghistorian/jekyll/wiki/Onboarding-Checklist-for-New-Editors

• add all new publication members's bios to the PH Project Team page (including a small black and white headshot).

• Select a new publication Team Managing Editor (should be prepared to serve at least a year)

• Select a new publication Team Ombudsperson (should be prepared to serve at least a year).

• Communicate the Managing Editor and Ombudsperson selections to @acrymble and make sure that they are identified on the website.

• Create a blogpost and tweets to announce the new publication; this will call for translators/reviewers

• provide managing editor training (shadowing) and partner them with an existing managing editor for mentoring.

• provide shadowing opportunities to all incoming editors

• logo for project

• colour-scheme (sympathetic with our existing colour scheme).

• technical tasks (technical team)

• copying existing directory tree for a language to a new named branch

• how to update the snippets file

• adding logos

• communication tasks (communication team)

• link a member of the new publication team with @programminghistorian/communication-team lead in order to help with translations of comms/ original comms

[acrymble]

@amsichani is this a guide for new teams AFTER a publication has been approved? I'm thinking of #1718

[amsichani]

hi @acrymble , I think yes, its a guide for new teams after the publication has been approved. I am not sure whether we have decided to have a more formal way of approving a publication at this point, but as far as I know the Portuguese team are now working towards their infrastructure. So I guess #1718 would be step 1 and this ticket /tasklist would be step 2 of an onboarding process of a new publication. @JoshuaGOB what you think?

[jenniferisasi]

Just chiming in as I saw it on my email, I guess it will also serve as a pointer to new teams when they contact us (wiki-see all that you would have to do), and before we do #1718, no?

[amsichani]

I agree @jenniferisasi . Its best to have something on our wiki for potential teams willing to undertake a whole new publication instead of answering individual emails every now and then.
I think it will also facilitate the role of the new publications manager @JoshuaGOB , and will formalise procedures and necessary tasks. I am all in favour of making guidelines that will make it easier for our responsible team member to simply follow than re-inventing the wheel - it also adds more transparency and efficiency in our processes.

[acrymble]

Is @JoshuaGOB involved in this too? I definitely see that there are technical elements that need documenting, but this also heavily involves his role in onboarding the new team. Can we make sure those conversations across teams are happening? And can you let me know if we need help to facilitate that?

[amsichani]

yes, @JoshuaGOB should be /is definitely involved in this, esp with his experience with the PT team and as New Publications manager.
Also, I want to invite @programminghistorian/french-team and @programminghistorian/spanish-team managing editors and team members to add here crucial steps/tasks based on their own experience, so we can create a full list of requirements. It would be great if we can collect all comments by 10 June, so we can then draft & proceed with the wiki page. I am also thinking that we can collaborate with @acrymble and also write a blogpost on this, for teams/people willing to initiate a new language publication and also remind them the ad -hoc translation option.