Python loves your contributions

Slide 1

Slide 1 text

Python loves your contributions by Stéphane Wirtel PyCon Ukraine 2018 - Kharkiv - 04/28/2018 @matrixise - 1 / 103

Slide 2

Slide 2 text

PythonFOSDEM CPython contributor #fellow member of @ThePSF member of EuroPython Society I live in Belgium Hi PyCon! I am Stéphane @matrixise - 2 / 103

Slide 3

Slide 3 text

Contributing? @matrixise - 3 / 103

Slide 4

Slide 4 text

Chapter 1: The Code @matrixise - 4 / 103

Slide 5

Slide 5 text

Once upon a time... @matrixise - 5 / 103

Slide 6

Slide 6 text

a bunch of happy developers, @matrixise - 6 / 103

Slide 7

Slide 7 text

have developed a new language @matrixise - 7 / 103

Slide 8

Slide 8 text

Python @matrixise - 8 / 103

Slide 9

Slide 9 text

Nice!!! we are here only for this language ;-) @matrixise - 9 / 103

Slide 10

Slide 10 text

for them, the main tool for the management, for the issues, and the contributions was the issue tracker! @matrixise - 10 / 103

Slide 11

Slide 11 text

The Issue Tracker bugs.python.org aka b.p.o @matrixise - 11 / 103

Slide 12

Slide 12 text

The Issue Tracker could only handle the contributions as patches @matrixise - 12 / 103

Slide 13

Slide 13 text

one or many patch(es) @matrixise - 13 / 103

Slide 14

Slide 14 text

one or many patch(es) For the same issue @matrixise - 14 / 103

Slide 15

Slide 15 text

Rietveld for the reviews :-/ @matrixise - 15 / 103

Slide 16

Slide 16 text

Rietveld @matrixise - 16 / 103

Slide 17

Slide 17 text

Rietveld @matrixise - 17 / 103

Slide 18

Slide 18 text

Rietveld was Custom fork of the official Rietveld Maintained by one person Not really sexy No hightligted diff Not perfectly integrated with the Bug Tracker @matrixise - 18 / 103

Slide 19

Slide 19 text

Rietveld was Custom fork of the official Rietveld Maintained by one person Not really sexy No hightligted diff Not perfectly integrated with the Bug Tracker @matrixise - 19 / 103

Slide 20

Slide 20 text

Typical Work ow @matrixise - 20 / 103

Slide 21

Slide 21 text

Typical Work ow As a contributor Open an issue Checkout the CPython source code from hg.python.org Make the fix Upload a patch Have a review with Rietveld @matrixise - 21 / 103

Slide 22

Slide 22 text

Typical Work ow As a core dev Download the patch Make sure it still applies cleanly Fix the conflicts or ask a new patch to the contributor Run test suite manually (10-15 min) Commit the change manually Write the commit message Commit in the maintenance branches first and then merged in the default branch Run the test suite manually again Commit the merge Push the changes @matrixise - 22 / 103

Slide 23

Slide 23 text

Typical Work ow About the patch Is there a conflict? Who is the author? Is there a description? Where is the reference of revision? diff --git a/Misc/python.man b/Misc/python.man --- a/Misc/python.man +++ b/Misc/python.man @matrixise - 23 / 103

Slide 24

Slide 24 text

Typical Work ow About the continuous integration Check the buildbots (between 1h & 1d... if we are lucky) Frequent bugs on Windows the developers are on Linux or OSX or just too lazy If green, port to several branches can introduce new bugs in the other branches risk of conflicts tests executed by Buildbot @matrixise - 24 / 103

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Typical Work ow Status Download the sources from https://hg.python.org Use Patches Store them on bugs.python.org Use a custom version of Rietveld Complex Workflow @matrixise - 26 / 103

Slide 27

Slide 27 text

Di culty for the contribution @matrixise - 27 / 103

Slide 28

Slide 28 text

I am God! I want to contribute, change the work ow! @matrixise - 28 / 103

Slide 29

Slide 29 text

How? @matrixise - 29 / 103

Slide 30

Slide 30 text

Too simple ;-) @matrixise - 30 / 103

Slide 31

Slide 31 text

We have just switched to Git/GitHub! Read for more information: PEP 512: Migration from hg.python.org to Git/GitHub @matrixise - 31 / 103

Slide 32

Slide 32 text

The Open Hub 48% for SVN 37% for Git 2% for Mercurial PyPI 62% for Git 22% for Mercurial 13% for the rest Why Git? Git is 3 times more popupar as Mercurial for the top 100 projects on PyPI. @matrixise - 32 / 103

Slide 33

Slide 33 text

