2015 hasn’t exactly gone according to plan.
I began the year with a strong plan in place for personal development and skills building. That plan was derailed when the New England snowpocalypse happened. I became homebound for nearly two months, and depression set in. (It’s amazing how losing access to infrastructure impacts mental health. There’s something to be said for the interrelated nature of personal metabolism and community metabolism.)
Once the snow finally began to melt, I reemerged with a serious case of general anxiety the likes of which I haven’t experienced in years. I suffered from anxiety most of my life up until 2010 when I found help and subsequently beat it. This Winter brought it back, and combined with my executive dysfunction issues from my 2002 head injury, there was no way I was in any condition to find a productive groove nor work towards goals with any consistency. So my number one priority became to seek help!
Since I moved to Boston, I hadn’t actually taken the time to establish relationships with new doctors, so I’ve spent the past few months doing just that. The act of engaging the healthcare system with all its quirks has been its own brand of therapy. So far I’ve seen a dentist (and it didn’t work out, so I’m looking for another), found a PCP I like as well as an ENT specialist, and finally found a psychologist I can work with! Hooray! Progress!
I’ll probably be writing more about my health in future posts. There’s a project brewing here that combines my personal health with my professional/activist interests around personal data ownership infrastructure, and I can’t wait to start sharing!
Focusing on my health hasn’t been the only thing I’ve been working on however.
Code for Boston
At the beginning of the year, I had a chat with Harlan Weber to say that I’d be stepping back a bit from my responsibilities as Community Lead to focus on my personal goals. At that point I was feeling a bit burnt out. At the end of April, we had a day long core team retreat to figure out the future of our brigade, streamline our collaborative processes, etc. By the conclusion of the retreat, I felt re-energized and ready to take on new responsabilites that we’d defined that weekend. In addition to many of the same community management activities I’d been doing, I also took on the role of ‘Scribe’, responsible for core team documentation. I immediately took over our collaborative Trello boards and have since discovered I have a knack for project management.
I’m really excited about what the rest of the year holds. After putting on two big events, and losing two of our core team members to life happening, we’ve decided we need to focus the rest of this year on the long-term sustainability of Code for Boston. We’re engaged in conversation with Code for America around the idea of ‘Institutionalization’ which is all about taking our brigade to the next level by figuring out how we can offload many of our logistical activities to paid staff. We’re not sure if this means we’re turning Code for Boston into its own non-profit, finding local partners, or starting a new organization that supports Code for Boston, but we’re heavily leaning towards the latter and looking to existing models in other cities for inspiration. In the mean time, we’re also going to begin working on leadership succession planning, diversity and inclusion efforts, and streamlining our documentation+processes so our members are better supported.
More on all this in future posts.
After six months off, I’ve become active again at Mozilla! I’d been hanging back since December to see how things would progress, and this thread started by Emma Irwin on the Participation Team’s collaborative process finally motivated me to dive back in. Since then, I’ve started working with Jonathan Wilde on a project called Gossamer, and next week I’m going to be in Mexico to work with the Mozilla Wiki Team at Wikimania.
Because many of my contributions to Mozilla have been invisible in the past (and because I have a terrible memory for most of it), I’ve started a blog specifically to track my daily/weekly activity. If you’d like to keep track of what I’m up to at Mozilla, check out http://mozillatracks.captaincalliope.net/
One of the through-lines this year with all of the above has been documentation. I’ve spent a lot of time keeping and maintaining health records, making sure collaborative documentation is accurate and up to date, and documenting my own activities. While I haven’t been doing this all out in the open yet, I’ve been developing good record keeping habits, learning what works and what doesn’t in terms of practices and tooling, and as a side effect leveling up in my ability to work with others.
I haven’t yet revisited/renegotiated the goals I set at the beginning of the year, but I am working towards being more open in my goal setting processes. For the past two years I’ve run my life off of a private Trello board that I’ve recently refactored into a public one: https://trello.com/b/GrOdToFy/captaincalliope-overview
This is a big step for one of my major goals for the year: putting together a support network of peers and mentors. I consult this Trello board frequently as part of my overall GTD process. By making it open, I invite others to join me in my personal and professional development at a deep level with clarity around how it might intersect with theirs.
Expect to see me publishing more frequently in all areas of my work!