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
230
Growing open source communities on GitHub around your WordPress plugin or theme
benbalter
1
250
It takes a digital village
benbalter
1
460
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
640
Other Decks in Technology
See All in Technology
Git in Team
kawaguti
PRO
3
330
The Cake Is a Lie... And So Is Your Login’s Accessibility
leichteckig
0
100
フルカイテン株式会社 エンジニア向け採用資料
fullkaiten
0
9.1k
Adminaで実現するISMS/SOC2運用の効率化 〜 アカウント管理編 〜
shonansurvivors
4
430
能登半島災害現場エンジニアクロストーク 【JAWS FESTA 2025 in 金沢】
ditccsugii
0
230
許しとアジャイル
jnuank
1
140
『バイトル』CTOが語る! AIネイティブ世代と切り拓くモノづくり組織
dip_tech
PRO
1
110
AWS Top Engineer、浮いてませんか? / As an AWS Top Engineer, Are You Out of Place?
yuj1osm
2
200
ACA でMAGI システムを社内で展開しようとした話
mappie_kochi
1
310
from Sakichi Toyoda to Agile
kawaguti
PRO
1
110
後進育成のしくじり〜任せるスキルとリーダーシップの両立〜
matsu0228
7
3.2k
【Kaigi on Rails 事後勉強会LT】MeはどうしてGirlsに? 私とRubyを繋いだRail(s)
joyfrommasara
0
210
Featured
See All Featured
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
54
3k
Measuring & Analyzing Core Web Vitals
bluesmoon
9
620
RailsConf 2023
tenderlove
30
1.2k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
23
1.5k
Reflections from 52 weeks, 52 projects
jeffersonlam
352
21k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
32
1.6k
Embracing the Ebb and Flow
colly
88
4.8k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
19
1.2k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Bash Introduction
62gerente
615
210k
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]