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. 1.
  2. 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
  3. 4.
  4. 6.

    ‣ Improve your skills ‣ Meet people ‣ Find mentors

    and teach others ‣ Build a reputation (and a career) ‣ Learn people skills ‣ Feeling of empowerment Why?
  5. 7.

    ‣ Self-interest ‣ Self-expression ‣ Improve the world ‣ Hormones

    Credit: Rasmus Lerdorf, “Good Chemistry,” Sunshine PHP 2015
  6. 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
  7. 10.
  8. 11.
  9. 12.
  10. 13.
  11. 14.
  12. 15.
  13. 16.
  14. 17.
  15. 18.
  16. 19.
  17. 20.
  18. 21.
  19. 22.
  20. 23.
  21. 24.
  22. 26.
  23. 27.
  24. 28.
  25. 29.
  26. 30.
  27. 31.
  28. 32.
  29. 33.
  30. 34.
  31. 35.
  32. 36.
  33. 37.

    ‣ Who is involved in this project? ‣ Project documentation

    ‣ Use the tools provided by the project Get the lay of the land
  34. 38.
  35. 39.
  36. 40.
  37. 41.
  38. 42.

    ‣ Start with a project you use ‣ Use a

    resource to discover projects Find a project
  39. 43.
  40. 44.
  41. 45.
  42. 46.
  43. 47.
  44. 48.

    ‣ Is the project open source? ‣ Does it actively

    accept contributions? ‣ Is the project welcoming? Before you contribute
  45. 50.

    ‣ Give context ‣ Do your homework ‣ Keep requests

    short & direct ‣ Keep communication public ‣ Ask questions (but be patient) ‣ Respect decisions ‣ Keep it classy
  46. 52.

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

    high-level topic or idea ‣ Propose a new feature When to open an issue…
  47. 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…
  48. 54.
  49. 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…
  50. 57.
  51. 58.

    ‣ Fork the repository ‣ Clone & create a branch

    for your edits How to submit a PR
  52. 59.
  53. 60.

    ‣ Fork the repository ‣ Clone & create a branch

    for your edits ‣ Reference any relevant issues How to submit a PR
  54. 61.
  55. 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
  56. 63.
  57. 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