I thought about Feneas structure this morning. Feneas started out small, so because of necessity almost everything ended up being handled by the board members. But Feneas has been growing and maybe the structures need to grow with it. For example, current board members are mostly responsible for running the technical infrastructure of Feneas. But because they’re board members, they’re also responsible for the social infrastructure. That’s a lot of work and I’m worried that at some point one of them burns out and we lose both infrastructures at the same time.
There’s a lot of things to do in a association like this and while I like the flexible tools we’ve adopted, they’re also bad at letting people take responsibility for things. I would suggest that we try to form teams around specific tasks (admin, technical, social, etc.). Just letting people know that “hey, you can participate with your skills even if you’re not part of board” would be a step forward. I’m sure we have people with technical skills who could take over managing some parts of the technical infrastructure. And I think we need more people with communication skills (re: recent discussion with XSF & Matrix) and time to do outreach. Thoughts?