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

The decentralized web is about trust. You should only join Friend Camp if you personally trust Darius Kazemi with your social media data. You probably only have that level of trust if we are IRL friends or have been internet friends for a long time. Generally speaking this is a small, closed community. In the end, Darius is the arbiter of what is allowed here. If you don't have a good idea of the kind of behavior that flies with Darius, again, you probably shouldn't join this instance. In the interest of specificity, we do have a code of conduct and privacy policy which you should read. Friend Camp features several modifications that were requested by our users. * you can log in via any subdomain, which means you can log in to multiple accounts in the same browser session (for example, log in once on and then as another user on * they are no longer called "toots", they are now "posts" * if you have a locked account and you get a follow request, a reminder appears under your "post" button (on normal Mastodon mobile it is otherwise buried in a sub-menu and you might not see it for a long time) * the emoji dropdown is a neutral smiley face instead of the cry-laughing smiley @mentions are rendered as "@user" for a Friend Camp user and "@user@domain" for remote users. This helps clear up when you follow two people who have the same username on different servers. * there is a "never ask me again" checkbox on the confirmation for clearing your notifications -- more info here * When an mp3 link is in a post, we also embed an inline mp3 player. git commit here * 500 characters of profile text git commit here, requested by @deerful Important Bit from the Privacy Docs: If you want decent privacy (the info doesn't leave this server), the only way to do that is to set your account to private, only accept friend requests from other users, and only ever @ mention other users. Once you start talking to people on other servers, all bets are off. Any private message you send to someone on another server could be looked at by the admin of a different server. This is kind of like email: if you are on a private email server, and you send an unencrypted email to a gmail account, congrats, Google now has the content of that email. But also, you do this every day, so, hey. The internet! Our beautiful icon is based on photo3idea_studio from, licensed CC 3.0 BY. It has been modified by!