September 2019 Skype call - Editorial Agenda, Monday 30th September

[amsichani]

Monday 30th September 2019 . Time is 9:00 AM - Mexico time; 10:00 AM - EST; 3:00 PM - British time; 4:00 PM - CET. @amsichani will be facilitating the call.

Working agenda follows. Please add by commenting or editing this comment directly.

All team members, please make an effort to close at least 1 ticket assigned to you.

• Current Research Projects or Submissions Pending about the Programming Historian (@drjwbaker to add note about Archivist role here Private Repo #1426)
• Development Team Report
• Technical Report
• Communications Report
• Global Team Report
• Editorial Team setup Editorial Team setup #1328
• ProgHist Ltd report (Incorporated entity: Chairperson for Board of Directors #1403, Add explainer re relationship between the Programming Historian and ProgHist Ltd #1444)
• FR team enlargement FR team enlargement #1394
• ES team Report -planning PH-FR 3M Planning #1469
• Copyediting workflow English Language Copyediting #1381
• Team Survey results (@acrymble)

[mdlincoln]

FYI @amsichani the winning day for our #1430 was September 30th at the usual time, and I've gone ahead and scheduled it - is that going to be OK based on the doodle responses for the editorial team call?

[amsichani]

Hi @mdlincoln thanks for letting me know (I haven't receive a doodle for the TechMeeting;-). Probably we ll go with the 2nd most popular choice here.

[mdlincoln]

🤦‍♂ or... I misread my long list of doodle polls and thought that your poll was the tech poll haha. Belay that... I'll send another one shortly! Looks like YOU get to have monday after all!

[drjwbaker]

Project Development Team Report

By: @drjwbaker
Date: 27 Sept 2019

Actions Completed Since Previous Report:

• made this template for reporting to monthly calls Meeting Report Template #1432
• incorporated as a legal entity Incorporation with Companies House (UK) #1437 and added explainers on the the site Explainers re relationship between the Programming Historian and ProgHist Ltd #1442 (thanks to ES and FR teams for their efforts here). Company begins operating on 1 October 2019.
• opened a bank account Bank account for ProgHist Ltd #1440 Will close issues once login details are confirmed.
• interviews for English ME role.

Actions Remaining Open Since Previous Report:

• a number of open issues arising from Incorporation with Companies House (UK) #1437 many of which will be resolved after ProgHist Ltd Board of Directors meeting 3 October Board of Directors Meeting 10/19 #1439
• agreeing mechanisms for requesting translation that replace our current ad-hoc system Requesting Translation guidance #1458 (nearly done)

Queries for the Team:

• none

6-month focus:

• getting mechanisms in place for receiving money Donation mechanisms #1457 including reopening conversations around sponsorship and other revenue generating activities (e.g. paid workshops)

12+ month focus:

• understanding forward financial planning so that we can plan spending and hire staff.

Further Comments:

• none

[mdlincoln]

Tech Team Report

By: @mdlincoln
Date: 27 Sept 2019

Actions Completed Since Previous Report:

• Broke down alt-text descriptions for lesson galley images #1324 into sub-units of work divided across the team

Actions Remaining Open Since Previous Report:

• Website search Full-text search #1018 will be discussed at November meeting with presentation by @ZoeLeBlanc
• Small addition to footer Add RSS feed link to footer #1224

Queries for the Team:

• Re: Requesting Translation guidance #1458 IT is possible to make PR reviews even more stringent, such that ALL requested reviewers must approve it before it can be merged. Helpful, or annoying?

6-month focus:

• Get entire team up to speed on making minor-to-medium technical changes
• Website search Full-text search #1018

12+ month focus:

• Plan S / DOIs again Plan S implementation #1370

Further Comments:

• Next tech team meeting October 9

[amsichani]

Many thanks @drjwbaker and @mdlincoln for these reports ! May I ask also @jenniferisasi to briefly report on Comms, @JMParr on Global and @spapastamkou on the FR front before our meeting (following this template https://github.com/programminghistorian/jekyll/wiki/Meeting-Report-Template)? Thanks!

[jenniferisasi]

Communications Team Report

By: @jenniferisasi
Date: 29 Sept 2019

Actions Completed Since Previous Report:

• Completed Communication: Blogpost/Newsletter for September #1456 as a continuation of the short-term plan to keep users informed
• Published note on @grandjeanmartin joining the team (by @spapastamkou)
• Publicized search for editorial membres for PH en français on Twitter
• Decided to add a footer for RSS feed Add RSS feed link to footer #1224; project opened by @mdlincoln

Actions Remaining Open Since Previous Report:

• Establish a long term plan for the Communications Team
• Community Survey Issue: Audience and Learning Paths Community Survey Issue: Audience and Learning Paths #1022 for @amsichani

Queries for the Team:

• Can we have an issue open for the newsletter in between publications for people to add accomplishments? For example, once I close Communication: Blogpost/Newsletter for September #1456 I open a new issue till December.

6-month focus:

• Create a plan by/for @amsichani as Education Manager
• Get a Research Impact Manager and create a plan for him/her (awaiting decision at @drjwbaker's institution)

12+ month focus:

• Have a newsletter out every 3 months
• Increase visibility of PH in educational settings

Further Comments:

[spapastamkou]

FR team Report

By: @spapastamkou Date: 30/09/2019

Actions Completed Since Previous Report:

• Fr team enlargement (FR team enlargement #1394): @grandjeanmartin joined the team (welcome blogpost published; onboarding checklist in progress Onboarding Checklist for FR New Editor: Martin  #1448; 3 months task planning PH-FR 3M Planning #1469)
• Translated pages in FR: translator guidelines (Translator Guidelines in French #1389); privacy policy (French translation of privacy policy #1359) @fdlaramee
• 1 translated lesson published: Comprendre les pages web

Actions Remaining Open Since Previous Report:

• Fr team enlargement (FR team enlargement #1394): open call for new members in progress (blog post published, deadline 10 October, 2 candidatures received up to now)
• FR lessons request page: Lesson requests FR page #1431
• Twitter Bot and FR lessons: Twitter Bot and New Languages #1167 (in progress, as we wait for a 6th translated lesson to be published until we can feed the gsheet)
• 2 translated lessons under edition/soon to be edited: ph-submissions issues Updated my bio/interests/team:true #263, Added self as ombudsperson #264 @fdlaramee @spapastamkou
• 1 translation in progress: ph-submissions issue difficulty level needed SPARQL lesson #262 @grandjeanmartin

Queries for the Editorial Board:
Reminder: the question of shadow editing remains open for both @fdlaramee and @grandjeanmartin.

6-month focus:

• 3 months planning for all FR team members, see PH-FR 3M Planning #1469
• Participate to the DH francophone conference in May 2020 in Bordeaux, France (no cfp published yet).

12+ month focus:

• Publish original lessons in FR

Further Comments:

• Marie Puren left the team.

[spapastamkou]

I am likely to miss today's meeting after all, because I might still be in public transports around that time (I need to leave work earlier). If it is the case, I apologize in advance. I just left a report on our activities and @fdlaramee and @grandjeanmartin can provide further info on these.

[rivaquiroga]

ES team Report

By: @rivaquiroga Date: 30/09/2019

Actions Completed Since Previous Report:

• María José's Sabbatical checklist completed (Maria José Sabattical Checklist #1279) @mariajoafana @rivaquiroga
• Translated pages in ES: privacy policy (Spanish translation of privacy policy #1360) @jenniferisasi

Actions Remaining Open Since Previous Report:

• 3 original lessons under edition (#188, #212 & #254) @jamotilla @mariajoafana @jenniferisasi
• 3 translations under review (#163, #173, #205) @jamotilla @vgayolrs
• Finding a new Ombudsperson (complete translations for special terms in new snippets.yml  #443) @rivaquiroga
• @JoshuaGOB & @rivaquiroga shadowing @walshbr on #251 as part of their onboarding process. The lesson is soon to start the reviewing process.
• Publish Translation Guidelines (Guía para Traductores + Wiki #1424) @rivaquiroga
• Follow up with Bogotá Workshop participants to inquire about their tutorials @rivaquiroga

Queries for the Editorial Board:

6-month focus:

• 3 months planning as team and for all members, following the model of FR team PH-FR 3M Planning #1469

12+ month focus:

• Will be defined after next team meeting

Further Comments:

• María José Afanador started her sabbatical this month. She will keep her rol as an Editor for the two open tickets she was working on (/Propuesta - Construir un repositorio de fuentes históricas con Omeka Classic ph-submissions#188 & Ticket de revisión "Introducción a Map Warper" ph-submissions#212)
• @rivaquiroga started as Managing Editor of the ES team this month.
• Next team meeting should take place during October

[JMParr]

Global Team: I have created a Wiki page for our Global Team, and have been working on a list of contacts. I plan to reach out shortly to the other members of The Global Team for assistance in making contact. (Separately, are there any team members who speak Italian? I know a little, but I'm very rusty.) I have also spoken to my colleague who has been working in Rwanda about the possibility of working on a grant to do a DH workshop there. She hasn't had the bandwidth to discuss either logistics or grant writing further, but I hope to have a conversation later this spring. Finally, I will be sending out an email to the Global Team members later this week, about arranging our quarterly call later this week.

…

On Mon, Sep 30, 2019 at 9:53 AM Riva Quiroga ***@***.***> wrote: ES team Report By: @rivaquiroga <https://github.com/rivaquiroga> Date: 30/09/2019 Actions Completed Since Previous Report: - María José's Sabbatical checklist completed (#1279 <#1279>) @mariajoafana <https://github.com/mariajoafana> @rivaquiroga <https://github.com/rivaquiroga> - Translated pages in ES: privacy policy (#1360 <#1360>) @jenniferisasi <https://github.com/jenniferisasi> Actions Remaining Open Since Previous Report: - 3 original lessons under edition (#188 <programminghistorian/ph-submissions#188>, #212 <programminghistorian/ph-submissions#212> & #254 <programminghistorian/ph-submissions#254>) @jamotilla <https://github.com/jamotilla> @mariajoafana <https://github.com/mariajoafana> @jenniferisasi <https://github.com/jenniferisasi> - 3 translations under review (#163 <programminghistorian/ph-submissions#163>, #173 <programminghistorian/ph-submissions#173>, #205 <programminghistorian/ph-submissions#205>) @jamotilla <https://github.com/jamotilla> @vgayolrs <https://github.com/vgayolrs> - Finding a new Ombudsperson (#443 <#443>) @rivaquiroga <https://github.com/rivaquiroga> - @JoshuaGOB <https://github.com/JoshuaGOB> & @rivaquiroga <https://github.com/rivaquiroga> shadowing @walshbr <https://github.com/walshbr> on #251 <programminghistorian/ph-submissions#251> as part of their onboarding process. The lesson is soon to start the reviewing process. - Publish Translation Guidelines (#1424 <#1424>) @rivaquiroga <https://github.com/rivaquiroga> - Contacting Bogotá Workshop participants to inquire about their tutorials @rivaquiroga <https://github.com/rivaquiroga> Queries for the Editorial Board: 6-month focus: - 3 months planning as team and for all members, following the model of FR team #1469 <#1469> 12+ month focus: - Will be defined after next team meeting Further Comments: - María José Afanador started her sabbatical this month. She will keep her rol as an Editor for the two open tickets she was working on (/ programminghistorian/ph-submissions#188 <programminghistorian/ph-submissions#188> & programminghistorian/ph-submissions#212 <programminghistorian/ph-submissions#212>) - @rivaquiroga <https://github.com/rivaquiroga> started as Managing Editor of the ES team this month. - Next team meeting should take place during October — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1449?email_source=notifications&email_token=AFNO4WYCBMRXX2EBFADOTDTQMIAF7A5CNFSM4IXCWQT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD75W3LQ#issuecomment-536571310>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFNO4W6OAFH44QUA3NBHBS3QMIAF7ANCNFSM4IXCWQTQ> .

[drjwbaker]

Thinking about this meeting, I guess we need to get used to thinking about what we want to put in the 'Queries for the Editorial Board' bit of the template rather than - as we had previous - going through by open ticket that needs Editorial Board input. Our meetings should be room for reporting and discussing (as we did on the copy editing issue).