Hacktoberfest 2018 (Nashville PHP September 2018)

0c217b9a7dd0aa31ed40bd0f453727e1?s=47 Ben Ramsey
September 11, 2018

Hacktoberfest 2018 (Nashville PHP September 2018)

0c217b9a7dd0aa31ed40bd0f453727e1?s=128

Ben Ramsey

September 11, 2018
Tweet

Transcript

  1. None
  2. What is it?

  3. ‣ “month-long celebration of
 open source software” ‣ Open to

    everyone ‣ Five pull requests must be made to GitHub-hosted repositories ‣ You can sign-up anytime between October 1 and October 31
  4. None
  5. Contribute to Open Source

  6. ‣ Improve your skills ‣ Meet people ‣ Find mentors

    and teach others ‣ Build a reputation (and a career) ‣ Learn people skills ‣ Feeling of empowerment Why?
  7. ‣ Self-interest ‣ Self-expression ‣ Improve the world ‣ Hormones

    Credit: Rasmus Lerdorf, “Good Chemistry,” Sunshine PHP 2015
  8. ‣ Plan events, workshops, conferences ‣ Are you a designer?

    ‣ Write documentation, tutorials, translations ‣ Play the “project manager” ‣ Answer questions on Stack Overflow ‣ Review code, mentor others Coding not required
  9. ‣ Who is involved in this project? Get the lay

    of the land
  10. None
  11. None
  12. None
  13. None
  14. None
  15. None
  16. None
  17. None
  18. None
  19. None
  20. None
  21. None
  22. None
  23. None
  24. None
  25. ‣ Who is involved in this project? ‣ Project documentation

    Get the lay of the land
  26. None
  27. None
  28. None
  29. None
  30. None
  31. None
  32. None
  33. None
  34. None
  35. None
  36. None
  37. ‣ Who is involved in this project? ‣ Project documentation

    ‣ Use the tools provided by the project Get the lay of the land
  38. None
  39. None
  40. None
  41. None
  42. ‣ Start with a project you use ‣ Use a

    resource to discover projects Find a project
  43. None
  44. None
  45. None
  46. None
  47. None
  48. ‣ Is the project open source? ‣ Does it actively

    accept contributions? ‣ Is the project welcoming? Before you contribute
  49. ‣ Effective communication is key! Contributing

  50. ‣ Give context ‣ Do your homework ‣ Keep requests

    short & direct ‣ Keep communication public ‣ Ask questions (but be patient) ‣ Respect decisions ‣ Keep it classy
  51. ‣ Effective communication is key! ‣ Opening an issue Contributing

  52. ‣ Report an error you can’t solve ‣ Discuss a

    high-level topic or idea ‣ Propose a new feature When to open an issue…
  53. ‣ Comment to let people you’re working on an issue

    ‣ If the issue is old, ask for confirmation before beginning work ‣ If you opened an issue and later figured it out, comment on the issue and close it Issue tips…
  54. ‣ Effective communication is key! ‣ Opening an issue ‣

    Opening a pull request Contributing
  55. ‣ Submit trivial fixes ‣ Start work on a contribution

    that was asked for, or that you’ve already discussed, in an issue When to open a PR…
  56. ‣ Fork the repository How to submit a PR

  57. None
  58. ‣ Fork the repository ‣ Clone & create a branch

    for your edits How to submit a PR
  59. None
  60. ‣ Fork the repository ‣ Clone & create a branch

    for your edits ‣ Reference any relevant issues How to submit a PR
  61. None
  62. ‣ Fork the repository ‣ Clone & create a branch

    for your edits ‣ Reference any relevant issues ‣ If applicable, include before/after screenshots ‣ Test your changes! How to submit a PR
  63. None
  64. ‣ Fork the repository ‣ Clone & create a branch

    for your edits ‣ Reference any relevant issues ‣ If applicable, include before/after screenshots ‣ Test your changes! ‣ Contribute in the style of the project How to submit a PR
  65. Next steps

  66. ‣ MakeAPullRequest.com ‣ roshanjossey.github.io/first-contributions ‣ hacktoberfest.digitalocean.com ‣ opensource.guide ‣ Go

    hack! Psst: github.com/ramsey/collection
  67. Thank you Ben Ramsey benramsey.com @ramsey@phpc.social @ramsey