Build a Better
Hat Rack

All Contributions Welcome

These are my speaker notes. There are many like them, but these ones are mine

Hi!

Hi! I'm Katie, and I'm a software developer. I wear many hats. I use all the languages.

I do OSS contributions Docker have paid me for my contributions I am also an Active Technical Contributor for Open Stack Want to know what my contribution to OpenStack was?

an inline documentation change. It's a Python file, yo

If you committed within the window, you got a free ticket to Tokyo Incentive Driven Code Development

But how do we track all these contributions that we make

GitHub gives us some of this functionality Pretty graphs and the like

but it's not exactly perfect And it only include itself There are other ways - project specific, etc

But what about everything else? Code Review Documentation Testing Design UAT Promotion User Groups / Presentations

Who here: Has committed code to Joomla? - Dont answer the next ones Who here has not used Joomla Who has introduced Joomla to others? Who is only here because you're interested in learnign more?

These are all contributions Not even including all the aspects of the SDLC that go unattributed Community, yo

So, how can we track and record and acknowledge all this?

Let me tell you about Leslie Amazing human being

#LABHR

bit.do/LABHR

She started this hashtag, and wrote a blog post about it

Which I've turned into a easy to read manual to try and spread the message

DÅLIGORDLEK

#LABHR

It's a bad pun

#LABHR

Leslie and Deb meet over coffee Leslie of Google / Elastic Deb of Open Innovation Network Sahana Software Foundation Software for developing countries “No, this is great. This gives me one of those places to hang your hat. You know, something you can list on your LinkedIn profile instead of just a project that you work on for free because you love it. But no one really knows about it or notices.”

#LABHR

So Leslie + Blog = 5 steps

#LABHR

write the list

#LABHR

send the list

#LABHR

GRAVY Tweet about it

#LABHR

GRAVY #2 Linked in Recommendations NOT endorsements See later

#LABHR

GRAVY #3 Do it for someone not like you

#LABHR

Simple! Nice! Helpful!

But it didn't get that much traction Leslie reported ~30 known LinkedIn recommendation I've done talks in multiple different cities/languages It's always the same, one or two after the talk (PyConAU exception - because I refused to get off stage until 10 tweets happened) (This did result in some residiual activity during the sprints) Maybe y'all need a LIVE DEMO

How to
be nice

[demo]

Live demo, lets hope this works Hat Rack

Hi, Jack!

Jack is a force of good for the community - Davey

How to
say thank you

[demo]

Repeat for mic, if required.

How not to
react

This didn't happen last time. Ref Chris.

Chris was a little bit upset last time this happened Ref Tom

And not just him.

It took a third party to actually confirm they did good. Ref Russell. I've seen this before, not only in the #LABHR

Why can't we take a compliment?

Minimisation

Antonym of exaggeration "She'll be right, no worries" Understating

Tall Poppy
Syndrome

We are reluctant to allow ourselves to be elevated in front of our peers, lest we be cut down. And of course, everyone's favourite

Imposter
Syndrome

If we get thanked, we tend not to think it actually applies, because all the problems

Acknowledging just how splendid we are

We are amazing. We are splendid. We need to ack that. The fact that I didn't know half of these existed is a problem in itself.

can be dev or community or combination of both Sarah Mei Sam Saffron

Perl White Camel User Groups Advocacy * Community Tim O'Reilly Paul Fenwick

Python Software Foundation awards Community Service Distinguished Service Nick Coghlan

Acknowledging our own achievements

one way to break this is to start to acknowledge our own achievements

Lara Hogan, Donut Manifesto This donut = draft of a book Giving ourselves a little celebration if noone else will Tweeting the donut Piggybacking on a picture of a donut (instagram makes this OK).

I like the idea of donuts. This is one I did the other day. I'm not trying to be self-gratifying, but sometimes, you need to do that.

Not all contributions are donuts

sometimes it's the little things that add up onto something big

Stack Overflow

The profiles are now really nice!

Just a drop
in the ocean

How many people go onto stackoverflow to ask Does anyone know how many questions there have been answered on SO?

SO recently 10 million questions. Go on there and find your project's tag, and thank the people who are answering your things for you You might have a standalone SO instance for your Q&A

If a dev found a solution just half of those times, and it saved them just 30 minutes, that's nearly 1.85 billion hours saved. It's enough to read all of Wikipedia. 12,000 times. 8 million developers come here every day. It'd be a bigger country than more than half the world's nations. There are about 51,000 developers on the site at any given second. This is what 51,000 people looks like. Together, we've built a place where every 12 seconds a developer posts an answer that helps fellow coders.

Your community advocates need your thanks You can thank them by giving them something extremely useful

