Over and above what’s detailed in these posts, I’ve been splitting my time between working on projects for We Are Open and Outlandish this week. For the former, my ‘home’ co-op in the CoTech network, I’ve been mainly focusing on work for Catalyst and the Social Mobility Commission. We’re working with Erica Neve and Pedram Parasmand on three contracts, helping charities who are rapidly undergoing digital transformation. We had a really successful retrospective on Friday with UpRising, who we’ve been helping in more depth.
With Outlandish, I’m helping with some productisation of similar projects they’ve worked on for a range of clients. I find this really interesting as it’s simultaneously about meeting user needs and about organisational development. I’m also advising around ways in which they can develop the workshops they offer.
I’m fortunate to work with organisations which are so emotionally intelligent, and which go out of their way to be so. One of the reasons for working with Outlandish is to give them some short-term help with project management while they’re a bit stretched. But another reason is to learn from their processes and procedures; although they’ve only been a co-op for as long as us (four years), they’ve been together and honing things for a decade.
When I was at Jisc, one thing that always impressed me was their internal knowledgebase. They used PBworks for that, while Outlandish uses a WordPress installation with a theme called KnowAll. I’ve been wanting to experiment with wiki.js and so this week Laura Hilliger and I set up an instance at wiki.weareopen.coop and copied over existing pages from our GitHub wiki. I’ve set user permissions so that only logged-in members can edit the wiki, and indeed see any pages that are ‘internal’ only.
Other than that, I’ve just been reviewing a document Laura put together for some work we’re doing with Red Hat, doing a small amount of work for our ongoing work with Greenpeace, and contributing to a ‘playback’ of some recent work we did for Catalyst.
Next week, I’m tying up work for We Are Open on Monday, and for Outlandish on Tuesday, before turning everything off and going on a family holiday for 10 days. As my therapist said in our meeting on Friday, as I’m a bit of a perfectionist, there’s no guarantee that I will actually relax during my holiday just because I’m away from home. So I’m actively trying to cut myself some slack. I deliberately went for a slow run this morning and I even had an afternoon nap yesterday. Small steps.
Header image is a selfie I took on a family walk in the Northumbrian hills last Sunday. Inspired by Low-tech magazine’s solar powered website, I loosely followed this guide to create the ‘stippled’ effect. This reduced the size of an 8.6MB image to a mere 36.6KB.
In May 2016 I helped set up a co-operative with friends and former Mozilla colleagues called We Are Open Co-op. Since that time, we’ve done some inspiring work with fantastic clients, learned a lot about the co-operative economy, and worked in solidarity with similar organisations.
Since January 2018, and particularly during the last six months, I had taken a bit of a back seat in the co-op, focusing on my work at Moodle. However, the time has come for me to refocus my efforts to help continue building an organisation that I not only co-own but see as part of my life’s work.
It’s been an amazing journey over the last couple of years to take MoodleNet from an idea to reality. We did so with a small, part-time team who have gone above and beyond to achieve the vision of a federated, resource-centric social network for educators.
The future is bright for MoodleNet and I’ll be continuing in my role as Product Manager, ensuring the project has the necessary team and budget to make the required impact. I think it’s going to make a huge difference in the lives of hundreds of thousands of educators.
I’m sure it’s not necessary to note, but shall do anyway, that this decision was purely mine and not forced on me by anyone at Moodle. Over time, I’ve come to realise that my interests and talents are in the area of early-stage innovation.
So, from January 2020, I’ll be cutting back to three days for Moodle, meaning I’ve got more headspace for consultancy work. I’m excited to broaden my horizons again, getting involved in some of the really interesting projects that my co-op colleagues have picked up during the last few months, and working with new clients!
If you have any questions, I’m happy to answer them below. And if you’d like to work with the co-op, you might want to email: firstname.lastname@example.org
This week has been one of adjustments, for a couple of reasons.
First, my wife is back doing supply teaching, meaning that I have to be more flexible in my working arrangements so that I can drop off and pick up my daughter from school.
Second, two new people joined the MoodleNet team this week, so we’ve take the opportunity to shake things up a bit. Other than me, everyone else on the team will soon be doing 2.5 days per week. So we’ve agreed to have team meetings on Tuesdays and Thursdays, doing the bulk of our work together between those times.
This week, however, I was already committed to a co-op day on Wednesday with my We Are Open colleagues. It was enjoyable, even though we were talking about hard things like money. We’ve put a call out for people and organisations to fund Badge Wiki, which you can read about on our blog. Thanks to those who have already stepped up!
Other than that, I’ve helped ship MoodleNet v0.9.3 which is looking good, said goodbye to Alex Castaño, hello to Karen Kleinbauerů and James Laver (our new backend developers), done some planning for future releases, and produced a report for the rest of the Moodle Management team.
After a three month hiatus due to playing the magnificent Red Dead Redemption 2 together, Dai Barnes and I have finally got around to recording another episode of the TIDE podcast. Of course, it didn’t quite go to plan and Dai was called away to deal with a pupil (he lives and works at a boarding school) about halfway through the recording.
I’ve been doing plenty of other stuff as well, including writing for Thought Shrapnel every day (are you supporting that yet?), going geocaching with Scouts, taking my daughter to her first swimming gala, booking a family holiday to Iceland in December to see the northern lights, getting better at FIFA 19 Seasons, finishing Jamie Bartlett’s excellent book The People vs Tech, having my last Moodle coaching session (all of the Management team have had them), and trying to fit in daily exercise.
Next week, it’s half-term, and as I hinted at above I’m moving my non-Moodle from Wednesday to Friday. That means I’ve got a glorious Bank Holiday weekend with the in-laws, before spending Tuesday to Thursday planning with the rest of the Moodle Product Managers. I’m not sure whether that sounds intense or pretty chilled.
The Open Badges community has been crying out for a while now for a knowledge repository. You know, somewhere where people can go and find out about how other similar organisations have implemented badge systems, read interesting academic articles and whitepapers, and just discover what’s possible with the Open Badges specification.
That’s why I’m delighted that We Are Open Co-op, with the support of Participate, are building out Badge Wiki. This will be a community-powered project, meaning that it will only be as good as people make it. We’re providing the technical infrastructure and opportunities to pitch in, but we need people to write content, curate resources, and suggest updates!
Tomorrow is the first Badge Wiki ‘barn raising’ session, which we’re running in conjunction with the Open Recognition Alliance. Those who come along don’t need any previous experience with wikis. Nor do they need much knowledge about badges. All you need is a willingness to roll up your sleeves and get involved.