It All Started With a Patch

Getting started with open source.

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 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 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 Slide

4. Getting Started
   

   View 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 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 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 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 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 Slide

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

    View Slide