Tag Archives: Mastodon

The first #ForkTogether meeting, and what went wrong

On the 30th of June, we had the first Fork Off Together meeting, for which the goal is to fork off from the Mastodon project. The idea had been simmering for a while, and the required logistics was a lot bigger than one person could do on their own, yet, I tried to do it on my own.

Let me explain, I was not doing it on my own per se, but rather I was doing a lot of the preparations for this one meeting alone, even if I had two people that I worked fairly tight with, at one point my head just got too tired to properly communicate with others about what help I needed, so it more or less got easier to “just do it myself”, or ask my live-in boyfriend for help, as I could point and grunt at things, when words wouldn’t come out properly.

So, what went wrong with the first meeting?

To start off, over all it was a good experience, but we definitely had some teaching moments which we seemed to, as a group, react well to.

However, I want to start by pointing out what went wrong from my side ie what I could have done better or different. This isn’t about placing blame, but rather a reflection on why I did it the way I did.

So, my initial idea was based on something that I had experienced and learnt when I was active in the Pirate Party here in Sweden between 2009-2014. The organization had a way, which is common (from my understanding) for certain types of organizations, namely the type that has a lot of smaller organizations under the same umbrella. Eg. political org or youth organizations that wants to try and get funding for their work locally.

Having this kind of meeting, is a way to make it easy to start up one of those new small orgs, only requiring 3-5 people, and being youth orgs it meant that they could get a little money from the government. This also doubles as a means to encourage youth to get engaged in activities which will in the long run keep them too busy and away from crime, (but don’t quote me on this, this is just my general understanding of the concept).

What I tried to do was leverage that knowledge I had, to have our own startup meeting, and jeebus I had to try really hard to not accidentally use that term.

In the political org case, it was easy to adopt the same bylaws, coc, operational plan etc. because we were all part of the same organization. This was definitely my first mistake.Unfortunately I didn’t mentally connect the dots until the actual meeting, and I couldn’t have done it different at the time.

I need to highlight here, that the accepting the bylaws and things during the first meeting of this kind was based on it being a sub-association of a bigger org. There wasn’t supposed to be a need to do to much with the bylaws and if there was it would’ve been done before the meeting.

In my foggy mind I didn’t get this out in time and worded correctly. Heck, I had even said “no we won’t draft bylaws” before I realized the translation in full. I could have, and probably should have, checked myself when I realized that that document translated to bylaws. But I didn’t.

Another member of the meeting wrote some good reflections about this type of meeting too.

If that was my first mistake, what was my second one?

I thought that I could distance myself from responsibility and active choices by leveraging that I was just inviting people to a meeting. I didn’t want to make decisions for us, and this was the only way I knew how.

This isn’t as much a mistake as it is paradoxical. Mostly because either way I make decisions and it becomes a really weird situation. Especially if I couldn’t get all the info out of my head as fast as the questions came my way.

About 14 days in I was able to entirely fall apart, and did some public spectacle which didn’t reflect well on me, and also ended up possibly harming the project, I pushed away some people I really wanted in on the ground floor.

I could make excuses, and I could try to explain myself, but it won’t change anything. However, what I can do is recognize that I did screw up and that I can do better in the future. I understand my why, and that means that I can take preventive measures.

So, what preventive measures can I take in the future?

A big one, delegate. While we were 3 people working together in the early days, the same people who’ve also rejected any direct involvement in management, or interim-committee or the committee / board for the first year of this project, I did a bulk of the work and had trouble getting stuff out of my head.

When I felt like I was about to entirely break, the incident referenced above, I should’ve let go right there and just set up a Discord server and invited everyone, and continued to contribute to the group in their process of preparing a meeting together etc.

But at the same time, if I hadn’t done the meeting the way I did, I would not have learnt the lessons I did, so this is a double edged sword, imo.

So, what went right?

I took my time, and worked through it slowly. I built small road maps for myself to guide me along the way and asked for help when I felt stuck.

I need to remind you all that the survey blew up way bigger than I had ever expected. I think by the end we had almost 200 responses to the survey, and over 120 saying “let’s do this”. [link to the shared data on June 11th]

I couldn’t have planned for that, but when it happened I tried to baby-step my way through it.

The meeting, even though it was long and had it’s issues, was also pretty damn fantastic. The way I had translated Swedish meeting formalities to a discord server turned out to work pretty well, and once people got a hang of it they seemed to appreciate the somewhat rigid structure.

I hope, that using this experience I can create a template for hosting a first meeting when a group of people want to start an org together, and maybe I can help someone else avoid some of the problems that we encountered. Because there’s some solid structure here that definitely can be reused. That said, I will be publishing a separate post about the actual meeting structure and how set it up.