The Success of Rails: Ensuring Growth for the Next 100 Years

Eileen M. Uchitelle

May 18, 2022

5.5k

The Success of Rails: Ensuring Growth for the Next 100 Years

RailsConf 2022 Day 2 Opening Keynote in which I explore the history of Rails, Shopify's role in the evolution of Rails, and the reasons that more companies should be investing in the framework with ongoing contributions.

Eileen M. Uchitelle

May 18, 2022

Tweet

More Decks by Eileen M. Uchitelle

See All by Eileen M. Uchitelle

[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails

[Brighton Ruby 2023] The Magic of Rails

[RailsConf 2023 Opening Keynote] The Magic of Rails

Exit(ing) through the YJIT

Improving CVAR Performance in Ruby 3.1

Upgrading GitHub from Ruby 2.6 to 2.7

Technically, a talk | Ruby Day 2020

Technically, a talk | Brighton Ruby 2020

Technically, a talk | RailsConf 2020

Other Decks in Programming

See All in Programming

プチモブから始めてみよう(XP祭り2023)

Webパフォーマンス改善ハンズオン

AWS SDKのClientはFactory経由で作ろう

RubyVM を PHP で実装する〜Hello World を出力するまで〜

拡張機能でええんちゃう？

On the way to io_uring networking

readonly class で作る堅牢なアプリケーション

CDK Day 2023 - Configure cross-account deployment using CDK

Go×RLSで複数テナントのデータを安全に扱う/secure-data-access-with-go-rls-in-multi-tenant-environment

WebのE2Eテスト自動化〜導入から運用・評価までの道のり編〜

coconala_engineer

モノレポ化、そしてその先へ〜ヘンリーのRe-architecting戦略〜

CircleCIでChatGPTにエラーの解説を頼んでみた

Featured

See All Featured

Unsuck your backbone

Designing for Performance

JazzCon 2018 Closing Keynote - Leadership for the Reluctant Leader

Large-scale JavaScript Application Architecture

GraphQLの誤解/rethinking-graphql

Easily Structure & Communicate Ideas using Wireframe

Docker and Python

The Language of Interfaces

Debugging Ruby Performance

How to name files

Intergalactic Javascript Robots from Outer Space

Transcript

The Success

of Ruby on Rails
Ensuring growth for

the next 100 years

View Slide
Thank You,

Ruby Central ὑ

View Slide
Eileen M Uchitelle
Connect with me

@eileencodes

View Slide
I work at Shopify
Ruby & Rails

Infrastructure Team

View Slide
Member of the
Rails Core Team

View Slide
The Success

of Ruby on Rails
Ensuring growth for

the next 100 years

View Slide
The History of Rails

From hobby to

success

View Slide
2004
Rails is born
The History

of Rails

View Slide
2004
Rails is born
Tobi receives

a zip of Rails
The History

of Rails

View Slide
2004
2005
Snowdevil

launches
The History

of Rails
Rails is born
Tobi receives

a zip of Rails

View Slide
2004
Rails is born
Tobi receives

a zip of Rails 2005
Snowdevil

launches
Rails 1.0 is

released
The History

of Rails

View Slide
The History

of Rails
2006
Shopify

launches
2004
Rails is born
Tobi receives

a zip of Rails 2005
Snowdevil

launches
Rails 1.0 is

released

View Slide
2008
GitHub
launches
The History

of Rails
2006
Shopify

launches
2004
Rails is born
Tobi receives

a zip of Rails 2005
Snowdevil

launches
Rails 1.0 is

released

View Slide
Rails moves

to GitHub
The History

of Rails
2008
GitHub
launches
2006
Shopify

launches
2004
Rails is born
Tobi receives

a zip of Rails 2005
Snowdevil

launches
Rails 1.0 is

released

View Slide
2004
Rails is born
Tobi receives

a zip of Rails
2008
GitHub
launches
Rails moves

to GitHub
2005
Snowdevil

launches
Rails 1.0 is

released
2006
Shopify

launches
The History

of Rails

View Slide
Rails Governance

Team structure and

responsibilities

View Slide
1. Core
2. Committers
3. Issue
4. Triage
Rails Governance Structure

View Slide
1. Core
2. Committers
3. Issue
4. Triage
Security
Includes Core

and other

security-focused

contributors
Rails Governance Structure

View Slide
Rails
Governance
Structure
How the
"Security"
team works.

View Slide
Security Team
• Triaging security issues on HackerOne
and [email protected]

View Slide
Security Team
• Triaging security issues on HackerOne
and [email protected]

• Writing patches for vulnerabilities

View Slide
Security Team
• Triaging security issues on HackerOne
and [email protected]

• Writing patches for vulnerabilities

• Requests CVE

View Slide
Rails
Governance

Structure
How the

"Triage" team
works.

View Slide
@keeran @
fl
avorjones @tonkpils @skipkayhil
@adrianna-chang-

shopify
@hahmed @hparker @ jorgemanrubia
@ghiculescu

View Slide
Triage Team
• Initial triaging of issues

View Slide
Triage Team
• Initial triaging of issues

• Reviewing pull requests

View Slide
Rails
Governance
Structure
How the

"Issues" team
works.

View Slide
@p8 @seejohnrun
@zzak
@robin850 @vipulnsward
@Edouard-chin
@sikachu

View Slide
Issues Team
• Triage issues, review PRs, nurture
contributors

View Slide
Issues Team
• Triage issues, review PRs, nurture
contributors

• Merge documentation and non-code
changes

View Slide
Rails
Governance
Structure
How the
"Committers"
team works.

View Slide
@amatsuda @schneems @eugeneius
@y-yagi
@gmcgibbon @yahonda
@jonathanhefner

View Slide
Committers Team
• Triage issues, review PRs, nurture
contributors

View Slide
Committers Team
• Triage issues, review PRs, nurture
contributors

• Merge most code changes

View Slide
Rails
Governance

Structure
How the

"Core" team
works.

View Slide
@jeremy @matthewd @dhh @tenderlove
@carlosantonio

dasilva
@rafaelfranca @guilleiguaran
@fxn @jhawthorn
@byroot @eileencodes
@kamipo

View Slide
Core Team
• Triage issues, review PRs, nurture
contributors

View Slide
Core Team
• Triage issues, review PRs, nurture
contributors

• Setting the direction of the framework

View Slide
Core Team
• Triage issues, review PRs, nurture
contributors

• Setting the direction of the framework

• Releasing Rails

View Slide
Core Team
• Triage issues, review PRs, nurture
contributors

• Setting the direction of the framework

• Releasing Rails

• Setting Policy & Guidelines

View Slide
Core Team
• Triage issues, review PRs, nurture
contributors

• Setting the direction of the framework

• Releasing Rails

• Setting Policy & Guidelines

• Contributor Growth

View Slide
Rails
Governance
Making Rails
more
welcoming.

View Slide
Making Rails more welcoming
• Open Discord server coming soon

View Slide
Making Rails more welcoming
• Open Discord server coming soon

• Implement review rounds for PRs

View Slide
Making Rails more welcoming
• Open Discord server coming soon

• Implement review rounds for PRs

• Disabled the stale bot

View Slide
Making Rails more welcoming
• Open Discord server coming soon

• Implement review rounds for PRs

• Disabled the stale bot

• Open source of
fi
ce hours at RailsConf:
Shopify Booth - today 3-4pm PST

View Slide
How I started

contributing to Rails

View Slide
My History of

Rails
2009
First learn of

Rails

View Slide
My History of

Rails
2009
First learn of

Rails
2011
Attend Big
Nerd Ranch

View Slide
View Slide
My History of

Rails
2014
First Rails PR
2009
First learn of

Rails
2011
Attend Big
Nerd Ranch

View Slide
My History of

Rails
2014
First Rails PR
2009
First learn of

Rails
2011
Attend Big
Nerd Ranch
Issues Team

View Slide
My History of

Rails
2015
Committers

Team
2014
First Rails PR
2009
First learn of

Rails
2011
Attend Big
Nerd Ranch
Issues Team

View Slide
My History of

Rails
2015
Committers

Team
2014
First Rails PR
2009
First learn of

Rails
2011
Attend Big
Nerd Ranch
Issues Team
2017
Core Team

View Slide
Why I work
on Rails.
A drive to work
on something
bigger.

View Slide
Why I work
on Rails.
To rede
fi
ne
developer
happiness.

View Slide
Why I work
on Rails.
To ensure
applications
stay on Rails.

View Slide
You should be

investing in Rails

View Slide
Investing

in Rails.
Ensure it's part
of your
mission.

View Slide
Investing

in Rails.
Build a
dedicated
team.

View Slide
Investing

in Rails.
Treat Rails like
an extension

of your app.

View Slide
How to start

contributing to Rails

View Slide
How to
contribute

to Rails.
Read the
contributing
docs.

View Slide
guides.rubyonrails.org/contributing_to_ruby_on_rails.html

View Slide
How to
contribute

to Rails.
Get Rails
running on
your machine.

View Slide
What does a good PR look like?
• Write a descriptive commit message

View Slide
Fix tag helper regression
Vue.js, alpinejs, and potentially other JS libraries
support tags starting with `@` symbols. This was broken
by the recent security release in 649516c.
I've only added `@` to the list even though there are
potentially other safe characters. We can add more
if necessary (and if safe).
Fixes:
* #45014
* #44972

View Slide
What does a good PR look like?
• Write a descriptive commit message

• PRs should be 1 commit

View Slide
What does a good PR look like?
• Write a descriptive commit message

• PRs should be 1 commit

• Open PRs against `main`

View Slide
What does a good PR look like?
• Write a descriptive commit message

• PRs should be 1 commit

• Open PRs against `main`

• Add tests & docs

View Slide
What does a good PR look like?
• Write a descriptive commit message

• PRs should be 1 commit

• Open PRs against `main`

• Add tests & docs

• Add a CHANGELOG entry if applicable

View Slide
* `rails db:schema:{dump,load}` now checks
`ENV["SCHEMA_FORMAT"]` before config
Since `rails db:structure:{dump,load}` was deprecated
there wasn't a simple way to dump a schema to both
SQL and Ruby formats. You can now do this with an
environment variable. For example:
```
SCHEMA_FORMAT=sql rake db:schema:dump
```
*Alex Ghiculescu*

View Slide
What does a good PR look like?
• Write a descriptive commit message

• PRs should be 1 commit

• Open PRs against `main`

• Add tests & docs

• Add a CHANGELOG entry if applicable

• Follow Rails style and patterns

View Slide
What does a good PR look like?
• Write a descriptive commit message

• PRs should be 1 commit

• Open PRs against `main`

• Add tests & docs

• Add a CHANGELOG entry if applicable

• Follow Rails style and patterns

• Don't break public APIs

View Slide
How to
contribute

to Rails.
No really.
Upgrade your
apps
fi
rst.

View Slide
How to
contribute

to Rails.
Run your
application off
main.

View Slide
How to
contribute

to Rails.
Look at how
your apps are
using Rails.

View Slide
How to
contribute

to Rails.
Keep showing
up and
contributing.

View Slide
Why companies

avoid open source

View Slide
Why leaders
don't fund
OSS.
Leaders don't
see it as a
priority.

View Slide
Why leaders
don't fund
OSS.
Leaders think
working on
OSS is "fun".

View Slide
Why leaders
don't fund
OSS.
Leaders view
OSS work as a
reward.

View Slide
How to convince

leadership

View Slide
How to
convince
leadership.
Find your

internal

allies.

View Slide
How to
convince
leadership.
Gather
supporting
data.

View Slide
How to
convince
leadership.
Spend time
developing a
growth plan.

View Slide
How to
convince
leadership.
Be mindful of
the language
you use.

View Slide
How to
convince
leadership.
Don't get
discouraged.
Try again later.

View Slide
Why should we

invest in Rails?

View Slide
Why invest

in Rails?
Improves
engineering
skills.

View Slide
Why invest

in Rails?
Because it's
essential to
app health.

View Slide
Why invest
in Rails?
It's less
expensive than
a rewrite.

View Slide
Blocked upgrade
Unhappy engineers
Low morale
Force rewrite
Site falling over
High Risk
💻

View Slide
Resilient application
Improved engineering skills
Rails evolves with you
Stable foundation
Low technical debt
💻

View Slide
Investing in
Rails is
proactive.

View Slide
Investing in
Rails is
proactive.
Rewriting an
application is
reactive.

View Slide
Why invest

in Rails?
Because

you're

missing out.

View Slide
Why invest

in Rails?
To make sure
Rails is built

for you.

View Slide
Why invest

in Rails?
To ensure

success for
100+ years.

View Slide
Thank You
RailsConf!

Find me online @eileencodes

View Slide