Here in Oxfordshire we’re nowhere near the epicentre of Storm Darragh, but we’re still feeling the effects. A huge tree came down and blocked the Thorney Leys road in Witney near Burwell Meadow and the kids and I needed to take an ad-hoc diversion.
🤞 Fingers crossed for all my friends and family in worse-hit places!
For my final bit of Three Rings volunteering this International Volunteer Day, I’m working on improving the UI of a new upcoming feature: a spreadsheet-like page that makes it easy for administrators to edit the details of many volunteers simultaneously (all backed by the usual level of customisation and view/edit permissions that Three Rings is known for).
It’s a moderately-popular request, and I can see it being helpful to volunteer coordinators at many different types of voluntary organisation.
Don’t have time to write up the test instructions today, though, because I’ve got to wrap up my volunteering and go do some childwrangling, so that’ll do for now!
Even when it’s technical, not all of my International Volunteer Day work for Three Rings has been spent using our key technologies (LNMR [Linux, Nginx, MariaDB, Ruby] stacks).
Today, I wrote some extra PHP for our WordPress-powered contact form to notify our Support Team volunteers via Slack when messages are sent. We already aim to respond to every message within 24 hours, 365 days a year, and are often faster than that… but this might help us to be even more-responsive to the needs of the charities who we help look after.
My Three Rings volunteering this International Volunteer Day isn’t all technical work. It’s also time to process the incoming postal mail.
Our time as volunteers may be free, but our servers aren’t, so the larger and richer charities that use our services help contribute to our hosting costs. Most send money digitally, but some use dual-signatory accounts that require they send cheques.
As well as the programming tasks I’m working on for Three Rings this International Volunteer Day, I’m also doing a little devops. We’ve got a new server architecture rolling out next week, and I’m tasked with ensuring that the logging on them meets our security standards.
Each server’s on-device logs are retained in date-stamped files for 14 days, but they’re also backed-up offsite daily.
Those bits all seem to be working, so next I need to work out a way to add a notification to our monitoring platform if any server doesn’t successfully push a log to the offsite backup in a timely manner.
Not every code review is fireworks, but most Three Rings changes come from the actual needs of the voluntary organisations that Three Rings supports. Some of our users were confused by the way the Admin > Roles page was laid out, so one of our volunteers wrote an improved version.
And because we’re all about collaboration, discussion, learning from one another, and volunteer-empowerment… I’ve added a minor suggestion… but approved their change “with or without” it. I trust my fellow volunteer to either accept my suggestion (if it’s right), reject it (if it’s wrong), or solicit more reviews or bring it to Slack or our fortnightly dev meeting (if it requires discussion).
Good news! It turns out that the new code to fix the mail merge fields in Three Rings doesn’t introduce an inconsistency with established behaviour. It was important to check, but it turns out all is well.
I touched bases with a fellow volunteer on Slack. Three Rings volunteers primarily communicate via Slack: it helps us to work asynchronously, which supports the fact that our volunteers all have different schedules and preferences. Some might do a couple of evenings a week, others might do the odd weekend, others still might do an occasional intense solid week of volunteering with us and then nothing for months! A communication model that works both synchronously and asynchronously is really important to make that volunteering model work, and Slack fits the bill.
We get together in person sometimes, and we meet on Zoom from time to time too, but Slack is king of communication at Three Rings
My first task this International Volunteer Day is to test a pull request that aims to fix a bug with Three Rings’ mail merge fields functionality. As it’s planned to be a hotfix (direct into production) we require extra rigor and more reviewers than code that just goes into the main branch for later testing on our beta environment.
My concern is that fixing this bug might lead to a regression not described by our automated tests, so I’m rolling back to a version from a couple of months ago to compare the behaviour of the affected tool then and now. Sometimes you just need some hands-on testing!
Happy International Volunteer Day! Volunteering rocks.
As I’m on sabbatical, I’m in the lucky position of being able to spend most of the day on a volunteer project very close to my heart: Three Rings. Three Rings is a 22-year-old web-based service produced by volunteers, for volunteers. The software service we produce supports the efforts of around 60,000 volunteers working at charities and other voluntary organisations around the globe.
I’ll be posting throughout the day about some of the different tasks I take on. My volunteer role with Three Rings is primarily a developer/devops one, but it takes all sorts to make a project like this work (even if my posts look biased towards the technical stuff)!
But first: coffee.
TFW a recipe calls for a glass of wine but you can’t get the cork back in the bottle so you just have to drink the rest of it.
Ah well, what’s a chef to do? 🤷🍷
Not quite ready for wintering indoors, our village’s hardy sheep are enjoying pasturing in the large field near the school this beautiful but chilly morning.
In good news, my injured arm is not broken and should recover within a couple of weeks.
In amusing news, the doctor who treated me recognised me from (tales of) my electric shock admission earlier in the year, even though she never treated me on that ocassion.
I’m leaving Ireland a day late, from the wrong airport, and with one fewer functioning arm than I anticipated. It’s been quite the ride. I’ll be glad to get home.
(for those that are concerned: I’ve damaged my shoulder, possibly while slipping down a hill in search of a geocache or geohashpoint; so, y’know, the usual reason I get injured… but I’ve got some physio instructions I’m supposed to follow, and I’ll be okay)
Sooo… I’m in Dublin.
I missed me flight at Knock airport, which turns out to have been the only plane leaving that tiny airport today. So I arranged a flight from Dublin tomorrow, extended my car rental and arranged to drop it off in the capital’s airport instead, and zipped over here.
Now I’m in an underlit bar sipping a Guinness and waiting for a pizza.
I’ve only been driving in Ireland for several days, so less than 100% of the iconography of the signage makes sense to me instantly, for now. But this one’s a complete mystery to me.
Is this warning joggers than tiny cars might bounce off their heads? Or is it exhorting distant swerving motorists to put on their right indicator to tell people which way to run to avoid being hit by them? Or maybe it’s advising that down this road is a football pitch for giants and they’ll play “headers” with you in your car if you’re not careful? I honestly haven’t a clue.