Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Open source workflows in highly regulated envir...
Search
Ben Balter
May 08, 2017
Technology
0
92
Open source workflows in highly regulated environments
Why how you work is as important as what you work on.
Ben Balter
May 08, 2017
Tweet
Share
More Decks by Ben Balter
See All by Ben Balter
A community of communities: Empowering maintainers to grow communities around their code
benbalter
1
1.3k
Fostering a culture of collaboration
benbalter
0
220
Growing open source communities on GitHub around your WordPress plugin or theme
benbalter
1
240
It takes a digital village
benbalter
1
450
Optimize for Developer Happiness
benbalter
0
280
The technology is the easy part
benbalter
2
290
How to foster an open source culture inside Government
benbalter
3
2.4k
Open source inspired workflows for open (and closed) geospatial data
benbalter
0
150
10 ways people are (mis)using GitHub Pages for fun and profit
benbalter
6
630
Other Decks in Technology
See All in Technology
Autonomous Database Serverless 技術詳細 / adb-s_technical_detail_jp
oracle4engineer
PRO
18
52k
Cloud WANの基礎から応用~少しだけDeep Dive~
masakiokuda
4
120
JAWS-UG のイベントで使うハンズオンシナリオを Amazon Q Developer for CLI で作ってみた話
kazzpapa3
0
120
工業高校で学習したとあるエンジニアのキャリアの話
shirayanagiryuji
0
120
AIドリブンのソフトウェア開発 - うまいやり方とまずいやり方
okdt
PRO
7
110
Intro to Software Startups: Spring 2025
arnabdotorg
0
280
Exadata Database Service on Dedicated Infrastructure セキュリティ、ネットワーク、および管理について
oracle4engineer
PRO
1
330
Infrastructure as Prompt実装記 〜Bedrock AgentCoreで作る自然言語インフラエージェント〜
yusukeshimizu
1
160
GCASアップデート(202506-202508)
techniczna
0
210
サービスロボット最前線:ugoが挑むPhysical AI活用
kmatsuiugo
0
140
生成AIによるソフトウェア開発の収束地点 - Hack Fes 2025
vaaaaanquish
34
16k
Claude Code x Androidアプリ 開発
kgmyshin
1
240
Featured
See All Featured
The Invisible Side of Design
smashingmag
301
51k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
358
30k
How STYLIGHT went responsive
nonsquared
100
5.7k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.6k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
26k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
810
We Have a Design System, Now What?
morganepeng
53
7.7k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
32
1.4k
Fantastic passwords and where to find them - at NoRuKo
philnash
51
3.4k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Testing 201, or: Great Expectations
jmmastey
45
7.6k
Docker and Python
trallard
45
3.5k
Transcript
Open source workflows in highly regulated environments @benbalter ben.balter.com
[email protected]
Conway's law “organizations which design systems ... are constrained to
produce designs which are copies of the communication structures of these organizations ”
How you work is as important as what you work
on
Roadmap 1. Open source moves beyond Agile 2. Open source
behind the firewall 3. Open source in regulated environments
1. Open source moves beyond Agile
Agile is a methodology "get incremental changes into users' hands"
Open source is a philosophy "remove barriers to the free
flow of information"
Closed source Open source Waterfall Traditional software development Publishing
proprietary code Agile Modern software development Working in the open
Both open source and agile value ad-hoc and informal communication
over documentation and process
Face-to-face versus asynchronous Agile Open source
Applying open source to Agile
Transparency solves for process
1. Prefer social constraints over administrative or technical constraints
2. Prefer systems that naturally capture and expose process
3. Prefer stakeholders subscribe to the software development process itself
The constraints of open source
Electronic Prefer systems that naturally capture process
Available Expose process via shareable URLs
Asynchronous Decisions can be made outside meetings
Informal Professional, not formal
Open source flow https://guides.github.com/introduction/flow/
Issues are Agile user stories
Everyone has access to issues
Anyone can open an issue
Teams prioritize, sequence, and implement
Create a branch
Add commits
Open a pull request
Discuss and review
Deploy
Merge
2. Open source behind the firewall
Open source is a philosophy, not a type of
software
Process is shared to the widest extent practical One team,
your organization, or the entire world
Human-centric processes produce human-centric software
Five best practices of open source behind the firewall
1. The technology is the easy part
2. Start small and go through the motions
3. Minimize information imbalance
4. Embrace the constraints of open source
5. Minimize Friction
Friction (n) - the time it takes to go from
"I want to contribute" to "I have"
3. Open source in regulated environments
Version control captures who made what change when
Open source workflows capture (and expose) process
How open source captures process 1. Chat (and issues) 2.
ChatOps 3. Continuous Integration 4. Code Reviews 5. Deployments
Chat (and issues)
Chat is inherently asynchronous
Chat captures and exposes who made what decision why
ChatOps A shared command-line for development teams
Meet Hubot
CultureOps
DevOps • View cameras in our datacenter • Search error
logs • Manage and trigger alerts • Perform server maintenance • Configure load balancer • Provision servers • Adjust firewalls • Activate DDoS mitigation • Configure DNS • Manage background jobs • Deploy to production
Continuous Integration (CI)
Required build statuses
Nothing gets deployed unless tests are green
Code reviews
Nothing gets deployed unless reviews are green
Deployments at GitHub On the pull request in Chat
How you work is as important as what you work
on
Open source workflows in highly regulated environments @benbalter ben.balter.com
[email protected]