The document discusses the process of contributing to Plone, emphasizing the importance of making contributions as self-service as possible. It highlights common problems contributors face, such as ensuring pull requests do not break tests and meeting testing requirements for various Plone versions. Additionally, it mentions tools like GitHub, Jenkins, and Mr. Roboto to aid in automating tests and releases.

1. Paving roadsPaving roads

2. @me
github.com/gforcada
twitter.com/gforcada
work at der Freitag
@me
github.com/gforcada
twitter.com/gforcada
work at der Freitag

3. QUICK QUIZQUICK QUIZ

4. Made a pull request on github?Made a pull request on github?

5. jenkins.plone.org?jenkins.plone.org?

6. Run a pull request job?Run a pull request job?

7. mr.roboto?mr.roboto?

8. «Plone is hard to contribute to»«Plone is hard to contribute to»

9. Make contributions as self-service as possibleMake contributions as self-service as possible

10. Problems:
Is my pull request breaking any test?
Problems:
Is my pull request breaking any test?

11. Problems:
Is my pull request breaking any test?
Which plone versions do I need to test against?
Problems:
Is my pull request breaking any test?
Which plone versions do I need to test against?

12. Problems:
Is my pull request breaking any test?
Which plone versions do I need to test against?
Did I miss any important detail?
Problems:
Is my pull request breaking any test?
Which plone versions do I need to test against?
Did I miss any important detail?

13. Problems:
Is my pull request breaking any test?
Which plone versions do I need to test against?
Did I miss any important detail?
All contributors have signed the CLA?
Problems:
Is my pull request breaking any test?
Which plone versions do I need to test against?
Did I miss any important detail?
All contributors have signed the CLA?

14. mr.roboto to the rescue!mr.roboto to the rescue!

15. github, jenkins and mr.robotogithub, jenkins and mr.roboto

16. MORE?
code analysis reports
MORE?
code analysis reports
Already on selected packages

17. MORE?
code analysis reports
hints on adding documentation
MORE?
code analysis reports
hints on adding documentation

18. MORE?
code analysis reports
hints on adding documentation
no tests added
MORE?
code analysis reports
hints on adding documentation
no tests added

19. MORE?
code analysis reports
hints on adding documentation
no tests added
auto run tests
MORE?
code analysis reports
hints on adding documentation
no tests added
auto run tests

20. MORE?
code analysis reports
hints on adding documentation
no tests added
auto run tests
auto merge on successful
MORE?
code analysis reports
hints on adding documentation
no tests added
auto run tests
auto merge on successful

21. MORE?
code analysis reports
hints on adding documentation
no tests added
auto run tests
auto merge on successful
automatic releases
MORE?
code analysis reports
hints on adding documentation
no tests added
auto run tests
auto merge on successful
automatic releases

22. github.com/plone/mr.roboto
github.com/plone/jenkins.plone.org
github.com/plone/mr.roboto
github.com/plone/jenkins.plone.org

23. THANKS FOR
LISTENING!
THANKS FOR
LISTENING!