/tg/Station 13

For administrative measures, MSO has the ultimate authority. Typically he lets democracy do it's thing through the headmins, but every now and then we'll see some activity on his part to bring about some change. Recent/relevant ones which come to mind are Rule 11 and FNR rule 10.

Assuming you become headmin, how do you plan to work with MSO? Say he feels passionately that a change should occur and you disagree, how would you approach this? Vice versa too, you want a change which he disagrees with.

This thread is also completely open to MSO himself and current and former headmins. What did these interactions look like in the past? How did the aforementioned rules come about?

From what I've seen, MSO treats adminbus with respect, which is the most important thing to me, and that what MSO wants for adminbus tends to be reasonable. I agreed with Rule 11's enactment, for instance.

I have worked with MSO well directly in the past, the most recent one being 2FA for admins, which had recurring approvals between me and him. I'm a member of ops-bus (though I'm not nearly as active in there as I'd like), and I did well as a key holder under him for my entire tenure there. I like to think that whatever the end outcome is between a dispute of MSO and the head admin team is, it will at least be something people won't get upset about.

MrStonedOne lets be friends I already forgot about the great secborg incident of 2017 lets just do some chillin' and killin'

This is a difficult question for me to answer because I haven't worked that closely with MSO in the past. I don't have any problem with the rules you brought up, nor how he's dealt with the admin team.

I think if it came down to a disagreement like you're describing, I would do my best to reach a compromise. If a compromise absolutely could not be reached, I would accept the outcome.

I've worked with MSO on a few projects, most notably the marathon rounds and the debate, evidence and implementation of rule 11.

We have good natured debates on a lot of topics and we've had a great relationship ever since we were trialmins together

Think carefully before answering. Make sure answer represent whole picture.

As codebase maintainer, occasionally clash with MSO. Creative endavours & conflicting viewpoints. Nature of beast.

Both goals same - Success of project. Path to accomplish different.

When talking Poes & MSO, never more than one DM away from solving problems. Have done in past, continue to do so at present. Communication key to success.

As admin, MSO quick to respond to query. Never have single problem. Work together, recent example stickyban issues.

Work together, share details, come to solution. Ask MSO for permission to remove erroneous bans. MSO set out guidelines to follow, grant permission to do so.

In any team, disagreements expected. Conflict expected. Self-awareness to know when to hold ground, compromise or back down entirely. Learn more about when to choose either option with every passing day of life.

As headmin - MSO's servers, MSO's rules. Advocate for beliefs with that context in mind.