Hi Tal, Brandt, Chris, Kyle, Thank you all for offering to support us in one way or another. Just to update with our plans:
- We have 12 contributors who have agreed to spend on average 4 days in November contributing. - The blog will be up tomorrow at http://enhackathon.github.io/ - already two blog posts waiting to go! - Our first day of EnHackathon contribution will be on Monday 4th November (sorry for short notice) when we will try to form a more concrete plan for the remaining days. - We will spend 2 days contributing the following week (perhaps Tues-Weds 12th-13th November). - We will spend the last 2 days the following week. I'm happy to set up an EnHackathon channel - is IRC or Zulip preferred in general? Please let me know if there are specific dates that are better than others for you - we can be flexible with the last 4 days, and all the support we can get is greatly appreciated! Thanks, Lewis On Mon, 28 Oct 2019 at 20:55, Tal Einat <talei...@gmail.com> wrote: > Hi Lewis, > > As I mentioned in our earlier conversation, I'd be happy to help! > > I'm in the UTC+2 timezone so hopefully I should be available for live > support for most of your working hours. I suggest setting up a dedicated > channel for online communication, e.g. an IRC channel or Zulip stream (with > Zulip I'll also be available via my phone.) > > Please update ASAP regarding the exact dates so I can let you know when > I'll be available and try to increase my availability during that period. > > I am unfortunately barely familiar with most of the interest areas you've > mentioned, with unittest being the exception. I'll still be able to assist, > but perhaps not as well as an expert on these would be. I suggest > contacting the experts on the relevant library modules directly regarding > this, mostly to ask what they think would be most helpful and whether they > have any preferences or requests, but also regarding their availability to > help before, during and after. > > - Tal Einat > > P.S. Apologies for the delayed reply, I'm working back through my email > backlog after a vacation. > > On Sun, Oct 20, 2019 at 3:04 PM Lewis Gaul <le...@scphillips.com> wrote: > >> 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/IFSE5U6CB3EXPVYRJOJJIKUD6R5QL2LP/ Code of Conduct: http://python.org/psf/codeofconduct/
