The document discusses community engineering at Magento. It notes that in 2017 there were 664 contributors to Magento's open source project, growing to 450 in 2018. It highlights qualities like patience, flexibility, and warmth that Magento looks for in contributors. It also discusses how Magento supports and rewards contributors, such as through clear communication, not assigning tasks as "jobs", rewarding hard work, connecting contributors personally including through pairing programs, supporting remote work, and giving credit. The document is presented by David Manners on community engineering at Magento.
14. 息 2018 Magento, Inc. Page | 14
Flexibility
willingness to change or
compromise.
15. 息 2018 Magento, Inc. Page | 15
Flexibility
Adam Paterson
(@adam_paterson)
Working on Import/Export
Happy to take the un-glamours
tasks,
Always asking How can I
help
29. 息 2018 Magento, Inc. Page | 29
Remote work
Work from anywhere you want
Communicate Asynchronously
Recognize that the future is
unknown
Have face-to-face meetings
online
Daily stand-up meetings are
for bonding, blockers, and the
future
Bond in real life
Give credit where it's due and
remember to say thank you
30. 息 2018 Magento, Inc. Page | 30
Community Engineering at Magneto
@mannersd
David Manners
Editor's Notes
#2: Aim here is to highlight what I look for in a contributor and how a maintainer can build a health env to contribute.
Ask who is a contributor and who is a maintainer.
#4: Its not the software?
Its the people!
There are 3 things that make open source great. Can you guess them?
#9: 2017: 664 providing 2450
2018: 450 providing 1646
Thats 3.6 prs a year on average!
#11: Sometimes PRs take a while,
Maintainers need to wait for feedback,
#13: Not saying it should have taken that long but both Dusan and the team needed patience for this task to get it done right
Times he could not contribute but we waited,
#14: Often the feedback can be Please change x
Or when running a project someone might have to do the dirty work,
#17: We do not just want to keep the same people involved so you need warmth in people to bring the new people into the community
Showing warmth and welcome in text format can be tough,
#21: Slack, live streams, regular and clear github communication, take the time and explain something in a call.
Often written word can lead to misunderstands so talk to people,
#23: Most of the time this is not a full time job for people,
Life gets busy so understand and plan for that,
#25: Build a reward system,
Offer swag, training, and a bit of fame.
#26: Training and event discounts,
Elephants and swag,
Recognition and articles,
Personal and company level reward system
#27: Dont just focus on the code but the people,
Take the time to get to know at least a little about people,
Slack donut app is a great opportunity for this
#29: Open source is a lot like remote work,
Look at gitlab and other remote first companies for ideas