I'm looking for literature (articles, blog posts, books) that covers "succession planning" for IT/sysadmin in activist groups. Like, for a volunteer group, what happens if your IT person just leaves? What are best practices so that the group isn't locked out of their web hosting etc (simply through lack of information rather than malice on the previous IT person's fault)

In my experience, succession planning in volunteer groups is poor, even in techie groups I've seen people fall massively foul of this.

Long time since I read it but it sounds like something that should be covered in one of the later chapters of The principles of Systems and Network administration by Limoncelli and Hogan.

(It covers a number of such topics including full chapters on hiring sysadmins, firing sysadmins, "being happy" and a lot more. I even think there is a chapter on managing management.)

@eitland @darius Hah, I read the initial question and my first thought was “I bet Tom (Limoncelli) would have something useful to say about this.” :-)

@darius "The Practice of System and Network Administration", by Thomas A. Limoncelli and Christine Hogan, is full of good advice. The "firing system administrators" chapter seems relevant.

@darius I wonder if @vladt might have some ideas ... I'm sure he's been through a few cycles of that.

@edsu @darius
I dont know about specifically IT related issues - most activist groups I worked with did not have dedicated IT people per say. However, we had a number of situations where people hijacked social media accounts and did develop techniques to reduce risk of that from happening.

Sign in to participate in the conversation
Friend Camp

Hometown is adapted from Mastodon, a decentralized social network with no ads, no corporate surveillance, and ethical design.