Nomenclature
Posted 3 months, 2 weeks ago at 11:03. 9 comments
Recognizing some existing internal group dynamics and the need for the entire Mozilla release engineering (RelEng) team to grow in a more sustainable manner, we recently started an internal reorganization of the RelEng group. John will likely blog about the new structure of the group at some point, but I’ll relate the bits that are pertinent to me.
Armen and I have been working together on projects for about a year now, and that’s been working out pretty well, so we’ve formalized that arrangement. Armen will begin “officially” reporting to me immediately, and we’ll be looking to hire some more teammates to fill out our sub-group of about 4 people.
Our focus will remain the same: look for large-ish sections of RelEng-related project work, whether existing or new, and drive them to completion. Some things we’ve worked on previously include properly integrating l10n builds into our buildbot infrastructure, and enabling nightly updates for localized builds. We are currently working on standardizing on one set of update tools and getting localized builds put together for mobile.
John has affectionately dubbed our sub-group “Big Chunks” in reference to the scope of work we take on. That’s a terrible name, and that’s where you come in. I’m soliciting alternate naming ideas for our new group. The leading candidate so far was proposed by Armen: “Chunk Norris”. I have faith in the collective wisdom of the internet to come up with something better (perhaps not even referencing “chunks” at all) or at the very least to entertain me with your attempts.
And….GO!
iBlue Chunks
Chunky bacon!
ChunkBots
Or maybe “Build it and they will come”
“Goonies”
The B Team. (is that B for big chunks? I don’t know.)
To quote the Nac Mac Feegle “Bigjobs!”
I’d suggest some particle physics stuff. You gotta dig huge holes in the ground to make all those small things come together. And once you’re done, you still don’t see the dimensions at the surface. LHC? Though, ALICE is part of LHC, not sure if that maps to the team structure
I was just chatting with an old coworker (who’s still there!) about my first release engineering job (no, Mozilla wasn’t it!), and the fact that we used to be able to comfortably fit around the same conference table, and now they’ve split into the:
* Build Infrastructure Team
* Release Team
* SCM Team
This sounds a lot like the first one.
(Congrats on the promotion, BTW; maybe some day, I’ll get one of those…)