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.
Earlier this year, I wrote about the importance of thinking about a project’s architecture of participation when encouraging contribution from a new or existing community of people.
In that post, I included a checklist containing eight points to consider. I think I’ve got another one to add: get your policies right by soliciting feedback on them.
We Are Open Co-op is currently in the first phase of creating Badge Wiki, a knowledge base for the Open Badges community. It’s a project made possible through the support of Participate.com.
- CC BY – we propose that Badge Wiki use a Creative Commons Attribution 4.0 International license instead of the CC BY-SA license used on other wikis, including Wikipedia. Although we would encourage them to do so, we recognise that some people may not be in a position to share material they reuse and remix from Badge Wiki under an open license.
- Register to edit – we propose that, in order to edit Badge Wiki, you must have a registered user account, approved by an administrator. This is to prevent valuable contribution time being taken up by wiki vandalism, trolling, and other anti-social behaviours caused by anonymous editing.
- Real name policy – we propose that members of Badge Wiki use their real names on their profile pages, as well as provide a short bio. This is to prevent accusations of sabotage, given that the Open Badges ecosystem includes commercial interests.
You’re welcome to leave feedback on the posts themselves, in relevant Open Badges Google Group thread, or directly to us: firstname.lastname@example.org.
Thanks in advance for your participation and contribution. Remember, comments expressing support and broad agreement are as valuable as expert nitpicking!