November 2019 Skype call - 25 November- Editorial Agenda

[amsichani]

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

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

All team leaders please post a small report on your team's activities closer that day.

• Current Research Projects or Submissions Pending about the Programming Historian
• Development Team Report
• Technical Report
• Communications Report
• Global Team Report
• Editorial Team
• Plan to work through stuck issues / old issues in the next month Action SM
• ProgHist Ltd report
• EN report - SM
• FR team Report
• 3 candidates applied to join the team, to be interviewed Nov 2019 - Action SP.
• ES team Report
• RQ in Chile during unrest, may need extra support. Action JI, JOB contact her
• Spanish team capacity query. A lot of long-term missing people. Action AC to liase with RQ.
• Internal Communications Internal Communication #1491 & Decision making Edit governance doc to better fit sub-team structure/powers #1543
• Action: Team leaders to decide together how to deal with internal communication to ensure their team memers are aware of relevant tickets.
• Edit governance doc to better fit sub-team structure/powers Edit governance doc to better fit sub-team structure/powers #1543

Call frequency and subteams.

[acrymble]

@amsichani since we now have minutes and actions from the last meeting, can we find a quick way to make sure everyone with an action reports on it or otherwise lets us know it needs more input? Otherwise the actions are meaningless.

[amsichani]

thanks for this @acrymble . I ll work on this and get back to the team as soon as possible

[jenniferisasi]

A quick note that Nov 28th is Thanksgiving here so all of us in the US will be out of the office and, most likely, celebrating the day with family/friends.

[walshbr]

Would be good to revisit this note - #1302 (comment). We had discussed in the past the possibility of staggering full board meetings starting in September once more of the sub boards were in place so that we weren't all planning on both monthly editorial board skype calls and monthly sub team calls.

[acrymble]

Related to @walshbr we also said that we only expected team leaders to come to these meetings. Everyone else's participation is o ptional (but we would prefer to know if you aren't planning to come). Do we want to continue with that approach?

[walshbr]

I'll mention this on the call, but opt-in for everyone required for leaders does seem to be the most sensible. That way people with the time and energy who want to be as engaged as possible can still have that option. Also in keeping with the general ethos of transparency.

[drjwbaker]

Project Development Team Report

By: @drjwbaker
Date: 20 Nov 2019

Substantive Actions Completed Since Previous Report:

• Proposal for donation mechanism. Went ahead and started Patreon/Paypal work Donation mechanisms #1457
• Ticket on business models we are happy with for fundraising What Business Models are we Happy with? #1487. In sum we agreed:
  • directly monetizing the content through subscriptions or advertising is unpopular with some people.
  • donations are fine within some limits - suggesting charity rather than business is the ethos some people have in mind.
  • workshops and training are a possible route for monetizing activity.
  • other options remain open to us.

Substantive Actions Remaining Open Since Previous Report:

• 2-month funded Impact Manager post. Job now up: https://www.sussex.ac.uk/about/jobs/research-assistant-impact-manager-prog-hist-2753. Deadline 3 Dec. I am receiving queries from potential applicants. Funded Impact Manager Post #1489
• Opened ticket (from discussion at previous call Internal Communication #1491) on editing governance to reflect our team structure to be discussed today under specific item
• Patreon plan for next 6 months Patreon Integration (stage 2) #1554
• start of plan to manage copyediting hires (once we have some £#$¢) Managing Copyediting Hiring #1537

Queries for the Team:

• none

6-month focus:

• maturing mechanisms in place for attraction 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

[amsichani]

I 've added actionable items from last meeting minutes under related items/teams in the agenda - hopefully, the teams' reports for this meeting and discussion during the call will address these.

[fdlaramee]

Apologies; a medical appointment will keep me away from this month's call.

All the best,
FDL

[mdlincoln]

Technical Team Report

By: @mdlincoln
Date: 20 Nov 2019

Substantive Actions Completed Since Previous Report:

• Discussed and drafted an issue triage and workload balancing guide: https://github.com/programminghistorian/jekyll/wiki/Technical-Team#issue-triage-workflow It will include guidelines for editorial team bug reports and issue requests, and describe how we will assess and prioritize complex feature requests.
• Received report from @ZoeLeBlanc on full-text search of lessons. We decided on a path forward to search lessons within each language group, and Zoe will be working on a draft implementation
• Merged alt text pr Add avatar_alt text to lesson header images #1357

Substantive Actions Remaining Open Since Previous Report:

• Plan S / DOI mechanics still ongoing Plan S implementation #1370

Queries for the Team:

• Any comments on our issue triage plan?

6-month focus:

• Have a finalized issue triage workflow plan
• Finish implementing site search

12+ month focus:

• Implement article metadata and DOIs compliant with plan S

[svmelton]

EN Editorial Report

By: @svmelton
Date: 21 Nov 2019

Actions Completed Since Previous Report:

• Recently published - Beginners' Guide to Twitter Data

• Retired SPARQL lesson Retire SPARQL lesson #1541

• Created kanban board to manage editorial workflow

Issues still in process:

• possible bug in "using geospatial data" #1181 is close to being fixed. @svmelton ran into issues while testing the lesson and the author is revising and will submit a PR to fix.

• Jupyter Notebooks lesson is at the managing editor stage, awaiting question on broken links

• Working with Batches of PDF Files is in author revision stage

Queries for the Team:

• Reaching consensus about Jim Clifford proposed lesson and its potential relevance to sudo pip install in intro to beautiful soup #1557

[svmelton]

FYI, I will need to leave about 30 minutes into the call for another meeting.