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
91
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
東京海上日動におけるセキュアな開発プロセスの取り組み
miyabit
0
150
FAST導入1年間のふりかえり〜現実を直視し、さらなる進化を求めて〜 / Review of the first year of FAST implementation
wooootack
1
130
Shadow DOM & Security - Exploring the boundary between light and shadow
masatokinugawa
0
670
PHPでResult型やってみよう
higaki_program
0
190
DATA+AI SummitとSnowflake Summit: ユーザから見た共通点と相違点 / DATA+AI Summit and Snowflake Summit
nttcom
0
220
AWS表彰プログラムとキャリアについて
naoki_0531
1
110
スプリントゴール未達症候群に送る処方箋
kakehashi
PRO
1
240
大規模組織にAIエージェントを迅速に導入するためのセキュリティの勘所 / AI agents for large-scale organizations
i35_267
6
240
Railsの限界を超えろ!「家族アルバム みてね」の画像・動画の大規模アップロードを支えるアーキテクチャの変遷
ojima_h
3
440
Recoil脱却の現状と挑戦
kirik
3
350
ゼロから始めるSREの事業貢献 - 生成AI時代のSRE成長戦略と実践 / Starting SRE from Day One
shinyorke
PRO
0
240
M365アカウント侵害時の初動対応
lhazy
7
4.6k
Featured
See All Featured
Scaling GitHub
holman
461
140k
VelocityConf: Rendering Performance Case Studies
addyosmani
332
24k
Principles of Awesome APIs and How to Build Them.
keavy
126
17k
Building Adaptive Systems
keathley
43
2.7k
We Have a Design System, Now What?
morganepeng
53
7.7k
How to train your dragon (web standard)
notwaldorf
96
6.1k
Site-Speed That Sticks
csswizardry
10
720
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.6k
Navigating Team Friction
lara
187
15k
RailsConf 2023
tenderlove
30
1.2k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.9k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
109
19k
Transcript
Open source workflows in highly regulated environments @benbalter ben.balter.com
ben.balter@github.com
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
ben.balter@github.com