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 environments
Search
Ben Balter
May 08, 2017
Technology
0
72
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.1k
Fostering a culture of collaboration
benbalter
0
170
Growing open source communities on GitHub around your WordPress plugin or theme
benbalter
1
200
It takes a digital village
benbalter
1
310
Optimize for Developer Happiness
benbalter
0
250
The technology is the easy part
benbalter
2
250
How to foster an open source culture inside Government
benbalter
3
2.2k
Open source inspired workflows for open (and closed) geospatial data
benbalter
0
120
10 ways people are (mis)using GitHub Pages for fun and profit
benbalter
6
600
Other Decks in Technology
See All in Technology
DevOpsDays History and my DevOps story
kawaguti
PRO
9
2.3k
ChatGPT for IT Service Management (IT Pro)
dahatake
7
1.4k
プロデザ! BY リクルート vol.18_リクルートのリサーチ実践組織「リサーチブーストコミュニティ」
recruitengineers
PRO
3
260
Azure Container Apps + Bicep 〜 こんな感じで運用しています
kaz29
2
400
KubeConにproposalを送りたい人へのアドバイス
sat
PRO
2
110
「手動オペレーションに定評がある」と言われた私が心がけていること / phpcon_odawara2024
blue_goheimochi
2
370
Meta Quest 3 で動く桜マシマシ WebXR アプリを IBM Cloud Code Engine と Babylon.js で作った話
1ftseabass
PRO
0
110
**強い**エンジニアのなり方 - フィードバックサイクルを勝ち取る / grow one day each day
soudai
64
19k
生産性向上チームの紹介
cybozuinsideout
PRO
1
840
長期間TiDBを使ってきた話 @ 私たちはなぜNewSQLを使うのかTiDB選定5社が語る選定理由と活用LT / Experiences with TiDB Over Time
chibiegg
2
850
AWS認定資格を取得したので、初めてマネコンを触った時を振り返ってみた。
ainatsuptr
2
100
少数チームで挑む: SwiftUI, TCA, KMPを用いた 新規動画配信アプリ 「ABEMA Live」の開発について
tomu28
0
610
Featured
See All Featured
Code Review Best Practice
trishagee
54
15k
Six Lessons from altMBA
skipperchong
20
3k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
30
6k
StorybookのUI Testing Handbookを読んだ
zakiyama
12
4.6k
Testing 201, or: Great Expectations
jmmastey
27
6.3k
Documentation Writing (for coders)
carmenintech
59
3.9k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
13
1.5k
The Art of Programming - Codeland 2020
erikaheidi
41
12k
The Straight Up "How To Draw Better" Workshop
denniskardys
227
130k
ParisWeb 2013: Learning to Love: Crash Course in Emotional UX Design
dotmariusz
104
6.6k
The MySQL Ecosystem @ GitHub 2015
samlambert
242
12k
Fireside Chat
paigeccino
20
2.6k
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]