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

Open Source Software Needs You!

headius
February 03, 2015

Open Source Software Needs You!

Have you ever used an open source project? Of course you have, but have you made any contributions yourself? Filed a bug report? Submitted a patch? Have you ever started your own OSS project, or taken a closed/private project public? What licenses should you use? How do you manage contributions? How do you encourage contributors and get work done? In this talk we'll go over the basics of OSS: how to get involved, how to start a project, how to manage contributions. We'll discuss project lifecycles, legal CYA tips, and how to keep projects moving. You'll see the inner workings of real OSS projects, and learn how to be a better OSS user and producer.

Presented at Jfokus 2015.

headius

February 03, 2015
Tweet

More Decks by headius

Other Decks in Programming

Transcript

  1. Open-source software (OSS) is computer software with its source code

    made available with a license in which the copyright holder provides the rights to study, change and distribute the software to anyone and for any purpose. http:/ /en.wikipedia.org/wiki/Open-source_software
  2. …computer software that can be classified as both free software

    and open source software…anyone is freely licensed to use, copy, study, and change the software in any way, and the source code is openly shared so that people are encouraged to voluntarily improve the design of the software. http:/ /en.wikipedia.org/wiki/Free_and_open- source_software
  3. Big Wins Linux and the BSDs Firefox and Chrome PHP,

    Python, Ruby, Perl, Erlang, Go, Dart, … OpenJDK and Mono
  4. Web Server Share Source Date Unix, Unix- like Windows W3Techs

    February 2014 67% 33% Security Space November 2012 62-82% 18-38% http:/ /en.wikipedia.org/wiki/Usage_share_of_operating_systems#Servers_on_the_Internet
  5. Unix or Unix-like? Linux - 54.9% BSD - 1.4% Darwin,

    HP-UX, Solaris - < 0.1% Unknown - 43.6 http:/ /en.wikipedia.org/wiki/Usage_share_of_operating_systems#Servers_on_the_Internet
  6. Finding a Project A tool or library you already use

    A technology you are interested in A language you want to learn A project you simply want to help
  7. LiteStep A project I was using myself Development had slowed

    Large, monolithic codebase Languages and APIs I was familiar with
  8. Meet the Community Mailing lists and forums Chat services like

    IRC or Gitter Q/A sites like Stack Overflow Social sites like LinkedIn or Facebook
  9. A Good Contributor 1. Respects and forgives others 2. Recognizes

    expertise 3. Increases the pool of resources
  10. Things to Contribute Help field questions on lists, forums, IRC

    Improve documentation Present at a conf or user group File bugs or submit fixes
  11. A Good Bug Reporter Clearly states expectation vs reality Provides

    code or steps to reproduce Volunteers relevant env details Responds to updates and comments
  12. Going Deeper Bug triage Help guide other bug reporters Observe

    fixes for other bugs Attempt your own fix!
  13. Fear Itself Afraid I’m not good enough Afraid I don’t

    know the best solution Afraid to make things worse Afraid I’ll be mocked or insulted
  14. My JRuby Contributions Several rewrites of interpreter JIT compiler to

    JVM bytecode Native I/O and process subsystem Ruby/Java integration layer
  15. Crafting a Fix Get a local copy of the code

    Make your changes Confirm they fix the original issue Confirm they do not fail tests Submit fix as a patch or pull request
  16. A Good Patch Fixes the original problem Limits changes to

    the actual fix Matches coding style Maintains documentation truths Includes a regression test
  17. More Tips Ask for help Accept that patch review takes

    time Not all patches are accepted Be willing to iterate
  18. Becoming a Committer Proven track record of contributions Respectful member

    of community Sustained interest Domain expertise
  19. Open Commit Bit Alternative path to core One accepted patch

    and you’re in Rapidly adds new core members Rewards early participation
  20. A Good Core Contributor Respectfully handles bugs and patches Discusses

    changes where necessary Does not violate others’ code Keeps the project’s tests green Remains humble
  21. Starting a Project Missing tool or library Code others find

    useful Community needed An itch to scratch http:/ /upload.wikimedia.org/wikipedia/commons/1/13/Michelangelo%2C_Creation_of_Adam_06.jpg
  22. Contributor Agreement? Requires users to “sign” an agreement Permission to

    release changes Copyright assignment Permission to change licensing Public assertion is often enough
  23. Relicensing? Changing software license requires permission of all contributors Get

    it right the first time or you’ll be chasing people around Some licenses have upgrade clause CPL to EPL, e.g.
  24. Get It Out There Use services familiar to community Include

    license from day 0 Include README, build scripts, examples Tell others in the community …but don’t expect a flood of users
  25. A Good Community Member Has a thick skin Expects to

    learn from everyone Remembers that these are real people
  26. Making Time Make it a fun hobby Prefer jobs that

    support OSS Explain the benefits to your partner Keep projects and interest aligned