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

It All Started With a Patch

Oliver Davies
February 08, 2017

It All Started With a Patch

Getting started with open source.

Oliver Davies

February 08, 2017
Tweet

More Decks by Oliver Davies

Other Decks in Technology

Transcript

  1. It All Started With A Patch
    Getting into open source
    A presenta on by ( )
    Oliver Davies @opdavies
    h ps:/
    /joind.in/talk/98504

    View full-size slide

  2. Oliver Davies
    Senior Developer at Appnova on
    Technologies
    Open source enthusiast
    Working with OSS full‐ me since 2010
    Drupal core contributor, mentor, module
    maintainer.
    One of over 3,800 contributors to Drupal 8
    to date

    View full-size slide

  3. Why Contribute to Open Source?
    Pay it forward
    Be part of a community
    Be a be er developer
    Be er career prospects
    Recogni on
    “There's a module for that.”
    “If you work in open source you get
    thousands of extra colleagues”

    View full-size slide

  4. Getting Started

    View full-size slide

  5. Mentoring
    Assist new and inexperienced
    contributors.
    Mentored code sprints.
    IRC/Slack office hours.
    h ps:/
    /www.drupal.org/core‐
    mentoring
    h ps:/
    /php‐mentoring.org
    Google Summer of Code

    View full-size slide

  6. Types of Contribution
    Report/fix a bug
    Review an exis ng patch, help diagnose an issue
    Write a test
    Documenta on updates
    Transla ons
    Test a new release
    Write a blog post, record a screencast

    View full-size slide

  7. Finding Something to Work On
    Start with something small.
    Novice tag on Drupal.org.
    up‐for‐grabs and first‐ mers‐only tags on GitHub.
    h p:/
    /yourfirstpr.github.io
    h p:/
    /www.firs mersonly.com

    View full-size slide

  8. Making Changes
    Patches
    One canonical version
    Clone the repository
    Make and commit changes
    locally
    Create a patch file (git diff,
    git format-patch)
    Patch uploaded to issue queue
    and reviewed
    Pull Requests
    Mul ple versions
    Fork the repository
    Make, commit, push changes
    Create PR
    PR is reviewed

    View full-size slide

  9. Takeaways
    Reviewers and maintainers are not scary (honest!).
    People are reviewing the code, not reviewing you.
    Not all changes will be accepted.
    Be aware of different workflows, guidelines per project.
    README, CONTRIBUTING.md files.
    Engage with the community.
    Contribute in person if possible (code sprints/hackathons).

    View full-size slide

  10. Questions?
    Feedback
    h ps:/
    /joind.in/talk/98504

    View full-size slide