Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Exploring Leadership, Mangement, and Mentorship...

Exploring Leadership, Mangement, and Mentorship in Open Source

Leadership. Management. Mentorship. When considering decentralized Open Source projects all of these ideas come into play is a truly unique way. That is because of the nature of Open Source itself: self-motivation and self-determination. The individual has considerably more control over their own destiny with respect to what, why, and how they do work as a contributor when compared to "work" inside a more traditional corporate structure. Further there is often a disparity in goals between the create of an Open Source project and those who go on to maintain that same project months or years down the road.

This talk will explore the value systems that exist in Open Source communities and discuss how they shape the ideas of leadership, management, and mentorship in Open Source projects. It will compare these ontologies in projects (both Open Source and not) of varying size, scope, and focus and demonstrate how they manifest directly into actions or structures in the projects. If you've ever wondered how Open Source gets made, this is the talk for you!

Charlie Robbins

July 14, 2017
Tweet

More Decks by Charlie Robbins

Other Decks in Technology

Transcript

  1. What am I going to talk about? 3 1 What

    is Open Source, practically speaking? 2 Open Source methodology, by default. 3 On Value Systems and incentives. 4 Moving mountains of code vs. the long tail in Open Source 5 Bottle your own lightning
  2. A N D P E O P L E P

    E O P L E lots of
  3. Junior?
 Senior? Product Manager Ops / ITSec Project Manager Engineer

    UX Designer Individual Contribut or Program Manager Engineeri ng Manager
  4. A N D P E O P L E P

    E O P L E even more
  5. Any UI Platform single-point of failure is a for both

    customer experience A N D developer experience
  6. Any organization that designs a system (defined broadly) will produce

    a design whose structure is a copy of the organization's communication structure. — Melvyn Conway, 1967 “ BETTER KNOWN AS CONWAY’S LAW
  7. and onboarding using Slack & Github Code reviews, ad-hoc Q&A,

    If you time to contribute can make then your problems are our problems
  8. 0 15 30 45 60 Q1 2016 Q2 2016 Q3

    2016 Q4 2016 Q1 2017 Q2 2017 Contributors New Contributors Total "Inner Source" has proven 43 VERY effective.
  9. 0 15 30 45 60 Q1 2016 Q2 2016 Q3

    2016 Q4 2016 Q1 2017 Q2 2017 Contributors New Contributors Total "Inner Source" has proven 43 VERY effective. Growth of more than linear! contributors is
  10. HAVE A CODE conduct of policy TL;DR? READ THIS AND

    USE IT. contributor-covenant.org
  11. Every Open Source governance model is a shallow wrapper (defined

    broadly) to a basic conflict resolution strategy. — Me? I guess? Today? “
  12. Every Open Source governance model is a shallow wrapper (defined

    broadly) to a basic conflict resolution strategy. — Me? I guess? Today? PLEASE DON’T CALL THIS A LAW “
  13. Every Open Source governance model is a shallow wrapper (defined

    broadly) to a basic conflict resolution strategy. — Me? I guess? Today? PLEASE DON’T CALL THIS A LAW IT’S JUST HUMAN NATURE “
  14. Meritocracy a lie is MERITOCRACY COMPLETELY IGNORES BASIC POWER &

    SOCIAL DYNAMICS INHERENT IN all human relationships
  15. WITH THE EXCEPTION OF A “CLASSIC” BDFL STRUCTURE IT’S ALL

    COMMITTEES source: Harvard Law School, ‘17
  16. source: Harvard Law School, ‘17 SIMILAR TO BUT NOT EXACTLY

    NODE.JS’ GOVERNANCE MODEL Let’s talk about COMMITTEES?