Hi all, In early November this year I'll be leading the first ever Python 'EnHackathon' at the Ensoft Cisco office - we anticipate having ~10 first-time contributors, all with experience writing C and/or Python (and training in both). We each have up to 5 days (per year) to contribute, with my intention being to focus on contributing to CPython. We will be blogging about our experience (probably using GitHub pages) - I'll send out the URL when it's been set up.
Having spoken to people about this at PyCon UK this year and emailed on the core-mentorship mailing list, I'm posting here looking for any core devs who would be happy to provide us with some guidance. I'm wary of PR reviews being a blocker, and not wanting my co-contributors to feel disheartened by issues they're working on not reaching a resolution. We're open to working on almost any area of CPython, although particular areas of interest/familiarity might be: CPython core, re, unittest, subprocess, asyncio, ctypes, typing. There would be scope for us to work in small teams to work on more substantial issues if that is seen as a useful way to contribute, otherwise we can start with some of the easier issues on bpo. Would anyone here be willing to offer some support to help us reach our full potential? Please don't hesitate to contact me if you're interested in any way, or if you have any advice. If this year is a success there's a high probability we would look to do a similar thing in future years (with the experience from this year already in the bag)! Thanks, Lewis
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/Y6BVYZZVOE27YC24ZXELYBVGDGDB523V/ Code of Conduct: http://python.org/psf/codeofconduct/