Why GitHub? GitHub is popular and familiar Primary place if you want to contribute to a project Avoid a custom infrastructure Concept of Pull Requests are easier to review have nice syntax hightligted diffs can be commented Web API ( REST & GraphQL ) @matrixise - 33 / 103

Slide 34

Slide 34 text

GitHub - Dashboards @matrixise - 34 / 103

Slide 35

Slide 35 text

GitHub - Web interface @matrixise - 35 / 103

Slide 36

Slide 36 text

GitHub - Reviews Integrated review Comment the code and ask for changes @matrixise - 36 / 103

Slide 37

Slide 37 text

GitHub - Reviews - Ready to merge @matrixise - 37 / 103

Slide 38

Slide 38 text

Migrations to GitHub 15th January 2016: PEPs 22nd July 2016: DevGuide 11st February 2017: CPython (2 years) @matrixise - 38 / 103

Slide 39

Slide 39 text

Automation @matrixise - 39 / 103

Slide 40

Slide 40 text

Run the test suite and the performance tests Run the code coverage Compile the documentation Execute for master and the stable branches (2.7, 3.6) Execute on the branches from the contributors Automation @matrixise - 40 / 103

Slide 41

Slide 41 text

The BOTS... @matrixise - 41 / 103

Slide 42

Slide 42 text

Job checks if the the commiter has signed the Contributor Agreement aka CLA The knights who say ni! https://github.com/python/the-knights-who-say-ni CLA: https://www.python.org/psf/contrib/contrib-form/ @matrixise - 42 / 103

Slide 43

Slide 43 text

Job checks the title of the PR with bedevere/issue-number has a Misc/NEWS.d/next entry with bedevere/news play with the labels awaiting review, awaiting merge, awaiting core review Bedevere! https://github.com/python/bedevere @matrixise - 43 / 103

Slide 44

Slide 44 text

Job based on needs backport to X.Y backports a Pull Request to an other branch merges a complete backport Miss Islington! https://github.com/python/miss-islington @matrixise - 44 / 103

Slide 45

Slide 45 text

BOTS + Automations = @matrixise - 45 / 103

Slide 46

Slide 46 text

BOTS + Automations = @matrixise - 46 / 103

Slide 47

Slide 47 text

BOTS + Automations = @matrixise - 47 / 103

Slide 48

Slide 48 text

as you can see BOTS are really useful for the core-devs @matrixise - 48 / 103

Slide 49

Slide 49 text

Status about the Work ow @matrixise - 49 / 103

Slide 50

Slide 50 text

Before Contributor Open an issue Clone Upload a patch Core Dev Wait a review of a Core Dev Download the patch Fix the conflicts Run the tests manually Run the code coverage manually Commit manually Write the commit message Merge into the branches Run the test suite manually Commit the merge Push the changes etc... process is long & manual & error prone @matrixise - 50 / 103

Slide 51

Slide 51 text

Slide 52

Slide 52 text

After Contributor Open an issue Clone Create a Pull Request Core Dev Review from contributors or core-dev Wait the feedback of the BOTS + Automation Wait the signal Mark the PR as needs backport to X.Y process is short & automatic @matrixise - 52 / 103

Slide 53

Slide 53 text

Slide 54

Slide 54 text

Statistics from Feb 2017 to Apr 2018 April is not yet nished @matrixise - 54 / 103

Slide 55

Slide 55 text

Pull Requests: 6542 @matrixise - 55 / 103

Slide 56

Slide 56 text

Merged Pull Requests: 4966 @matrixise - 56 / 103

Slide 57

Slide 57 text

Top Merge Time @matrixise - 57 / 103

Slide 58

Slide 58 text

Core-Devs & Contributors / Numbers @matrixise - 58 / 103

Slide 59

Slide 59 text

Core-Devs & Contributors / Pull Requests @matrixise - 59 / 103

Slide 60

Slide 60 text

Code @matrixise - 60 / 103

Slide 61

Slide 61 text

Documentation There is the PEP 545 for that!!! @matrixise - 61 / 103

Slide 62

Slide 62 text

Yeah! CPython loves your Pull Requests @matrixise - 62 / 103

Slide 63

Slide 63 text

Yeah! CPython loves your Pull Requests and @matrixise - 63 / 103

Slide 64

Slide 64 text

Your rst contribution could be the Ukrainian/Russian translation of the documentation. @matrixise - 64 / 103

Slide 65

Slide 65 text

Your rst contribution could be the Ukrainian/Russian translation of the documentation. Read PEP 545 @matrixise - 65 / 103

Slide 66

Slide 66 text

@matrixise - 66 / 103

Slide 67

Slide 67 text

