Nomination: idunbarh
Nominee
Name: Ian Dunbar-Hall
GitLab Handle: @idunbarh
Organization:
Employer: Lockheed Martin
Bio: Hello P1TOC! I lead a team tasked with driving adoption of Platform One products and services both for internal company use and by our government customers. My role involves balancing evangelism, customer advocacy, and technical development.
My background is software development with a focus on navigation and safety critical systems. This was primarily supporting hypersonics programs. I've always been a bit of a development tool nut, which has led to a career focused on DevSecOps and enabling teams to perform better. 6 years ago, my frustrations with a lack of modern centralized development tools led to me creating an "unofficial" company wide gitlab instance with a lot of the capabilities available on repo1.
- Fleet of shared GitLab Runners (CI-as-a-Service)
- Standardized container images for pipelines
- Extensive examples and other getting started resources
- Community driven support structure
- Embraced that everything should be "self-service" and minimize developer friction
Ultimately this service was adopted as an enterprise gitlab deployment that supports 10k+ active users and performs 25k+ daily CI builds.
I first became aware of P1 in Oct 2019. I immediately saw the parallels to my own activities about implementing cultural change and adding value by meeting actual customer need.
A couple of P1 touch points I'm involved with:
- Prior to registry1 being available, I open sourced a mirroring python script for IronBank (Jan 2020). This script was used to mirror the entire IB library nightly, in addition to approval and approval artifacts, to internal registries.
- Open sourcing all company BB and IB development to minimize deviation from upstream repo1 projects.
- My team members and I shepherd 5 released IB Images in the last quarter and we’re working to contribute all of our internally maintained container images for pipelines.
- My team members and I are laying the architecture for deploying BB using flux to internal k8s clusters. Ultimately using BB’s GitOps deployment for k8s cattle cluster management.
- I’m meeting daily with teams looking to adopt BB and IB. We're starting engagements to get teams onboarded to BB and leverage IB images.
I believe I can add value as a Community Appointed Member because:
- I’m stubbornly focused on community building, while preferring to work behind the scenes to allow others to shine.
- I believe P1’s success is based on impartiality and driving change. No one entity should have an oversized influence.
- I view the role of a community appointed member as a customer advocate and should be focused on ensuring the success of P1's customers.
- I’m happy to devote a large portion of my time to the P1TOC and P1’s success.
I appreciate everyone taking the time to read this, and I look forward to continuing to be a member of the P1 community.
Cheers,