But why say
thank you?

Apart from it being a nice thing todo.

It's nice thing to do

Not getting acknowedgement sucks Burnout Plight of the organiser

Encourage continued engagement

They have done a thing once, they will do it again. Charelle's story from Compcon - first commit, hand held from Russell

Voluntold

I'm super encourageable. I think half the stuff i do is average until validated

"Foot in the Door"

"Fear, Uncertainty
and Dopamine" - Paul Fenwick Amazing talk about a few different issues about hacking brains Brilliant riff about making contrubutors stick Foot in the Door - Drive Safely sign - 17% baseline, 76% with pre-sticker Car Bumper Stickers A tiny little foot in the door STICKERS Little things = seed, -> improvement over time "If you see someone doing something like that - acknowledge them like crazy

Change self image

it makes them feel valued self image change, they feel included in the project, and it makes them feel good but it also binds their fate to yours if your project fails, it reflects badly on them, because they are now involed in your project

But just how can we say thank you

Communication
within
your project

Mentioning things in your release notes is a good thing. MediaGolbin does this Drupal concatenates thread commentors into git commit message But the scope of this communication is only within your existing community. You need to extend to more general communications

Communication
outside
your project

Give your helpers something to show for their work

This is the new age resume. Publically accessible. We can thank people who would otherwise be unrecognised LinkedIn is pretty awful though.

Recommendations
vs
Endorsements

Two main ways to add content to someone's linkedin profile

Recommendations

Here's all the different sections that you can fill on your profile

But here are the only ones that are able to be recommendable

Running a conf, volenteering as a thing, is experience LIST IT AS SUCH

Endorsements

... possibly not as helpful

User
Contributions

No idea how the 'Repositories contributed to' works I've done Rails, Rubocop, Docker, OpenStack, Pybee... they arent there

focus on this graph. So much focus

What counts?

Commits

(against `master` or `gh-pages`)

Issues and Pull Requests

(opened, in the past year)

Continued discussions on a PR only counts as one

But only if...

you own the repo

or, you're a collaborator

or, you're in the owner organisation

or, you forked the repo

... but commits don't count on forks

What counts?

Only some of your work.

But what if you really want that full green graph

Sound too hard?

It's ok, there's a hack for that

$ pip install rockstar

$ rockstar

By default - one hello world in c++ everyday for as many days as you specify

ozh.org/contribution

Project
Contributions

Looking at any github project page we can see all the contributors right? THere's a button right at the top and everything

But if we click it, then we don't actually get the contributors We get the top ones, with a graph, ranked by lines of code

And it's only the top 100

This is only some of the contributors

Not even all the code commiters are listed!

This is only some of the contributions

What about everything else

What about
everything else?

Logged Issues

Unmerged Pull Requests

Code Reviews

Feature Discussions

Feature Voting

What if...

What if these contributions counted

What if these contributions were accolates

you have a profile

What if you could change your profile

What if you could curate a list of repositories you were proud to have worked on

And add ones that would otherwise fall off the end because they don't have enough stars?

What if your contributions outside your namespace could be curated?

What if you could list what you were proud to have worked on

What if you could add things that you had interacted with, but not committed code to

What if you could display that the owners of the project had given you accolades for your work? What if, as a project owner, you could give props to community members

What if the gamification goal was community help, not a full green graph

But how can you find who in your project community to give props to? The customisation of the github profile may not exist, but the data for who could be given props does

github.com/glasnt/octohat

`pip install octohat`

introducing octohat

hakimel/reveal.js

Code Contributors: 142

Non-Code Contributors: 435

joomla/joomla-cms

Code Contributors: 414

Non-Code Contributors: 266*

* Since June 2015, ~700 issues/PRs

Joomla is massive I could only get this many before my GitHub token ratelimited.

avinassh/rockstar

Code Contributors: 30

Non-Code Contributors: 38

glasnt/octohat

Code Contributors: 6

Non-Code Contributor: 3

So many conversions! TODO update moar stats

TL;DR:

There's nothing wrong
with being nice

Thank people that have already done so much Encourge them to do more Do more you self

#LABHR

bit.do/LABHR

github.com/glasnt/octohat

Non-code contributors to this talk:

Donna Benjamin, Nick Coghlan, Robert Collins, Ben Dechrai, Tom Eastman, Paul Fenwick, Leslie Hawthorn, Lindsay Holmwood, Russell Keith-Magee, Deb Nicholson, Christopher Neugebauer, Christopher Pitt, Davey Shafik, Aurynn Shaw, Jack Skinner

Thank You <3

Build a BetterHat Rack All Contributions Welcome These are my speaker notes. There are many like them, but these ones are mine