Communication We have several channels: Mailing lists python-list@python.org python-dev@python.org python-ideas@lists.python.org core-mentorship@python.org IRC (irc://irc.freennode.net/#python-dev) @matrixise - 67 / 103

Slide 68

Slide 68 text

Communication ZulipChat @matrixise - 68 / 103

Slide 69

Slide 69 text

Then @matrixise - 69 / 103

Slide 70

Slide 70 text

We are ready for the future! @matrixise - 70 / 103

Slide 71

Slide 71 text

Chapter 2: The Community @matrixise - 71 / 103

Slide 72

Slide 72 text

 -> Language and Community  Brett Cannon, PyCon US 2014 @matrixise - 72 / 103

Slide 73

Slide 73 text

The Python Community is respectful, safe and open! Code of Conduct @matrixise - 73 / 103

Slide 74

Slide 74 text

Contributions @matrixise - 74 / 103

Slide 75

Slide 75 text

Contributions Mailing lists IRC / slack channels / ZulipChat Meetups PyLadies DjangoGirls (Kiev, Kharkov?) Sprints PyCons @matrixise - 75 / 103

Slide 76

Slide 76 text

Who organise? @matrixise - 76 / 103

Slide 77

Slide 77 text

Who organise? you! @matrixise - 77 / 103

Slide 78

Slide 78 text

Who organise? you! me! @matrixise - 78 / 103

Slide 79

Slide 79 text

Who organise? you! me! all of us! @matrixise - 79 / 103

Slide 80

Slide 80 text

Conferences PyCon Ukraine 2018 PyCon US in Cleveland (USA) EuroPython 2018 (Edinburgh / UK) @matrixise - 80 / 103

Slide 81

Slide 81 text

Conferences PyCon Ukraine 2018 PyCon US in Cleveland (USA) EuroPython 2018 (Edinburgh / UK) but also a lot of conferences DjangoCon Europe PyCon CZ 2018 (Prague / Czech Republic) PyCon PL 2018 (Ossa / Poland) ... https://python.org/events @matrixise - 81 / 103

Slide 82

Slide 82 text

Slide 83

Slide 83 text

DjangoGirls &| PyLadies @matrixise - 83 / 103

Slide 84

Slide 84 text

PyLadies http://www.pyladies.com/ @matrixise - 84 / 103

Slide 85

Slide 85 text

DjangoGirls https://djangogirls.org/kharkiv/ @matrixise - 85 / 103

Slide 86

Slide 86 text

How to become a good contributor Is there a recipe? @matrixise - 86 / 103

Slide 87

Slide 87 text

No! @matrixise - 87 / 103

Slide 88

Slide 88 text

No! maybe you will fail, but at least, you tried an initiative! @matrixise - 88 / 103

Slide 89

Slide 89 text

Chapter 3 @matrixise - 89 / 103

Slide 90

Slide 90 text

PSF Mission "The mission of the Python Software Foundation is to promote, protect, and advance the Python programming language, and to support and facilitate the growth of a diverse and international community of Python programmers". @matrixise - 90 / 103

Slide 91

Slide 91 text

Python Software Foundation Intellectual Property Members Money @matrixise - 91 / 103

Slide 92

Slide 92 text

Intellectual Property Software Licenses Trademarks @matrixise - 92 / 103

Slide 93

Slide 93 text

Members Basic (non-voting) Supporting Contributing/Managing Fellows @matrixise - 93 / 103

Slide 94

Slide 94 text

Money comes from... Donations Sponsorships PyCon US @matrixise - 94 / 103

Slide 95

Slide 95 text

Money goes to... Other PyCons Workshops Meetups fees Software projects Infrastructure Employees ... @matrixise - 95 / 103

Slide 96

Slide 96 text

The PSF is NOT the Python Community, you are a member of this awesome Community @matrixise - 96 / 103

Slide 97

Slide 97 text

Think globally; act locally Join the PSF (it's free) Engage with a community (or start one) Contribute - organise/mentor/code @matrixise - 97 / 103

Slide 98

Slide 98 text

What Can I Do for Python ? @matrixise - 98 / 103

Slide 99

Slide 99 text

What Can I Do for Python ? now, you know! @matrixise - 99 / 103

Slide 100

Slide 100 text

The contribution is for... @matrixise - 100 / 103

Slide 101

Slide 101 text

@matrixise - 101 / 103

Slide 102

Slide 102 text

Thank you! Дякую @matrixise stephane@wirtel.be @matrixise - 102 / 103

Slide 103

Slide 103 text

@matrixise - 102 / 103

Slide 104

Slide 104 text

Credits Talks Naomi Ceder for her presentation "Stay for the community" Brett Cannon for his sentence "Came for the language, stayed for the community" Images http://www.pierre-leautey.fr/lagence-de-communication-et-marketing-ds- consulting-de-pierrette-sicot/ @matrixise - 103 / 103