Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Brandon Walsh Retirement 😭 #2214

Closed
ZoeLeBlanc opened this issue Jul 28, 2021 · 10 comments
Closed

Brandon Walsh Retirement 😭 #2214

ZoeLeBlanc opened this issue Jul 28, 2021 · 10 comments
Assignees

Comments

@ZoeLeBlanc
Copy link
Member

Sadly our beloved @walshbr is retiring at the end of the Summer!

As far as I can tell the only remaining open ticket assigned to you is #2072 which we'll discuss at our Summer meeting (hopefully next week).

A few other remaining things that I'm sure you're already on top of Brandon is making sure we hand over any of your remaining duties, remove you from any documentation so that you don't get unnecessarily pinged, and then I wonder if we should do some type of exit interview 🤔 (just a thought though!) .

Regardless just wanted to start this ticket off to make sure that we kept track of anything related to your retirement ❤️ .

@walshbr
Copy link
Contributor

walshbr commented Jul 28, 2021

Happy to do an exit interview if ya want - @svmelton had talked about it as well, and we could do the two together if you want. This is the full checklist:

  • Remove Google Groups access (@jenniferisasi)
  • Remove Google Analytics access (@acrymble)
  • Remove Github Jekyll access (@ZoeLeBlanc)
  • Remove from ProgHist Ltd register of members (@drjwbaker)
  • Remove Twitter access (@jenniferisasi)
  • Change team: true to team: false, and add team_end: YYYY to the _data/ph_authors.yml file to remove the person from the Project Team page (@acrymble)
  • Check that they have no open issues assigned to them on either the Jekyll repository or the Submissions Repository (team leader).
  • Review service integrations page to ensure that they do not have any associated integrations tied to their accounts (@mariajofana).
  • If they hold any other team roles, inform @mariajofana that a replacement is needed.
  • Finalize Twine Lesson publication
  • Discuss Accessibility Audit #2072 with tech team
  • debrief with @ZoeLeBlanc and @svmelton

I do have one lingering lesson editing that's still in the pipeline, so I think we might not want to actually take steps on these until, say, the third or fourth week of August? I'm not sure the lesson will be done by then, but I think I should be able to carry out those duties after the summer's end (might be slightly easier if I still have push access though).

@drjwbaker
Copy link
Member

drjwbaker commented Aug 2, 2021

@walshbr I note you are an admin on the repo https://github.com/orgs/programminghistorian/teams/administrators Do we need to nominate someone to take over this or are 4 people enough?

@walshbr
Copy link
Contributor

walshbr commented Aug 2, 2021

That'd be up to @ZoeLeBlanc I think. I believe ML (when he was technical lead) wanted to have fewer folks as admins, and I was only added later for whatever particular work I was doing at that time.

@drjwbaker
Copy link
Member

ML did. Happy to @ZoeLeBlanc to make the call if having a second @programminghistorian/technical-team person as repo admin is useful.

@walshbr
Copy link
Contributor

walshbr commented Aug 5, 2021

@svmelton I just moved the last lesson I'm editing along to copyediting. So I think we should be good for going ahead with the rest of these now that that piece is moving through the finale stages and we have a tech call scheduled to discuss the last open ticket on my plate.

@svmelton
Copy link
Contributor

svmelton commented Aug 9, 2021

Thank you @walshbr!! We're going to miss you :(

@walshbr
Copy link
Contributor

walshbr commented Aug 23, 2021

@jenniferisasi @acrymble @ZoeLeBlanc @drjwbaker just a note to start checking off these items. I'm meeting with the tech team tomorrow to discuss the last things I'd been working on with them, so might be good to wait until after that to remove my push access to the repository. But other than that I'm sailing away.

@walshbr
Copy link
Contributor

walshbr commented Aug 23, 2021

DM'd @svmelton and @ZoeLeBlanc about a debrief if they wanted it. We've got one scheduled.

@walshbr
Copy link
Contributor

walshbr commented Aug 24, 2021

Opened #2233 to remove me from the project team page (no need to make @acrymble do it for me).

@ZoeLeBlanc
Copy link
Member Author

Closing this since @walshbr is officially retired 😭 ! We miss you Brandon ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants