[Python-Dev] Re: EnHackathon 2019 - seeking core dev support
On Thu, Oct 31, 2019 at 3:30 PM Lewis Gaul wrote: > I'm happy to set up an EnHackathon channel - is IRC or Zulip preferred in > general? > I prefer Zulip since I can easily participate using my phone, as well as receive email notifications. It also makes searching and following previous discussion trivial, unlike with IRC. It would be reasonable to simply use the existing core/help Zulip stream for this purpose. - Tal ___ 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/GGXK2CSOJNXL2YAHXJBCANPJH33GXKOZ/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: EnHackathon 2019 - seeking core dev support
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 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 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/
[Python-Dev] Re: EnHackathon 2019 - seeking core dev support
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 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/ZXCN2ISIS2QKUTGF3JODVPRWIS2Z773H/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: EnHackathon 2019 - seeking core dev support
Hi Lewis. I'm in the Pacific time zone. Barring any surprises (I'm getting married late next month), I can commit to being online in the morning (the last few hours of your business day), as well as during my normal business hours (late evening/night for you). Just tag "@brandtbucher" on any PRs you'd like reviewed. You can also tag or email me directly with any questions you have. It would also help if you could nosy "brandtbucher" on any bpo issues you plan on working on. Looking forward to getting some new contributors! Brandt ___ 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/Z7SGJRZA5TAMN2O6VNFVPVA4XLNMVMFR/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: EnHackathon 2019 - seeking core dev support
Hi Brandt, Thanks a lot for offering to help out! Hopefully will also be a couple of core devs happy to help in November to avoid bottlenecks as much as possible. We'll be working between the hours of 10am-6pm UK time. Dates are TBC and can partly be flexible around when people like yourself are available. We still need to do some more work to identify candidate issues, but I'll let you know when we've done so (any suggestions from anyone are welcome!). I'll also make sure everyone is compliant with the standard requirements to get a PR merged. Thanks, Lewis On Sun, 20 Oct 2019, 16:25 Brandt Bucher, wrote: > Hi Lewis. > > I'm a trigger (not a core developer), but I'd be happy to make myself > available during that time for expedited PR reviews. Ideally, the core > review / merge stage would be your only bottleneck then. > > I'm a bit busy next month though, so do you know the actual dates / time / > time zones you plan to be working in? Also, are there any specific issues > you have identified that you want to work on within your stated areas of > interest? If so, I can do some homework before in order to speed up the > reviews. > > I'd recommend that all PR authors review the contributing section of the > developers guide beforehand: > https://devguide.python.org/pullrequest > > Specifically, make sure that every contributor has signed the CLA at least > a couple of business days before (it's often the longest blocker for > first-time contributions): > https://devguide.python.org/pullrequest/#licensing > > Looking forward to your help! > > Brandt > ___ > 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/5GMVGDLVCTP67VFMUBQDLWNNP22EADAU/ > Code of Conduct: http://python.org/psf/codeofconduct/ > ___ 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/PAM6DR5HTWRBXJOBGUVKOCFPF5C3A5YS/ Code of Conduct: http://python.org/psf/codeofconduct/
[Python-Dev] Re: EnHackathon 2019 - seeking core dev support
Hi Lewis. I'm a trigger (not a core developer), but I'd be happy to make myself available during that time for expedited PR reviews. Ideally, the core review / merge stage would be your only bottleneck then. I'm a bit busy next month though, so do you know the actual dates / time / time zones you plan to be working in? Also, are there any specific issues you have identified that you want to work on within your stated areas of interest? If so, I can do some homework before in order to speed up the reviews. I'd recommend that all PR authors review the contributing section of the developers guide beforehand: https://devguide.python.org/pullrequest Specifically, make sure that every contributor has signed the CLA at least a couple of business days before (it's often the longest blocker for first-time contributions): https://devguide.python.org/pullrequest/#licensing Looking forward to your help! Brandt ___ 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/5GMVGDLVCTP67VFMUBQDLWNNP22EADAU/ Code of Conduct: http://python.org/psf/codeofconduct/
