Slide 1
Slide 1 text
The Success
of Ruby on Rails
Ensuring growth for
the next 100 years
Slide 2
Slide 2 text
Thank You,
Ruby Central ὑ
Slide 3
Slide 3 text
Eileen M Uchitelle
Connect with me
@eileencodes
Slide 4
Slide 4 text
I work at Shopify
Ruby & Rails
Infrastructure Team
Slide 5
Slide 5 text
Member of the
Rails Core Team
Slide 6
Slide 6 text
The Success
of Ruby on Rails
Ensuring growth for
the next 100 years
Slide 7
Slide 7 text
The History of Rails
From hobby to
success
Slide 8
Slide 8 text
2004
Rails is born
The History
of Rails
Slide 9
Slide 9 text
2004
Rails is born
Tobi receives
a zip of Rails
The History
of Rails
Slide 10
Slide 10 text
2004
2005
Snowdevil
launches
The History
of Rails
Rails is born
Tobi receives
a zip of Rails
Slide 11
Slide 11 text
2004
Rails is born
Tobi receives
a zip of Rails 2005
Snowdevil
launches
Rails 1.0 is
released
The History
of Rails
Slide 12
Slide 12 text
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
Slide 13
Slide 13 text
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
Slide 14
Slide 14 text
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
Slide 15
Slide 15 text
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
Slide 16
Slide 16 text
Rails Governance
Team structure and
responsibilities
Slide 17
Slide 17 text
1. Core
2. Committers
3. Issue
4. Triage
Rails Governance Structure
Slide 18
Slide 18 text
1. Core
2. Committers
3. Issue
4. Triage
Security
Includes Core
and other
security-focused
contributors
Rails Governance Structure
Slide 19
Slide 19 text
Rails
Governance
Structure
How the
"Security"
team works.
Slide 21
Slide 21 text
Security Team
• Triaging security issues on HackerOne
and [email protected]
• Writing patches for vulnerabilities
Slide 22
Slide 22 text
Security Team
• Triaging security issues on HackerOne
and [email protected]
• Writing patches for vulnerabilities
• Requests CVE
Slide 23
Slide 23 text
Rails
Governance
Structure
How the
"Triage" team
works.
Slide 24
Slide 24 text
@keeran @
fl
avorjones @tonkpils @skipkayhil
@adrianna-chang-
shopify
@hahmed @hparker @ jorgemanrubia
@ghiculescu
Slide 25
Slide 25 text
Triage Team
• Initial triaging of issues
Slide 26
Slide 26 text
Triage Team
• Initial triaging of issues
• Reviewing pull requests
Slide 27
Slide 27 text
Rails
Governance
Structure
How the
"Issues" team
works.
Slide 28
Slide 28 text
@p8 @seejohnrun
@zzak
@robin850 @vipulnsward
@Edouard-chin
@sikachu
Slide 29
Slide 29 text
Issues Team
• Triage issues, review PRs, nurture
contributors
Slide 30
Slide 30 text
Issues Team
• Triage issues, review PRs, nurture
contributors
• Merge documentation and non-code
changes
Slide 31
Slide 31 text
Rails
Governance
Structure
How the
"Committers"
team works.
Slide 32
Slide 32 text
@amatsuda @schneems @eugeneius
@y-yagi
@gmcgibbon @yahonda
@jonathanhefner
Slide 33
Slide 33 text
Committers Team
• Triage issues, review PRs, nurture
contributors
Slide 34
Slide 34 text
Committers Team
• Triage issues, review PRs, nurture
contributors
• Merge most code changes
Slide 35
Slide 35 text
Rails
Governance
Structure
How the
"Core" team
works.
Slide 36
Slide 36 text
@jeremy @matthewd @dhh @tenderlove
@carlosantonio
dasilva
@rafaelfranca @guilleiguaran
@fxn @jhawthorn
@byroot @eileencodes
@kamipo
Slide 37
Slide 37 text
Core Team
• Triage issues, review PRs, nurture
contributors
Slide 38
Slide 38 text
Core Team
• Triage issues, review PRs, nurture
contributors
• Setting the direction of the framework
Slide 39
Slide 39 text
Core Team
• Triage issues, review PRs, nurture
contributors
• Setting the direction of the framework
• Releasing Rails
Slide 40
Slide 40 text
Core Team
• Triage issues, review PRs, nurture
contributors
• Setting the direction of the framework
• Releasing Rails
• Setting Policy & Guidelines
Slide 41
Slide 41 text
Core Team
• Triage issues, review PRs, nurture
contributors
• Setting the direction of the framework
• Releasing Rails
• Setting Policy & Guidelines
• Contributor Growth
Slide 42
Slide 42 text
Rails
Governance
Making Rails
more
welcoming.
Slide 43
Slide 43 text
Making Rails more welcoming
• Open Discord server coming soon
Slide 44
Slide 44 text
Making Rails more welcoming
• Open Discord server coming soon
• Implement review rounds for PRs
Slide 45
Slide 45 text
Making Rails more welcoming
• Open Discord server coming soon
• Implement review rounds for PRs
• Disabled the stale bot
Slide 46
Slide 46 text
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
Slide 47
Slide 47 text
How I started
contributing to Rails
Slide 48
Slide 48 text
My History of
Rails
2009
First learn of
Rails
Slide 49
Slide 49 text
My History of
Rails
2009
First learn of
Rails
2011
Attend Big
Nerd Ranch
Slide 50
Slide 50 text
No content
Slide 51
Slide 51 text
My History of
Rails
2014
First Rails PR
2009
First learn of
Rails
2011
Attend Big
Nerd Ranch
Slide 52
Slide 52 text
My History of
Rails
2014
First Rails PR
2009
First learn of
Rails
2011
Attend Big
Nerd Ranch
Issues Team
Slide 53
Slide 53 text
My History of
Rails
2015
Committers
Team
2014
First Rails PR
2009
First learn of
Rails
2011
Attend Big
Nerd Ranch
Issues Team
Slide 54
Slide 54 text
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
Slide 55
Slide 55 text
Why I work
on Rails.
A drive to work
on something
bigger.
Slide 56
Slide 56 text
Why I work
on Rails.
To rede
fi
ne
developer
happiness.
Slide 57
Slide 57 text
Why I work
on Rails.
To ensure
applications
stay on Rails.
Slide 58
Slide 58 text
You should be
investing in Rails
Slide 59
Slide 59 text
Investing
in Rails.
Ensure it's part
of your
mission.
Slide 60
Slide 60 text
Investing
in Rails.
Build a
dedicated
team.
Slide 61
Slide 61 text
Investing
in Rails.
Treat Rails like
an extension
of your app.
Slide 62
Slide 62 text
How to start
contributing to Rails
Slide 63
Slide 63 text
How to
contribute
to Rails.
Read the
contributing
docs.
Slide 64
Slide 64 text
guides.rubyonrails.org/contributing_to_ruby_on_rails.html
Slide 65
Slide 65 text
How to
contribute
to Rails.
Get Rails
running on
your machine.
Slide 66
Slide 66 text
What does a good PR look like?
• Write a descriptive commit message
Slide 67
Slide 67 text
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
Slide 68
Slide 68 text
What does a good PR look like?
• Write a descriptive commit message
• PRs should be 1 commit
Slide 69
Slide 69 text
What does a good PR look like?
• Write a descriptive commit message
• PRs should be 1 commit
• Open PRs against `main`
Slide 70
Slide 70 text
What does a good PR look like?
• Write a descriptive commit message
• PRs should be 1 commit
• Open PRs against `main`
• Add tests & docs
Slide 71
Slide 71 text
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
Slide 72
Slide 72 text
* `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*
Slide 73
Slide 73 text
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
Slide 74
Slide 74 text
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
Slide 75
Slide 75 text
How to
contribute
to Rails.
No really.
Upgrade your
apps
fi
rst.
Slide 76
Slide 76 text
How to
contribute
to Rails.
Run your
application off
main.
Slide 77
Slide 77 text
How to
contribute
to Rails.
Look at how
your apps are
using Rails.
Slide 78
Slide 78 text
How to
contribute
to Rails.
Keep showing
up and
contributing.
Slide 79
Slide 79 text
Why companies
avoid open source
Slide 80
Slide 80 text
Why leaders
don't fund
OSS.
Leaders don't
see it as a
priority.
Slide 81
Slide 81 text
Why leaders
don't fund
OSS.
Leaders think
working on
OSS is "fun".
Slide 82
Slide 82 text
Why leaders
don't fund
OSS.
Leaders view
OSS work as a
reward.
Slide 83
Slide 83 text
How to convince
leadership
Slide 84
Slide 84 text
How to
convince
leadership.
Find your
internal
allies.
Slide 85
Slide 85 text
How to
convince
leadership.
Gather
supporting
data.
Slide 86
Slide 86 text
How to
convince
leadership.
Spend time
developing a
growth plan.
Slide 87
Slide 87 text
How to
convince
leadership.
Be mindful of
the language
you use.
Slide 88
Slide 88 text
How to
convince
leadership.
Don't get
discouraged.
Try again later.
Slide 89
Slide 89 text
Why should we
invest in Rails?
Slide 90
Slide 90 text
Why invest
in Rails?
Improves
engineering
skills.
Slide 91
Slide 91 text
Why invest
in Rails?
Because it's
essential to
app health.
Slide 92
Slide 92 text
Why invest
in Rails?
It's less
expensive than
a rewrite.
Slide 93
Slide 93 text
Blocked upgrade
Unhappy engineers
Low morale
Force rewrite
Site falling over
High Risk
💻
Slide 94
Slide 94 text
Resilient application
Improved engineering skills
Rails evolves with you
Stable foundation
Low technical debt
💻
Slide 95
Slide 95 text
Investing in
Rails is
proactive.
Slide 96
Slide 96 text
Investing in
Rails is
proactive.
Rewriting an
application is
reactive.
Slide 97
Slide 97 text
Why invest
in Rails?
Because
you're
missing out.
Slide 98
Slide 98 text
Why invest
in Rails?
To make sure
Rails is built
for you.
Slide 99
Slide 99 text
Why invest
in Rails?
To ensure
success for
100+ years.
Slide 100
Slide 100 text
Thank You
RailsConf!
Find me online @eileencodes