Service Integrations

While the content of The Programming Historian is tracked and hosted on GitHub, we do use several non-GitHub services to aid our editorial and publishing process.

Gmail

• [email protected] (please do not email this box as it is not monintored)
• purpose: to provide a shared email box that these service integrations can be linked to.
• maintained by @acrymble and linked to his phone number. Recovery email address is [email protected]
• at present the following people know the password: @acrymble, @drjwbaker, @walshbr, @amsichani, @mariajofana. Any team members who want to know please contact one of those people (you are all welcome to know it)

Google Groups

• [email protected]
• purpose: for internal emails only for members of the editorial board
• Connected to [email protected] account.
• maintained by @jenniferisasi.

Additional Google Groups for teams:

• [email protected]

• purpose: for internal emails of Project Development Team

• maintained by @acrymble.

• [email protected]

• purpose: for internal emails of English Publication

• maintained by @svmelton.

Directory of Open Access Journals (DOAJ)

• purpose: to provide catalogue entries of lessons that can be added easily to library catalogues.
• maintained by: @drjwbaker
• notes for transfer

1. March and September each year.
2. Login in at https://doaj.org/publisher/ (linked to [email protected])
3. Sort existing entries by date at DOAJ (e.g. https://doaj.org/toc/2397-2068) and identify new lessons: for EN https://programminghistorian.org/en/lessons/?sortType=date&sortOrder=desc, for ES https://programminghistorian.org/es/lecciones/?sortType=date&sortOrder=desc
4. Manually enter at https://doaj.org/publisher/metadata. Be sure to note volume number from 2019 onwards (note done for 2018 as volume numbers implemented half way through the year). For abstract, use a logical combination of header abstract and introduction.

Travis CI

• purpose: Dead link and YAML checking
• maintained by: @ZoeLeblanc
• notes for transfer: No password needed. New admin would need to authorize Travis CI to access their GitHub account.

Netlify

• purpose: live web previews of pull requests
• maintained by: @ZoeLeblanc
• Login is limited to the technical team lead (for maintenance) and the finance manager (for paying occasional charges for build minutes, etc.)

Twitter

• purpose: to tweet about news and content
• maintained by @acrymble, @walshbr (administrators)
• All members of the editorial board should have tweeting access. contact @acrymble if you don't.
• The account is linked to the following email: [email protected]

Twitter bot

• purpose: Pre-compose tweets
• maintained by: @walshbr (with @mdlincoln and @jerielizabeth as collaborators on Heroku account)
• notes for transfer: App is hosted at Heroku, which requires a Heroku account (currently linked to the Programming Historian gmail). The app uses Twitter credentials (the ProgHist Twitter account) as well as a Google Sheets keychain that exists can generated from the Google Cloud Console - instructions on the repo for the Programming Historian Bot. New admin would need to generate new custom keychain for Google Sheets, and ensure they have push privileges to Heroku.

Google Analytics

• purpose: Monitor site traffic
• maintained by: @acrymble, also linked to [email protected] account
• notes for transfer: New administrative access and user management accessible via the above email account.

Domain Name

• purpose: Gives us the custom url programminghistorian.org
• maintained by: Jessica Otis [email protected]. If contact required, email Jessica cc'ing [email protected] (center administrator) or [email protected] (systems administrator).

Cloudflare

• purpose: Provides HTTPS
• maintained by: @mdlincoln
• notes for transfer: Current admin removes programminghistorian.org from their Cloudflare account, allowing a new admin to add it to their Cloudflare account.

Zenodo

• purpose: deposit location for project citation.
• maintained by: @drjwbaker
• notes: annual (each November). Use process at https://guides.github.com/activities/citable-code/ to create a deposit from https://github.com/programminghistorian/jekyll. Latest deposit at https://doi.org/10.5281/zenodo.3525082.

Patreon

• purpose: accepting donations
• maintained by: @drjwbaker, linked to [email protected] account
• notes: password same as DOAJ (@acrymble knows this as well). Linked to Paypal for scheduled check out 5th of each month.
• activities:
  • @drjwbaker emails @jenniferisasi a list of supporters every Monday morning London time, @jenniferisasi then tweets the list Monday morning US central time
  • @drjwbaker curates a list of supporters and shares it with @jenniferisasi on the ticket for the newsletters
  • @acrymble to request list of 'Patron' tier supporters who can suggest lesson topics.

Paypal

• purpose: accepting donations and processing Patreon
• maintained by: @drjwbaker, linked to [email protected] account
• notes: password held by @drjwbaker. If you need to get in, do a password reset via [email protected].

YouTube

• purpose: publishing PH workshop video materials
• maintained by: @mariajoafana, linked to [email protected] account
• notes: password same as gmail account

Private repo for management of project and business documentation

• purpose: archive of project (e.g. bids or internal surveys) and business (e.g. incorporation) documents that we deem necessary to keep private from the public but to which the Editorial Board need periodic access (e.g. when writing bids, talks, or papers) https://github.com/programminghistorian/project-and-business-archive
• maintained by: @drjwbaker
• note: document containing sensitive and private financial information are held offline, a listing for which is at /project-and-business-archive/business/Finances/. Access requests can be made by contacting @drjwbaker.