Slide 1

Slide 1 text

Ruby & we

Slide 2

Slide 2 text

Why do we care?

Slide 3

Slide 3 text

How do we care?

Slide 4

Slide 4 text

Where can we help?

Slide 5

Slide 5 text

Where do we start?

Slide 6

Slide 6 text

Problem 1

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

1 result?

Slide 9

Slide 9 text

Then show me the result!

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

~ interlude ~

Slide 12

Slide 12 text

Excuses

Slide 13

Slide 13 text

“What if nobody cares?”

Slide 14

Slide 14 text

If you care, somebody else probably does too.

Slide 15

Slide 15 text

“What if they think my code sucks?”

Slide 16

Slide 16 text

Then you’ll have a chance to improve?

Slide 17

Slide 17 text

“What if …”

Slide 18

Slide 18 text

Shut up!

Slide 19

Slide 19 text

Find courage in your pears.

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

programming

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

~ end ~

Slide 24

Slide 24 text

Solution 2

Slide 25

Slide 25 text

How do I change things?

Slide 26

Slide 26 text

github.com/rubygems/rubygems.org

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

No content

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

Make your point 
 with Ruby.

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

“Cool, I know how to write tests.”

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

“Aw, mannn! This isn’t RSpec…”

Slide 35

Slide 35 text

It’s actually not that different.

Slide 36

Slide 36 text

No content

Slide 37

Slide 37 text

We had to write Cucumber features.

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

No content

Slide 40

Slide 40 text

You don’t have to write Cucumber features!

Slide 41

Slide 41 text

This was our test.

Slide 42

Slide 42 text

context '(…) with a single exact match' do setup do @sinatra = create(:rubygem, :name => "sinatra") create(:version, :rubygem => @sinatra) get :show, :query => "sinatra" end should respond_with :redirect should redirect_to('the gem') { rubygem_path(@sinatra) } end

Slide 43

Slide 43 text

This was our code.

Slide 44

Slide 44 text

redirect_to rubygem_path(@exact_match) \
 if @gems == [@exact_match]

Slide 45

Slide 45 text

That’s it.

Slide 46

Slide 46 text

No content

Slide 47

Slide 47 text

+34 −8 Lines

Slide 48

Slide 48 text

Pull Request conversation

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

" This makes it impossible to perform certain searches. For example, if a user wanted to search for all the gems with the omniauth prefix, this would no longer be possible because the omniauth gem exists.

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

No content

Slide 53

Slide 53 text

Are you sure? it seems to redirect only if there is only 1 element in the original search result array

Slide 54

Slide 54 text

No content

Slide 55

Slide 55 text

No content

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

(actual response)

Slide 58

Slide 58 text

Takeaway #1 Give clear examples in your Pull Requests

Slide 59

Slide 59 text

Takeaway #2 Don’t instantly fold, react to feedback politely.

Slide 60

Slide 60 text

Takeaway #3 Reviewing PRs is hard, make it easy.

Slide 61

Slide 61 text

Practice 3

Slide 62

Slide 62 text

What about the setup?

Slide 63

Slide 63 text

No content

Slide 64

Slide 64 text

./script/setup

Slide 65

Slide 65 text

Grab a data dump!

Slide 66

Slide 66 text

rubygems.org/pages/data

Slide 67

Slide 67 text

No content

Slide 68

Slide 68 text

script/load-pg-dump \
 -u olivierlacan \ -d rubygems_dev \ 
 -c dump

Slide 69

Slide 69 text

You’ll need PostgreSQL 9.5 to use it.

Slide 70

Slide 70 text

No content

Slide 71

Slide 71 text

To write tests, you gotta run tests.

Slide 72

Slide 72 text

redis-server

Slide 73

Slide 73 text

elasticsearch

Slide 74

Slide 74 text

Otherwise, some tests will fail.

Slide 75

Slide 75 text

bundle exec rake

Slide 76

Slide 76 text

1 minute later…

Slide 77

Slide 77 text

Finished in 52.023608s, 
 17.0884 runs/s, 
 32.1008 assertions/s. 889 runs, 1670 assertions, 
 0 failures, 0 errors, 5 skips

Slide 78

Slide 78 text

[!!!] Index does not exist

Slide 79

Slide 79 text

You’re missing the elasticsearch index.

Slide 80

Slide 80 text

bundle exec rake gemcutter:index:update

Slide 81

Slide 81 text

Tests + real world data give you ideas.

Slide 82

Slide 82 text

No content

Slide 83

Slide 83 text

2 years between the first & second PR

Slide 84

Slide 84 text

“Which gems use my gem as a runtime dependency?” New Problem

Slide 85

Slide 85 text

guides.rubygems.org

Slide 86

Slide 86 text

No content

Slide 87

Slide 87 text

No content

Slide 88

Slide 88 text

No content

Slide 89

Slide 89 text

Let’s play!

Slide 90

Slide 90 text

GET /api/v1/gems/rails/reverse_dependencies.json

Slide 91

Slide 91 text

No content

Slide 92

Slide 92 text

No content

Slide 93

Slide 93 text

No content

Slide 94

Slide 94 text

Are those runtime or development dependencies?

Slide 95

Slide 95 text

Both.

Slide 96

Slide 96 text

I’m a gem maintainer and I want to know who depends on it at runtime?

Slide 97

Slide 97 text

Before: you couldn’t.

Slide 98

Slide 98 text

Now: you can.

Slide 99

Slide 99 text

No content

Slide 100

Slide 100 text

No content

Slide 101

Slide 101 text

GET /api/v1/gems/rails/reverse_dependencies.json?only=runtime

Slide 102

Slide 102 text

No content

Slide 103

Slide 103 text

GET /api/v1/gems/rails/reverse_dependencies.json?only=runtime

Slide 104

Slide 104 text

No content

Slide 105

Slide 105 text

gems that depend on rails for runtime development 7115 1859

Slide 106

Slide 106 text

What about your gems?

Slide 107

Slide 107 text

What about the gems you use in production?

Slide 108

Slide 108 text

Back to the 
 Pull Request.

Slide 109

Slide 109 text

No content

Slide 110

Slide 110 text

Allow fetching only runtime reverse_dependencies from API Pull Request Title

Slide 111

Slide 111 text

Clear, concise, add screenshots it can help, don’t make assumptions. Description

Slide 112

Slide 112 text

No content

Slide 113

Slide 113 text

No content

Slide 114

Slide 114 text

Learn how to keep a fork updated: robots.thoughtbot.com/keeping-a-github-fork-updated Upkeep

Slide 115

Slide 115 text

Respond to other contributors, to maintainers, be patient. Communication

Slide 116

Slide 116 text

depend.herokuapp.com

Slide 117

Slide 117 text

No content

Slide 118

Slide 118 text

Don’t try rails, it will crash the app. :-p

Slide 119

Slide 119 text

[email protected] Questions? Want to pair?