Anyone want to lead the sprints at PyCon US 2016?
The call has started to go out for sprint groups to list themselves online. Anyone want to specifically lead the core sprint this year? If no one specifically does then I will sign us up and do my usual thing of pointing people at the devguide and encourage people to ask questions but not do a lot of hand-holding (I'm expecting to be busy either working on GitHub migration stuff or doing other things that I have been neglecting due to my GitHub migration work). ---------- Forwarded message --------- From: Ewa Jodlowska <ewa@python.org> Date: Mon, 4 Apr 2016 at 07:14 Subject: [PSF-Community] Sprinting at PyCon US 2016 To: <psf-community@python.org> Are you coming to PyCon US? Have you thought about sprinting? The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5) of coding with many Python projects and their maintainers. And if you're coming to PyCon, taking part in the Sprints is easy! You don’t need to change your registration* to join the Sprints. There’s no additional registration fee, and you even get lunch. You do need to cover the additional lodging and other meals, but that’s it. If you’ve booked a room through the PyCon registration system, you'll need to contact the registration team at pycon2016@cteusa.com as soon as possible to request the extra nights. The sprinting itself (along with lunch every day) is free, so your only expenses are your room and other meals. If you're interested in what projects will be sprinting, just keep an eye on the sprints page on the PyCon web site at https://us.pycon.org/2016/community/sprints/ Be sure to check back, as groups are being added all the time. If you haven't sprinted before, or if you just need to brush up on sprinting tools and techniques, there will again be an 'Intro to Sprinting' session the evening of June 1, lead by Shauna Gordon-McKeon and other members of Python community. To grab a free ticket for this session, just visit https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-t... . *Please note that conference registration is sold out, but you do not need a conference registration to come to the Sprints. _______________________________________________ PSF-Community mailing list PSF-Community@python.org https://mail.python.org/mailman/listinfo/psf-community
We think we have a partial (and hopefully temporary) solution to the bugs email blockage: ipv6 has been turned off on bugs, so it is sending only from the ipv4 address. Google appears to be accepting the emails again. However, the IPV4 address has a poor reputation, and Verizon at least appears to be blocking it. So more work is still needed. --David
On 4/5/2016 3:56 PM, R. David Murray wrote:
We think we have a partial (and hopefully temporary) solution to the bugs email blockage: ipv6 has been turned off on bugs, so it is sending only from the ipv4 address. Google appears to be accepting the emails again. However, the IPV4 address has a poor reputation, and Verizon at least appears to be blocking it. So more work is still needed.
Switching back to Google from Verizon. How is bugs email sent differently from list email? What the latter does works fine, at least for gmail. -- Terry Jan Reedy
On 6 April 2016 at 11:27, Terry Reedy <tjreedy@udel.edu> wrote:
On 4/5/2016 3:56 PM, R. David Murray wrote:
We think we have a partial (and hopefully temporary) solution to the bugs email blockage: ipv6 has been turned off on bugs, so it is sending only from the ipv4 address. Google appears to be accepting the emails again. However, the IPV4 address has a poor reputation, and Verizon at least appears to be blocking it. So more work is still needed.
Switching back to Google from Verizon.
How is bugs email sent differently from list email? What the latter does works fine, at least for gmail.
bugs.python.org is currently sending notification emails directly to recipients, rather than routing them via the outbound SMTP server on mail.python.org. Reconfiguring it to relay notifications via the main outgoing server is the longer term fix, but an initial attempt at enabling that resulted in errors in the bugs.python.org mail logs, so David reverted to the direct email configuration for the time being. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
On Wed, 06 Apr 2016 12:21:04 +1000, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 6 April 2016 at 11:27, Terry Reedy <tjreedy@udel.edu> wrote: bugs.python.org is currently sending notification emails directly to recipients, rather than routing them via the outbound SMTP server on mail.python.org.
Correct.
Reconfiguring it to relay notifications via the main outgoing server is the longer term fix, but an initial attempt at enabling that resulted in errors in the bugs.python.org mail logs, so David reverted to the direct email configuration for the time being.
Specifically, I think we should clean up the issues that are causing reputation loss (which pretty much means dropping rietveld, although in theory we could fix rietveld instead if someone wants to finish Ezio's patch). And then we need to understand the issue that caused me to back out the change: something is sending null-Sender emails to multiple recipients. We may not need to fix it (mail.python.org rejected them but they may be useless messages), but we probably should. I suspect they are actual bounces, but I don't have the time to investigate further at this time. --David
R. David Murray writes:
again. However, the IPV4 address has a poor reputation, and Verizon at least appears to be blocking it. So more work is still needed.
Don't take Verizon's policy as meaningful. Tell Verizon customers to get another address. That is the only solution that works for Verizon subscribers for very long (based on 15 years of Mailman-Users posts), they have never been a high-quality email provider. Further, Verizon (as an email provider) is in the process of dying anyway (they are very much alive as the new owner of AOL), so improvements in their email practices have a likelihood of zero to the resolution of a C float.
On Wed, 06 Apr 2016 12:03:36 +0900, "Stephen J. Turnbull" <stephen@xemacs.org> wrote:
R. David Murray writes:
again. However, the IPV4 address has a poor reputation, and Verizon at least appears to be blocking it. So more work is still needed.
Don't take Verizon's policy as meaningful. Tell Verizon customers to get another address. That is the only solution that works for Verizon subscribers for very long (based on 15 years of Mailman-Users posts), they have never been a high-quality email provider. Further, Verizon (as an email provider) is in the process of dying anyway (they are very much alive as the new owner of AOL), so improvements in their email practices have a likelihood of zero to the resolution of a C float.
Yes, Mark reminded me that Verizon still isn't accepting mail from mail.python.org, despite multiple contacts from the postmaster team. So they are pretty much a lost cause and no one should use them for email, I think. However, the "poor reputation" comment came from the error message returned by gmail when it bounced the spam-bounce-reports bugs was trying to send to Ezio. --David
No one stepped forward to lead the sprints this year, so I will put myself as the sprint leader and lean on everyone else who appears to help. :) On Tue, 5 Apr 2016 at 09:36 Brett Cannon <brett@python.org> wrote:
The call has started to go out for sprint groups to list themselves online. Anyone want to specifically lead the core sprint this year? If no one specifically does then I will sign us up and do my usual thing of pointing people at the devguide and encourage people to ask questions but not do a lot of hand-holding (I'm expecting to be busy either working on GitHub migration stuff or doing other things that I have been neglecting due to my GitHub migration work).
---------- Forwarded message --------- From: Ewa Jodlowska <ewa@python.org> Date: Mon, 4 Apr 2016 at 07:14 Subject: [PSF-Community] Sprinting at PyCon US 2016 To: <psf-community@python.org>
Are you coming to PyCon US? Have you thought about sprinting?
The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5) of coding with many Python projects and their maintainers. And if you're coming to PyCon, taking part in the Sprints is easy!
You don’t need to change your registration* to join the Sprints. There’s no additional registration fee, and you even get lunch. You do need to cover the additional lodging and other meals, but that’s it. If you’ve booked a room through the PyCon registration system, you'll need to contact the registration team at pycon2016@cteusa.com as soon as possible to request the extra nights. The sprinting itself (along with lunch every day) is free, so your only expenses are your room and other meals.
If you're interested in what projects will be sprinting, just keep an eye on the sprints page on the PyCon web site at https://us.pycon.org/2016/community/sprints/ Be sure to check back, as groups are being added all the time.
If you haven't sprinted before, or if you just need to brush up on sprinting tools and techniques, there will again be an 'Intro to Sprinting' session the evening of June 1, lead by Shauna Gordon-McKeon and other members of Python community. To grab a free ticket for this session, just visit https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-t... .
*Please note that conference registration is sold out, but you do not need a conference registration to come to the Sprints.
_______________________________________________ PSF-Community mailing list PSF-Community@python.org https://mail.python.org/mailman/listinfo/psf-community
I was thinking about holding a Patch Review Party/Sprint, which would provide people unfamiliar with the Python dev process a way to contribute to the project and get familiar with running tests, applying patches and so forth. I have a list of easy-ish patches that I wanted to take a look at and I could expand that and use those as a starting for people who don't have any particular bug tracker issues in mind. I'm not a patch review guru by any means, though. Also not sure if this is a good idea or if this is just late night caffeine talking. 2016-04-28 20:07 GMT+01:00 Brett Cannon <brett@python.org>:
No one stepped forward to lead the sprints this year, so I will put myself as the sprint leader and lean on everyone else who appears to help. :)
On Tue, 5 Apr 2016 at 09:36 Brett Cannon <brett@python.org> wrote:
The call has started to go out for sprint groups to list themselves online. Anyone want to specifically lead the core sprint this year? If no one specifically does then I will sign us up and do my usual thing of pointing people at the devguide and encourage people to ask questions but not do a lot of hand-holding (I'm expecting to be busy either working on GitHub migration stuff or doing other things that I have been neglecting due to my GitHub migration work).
---------- Forwarded message --------- From: Ewa Jodlowska <ewa@python.org> Date: Mon, 4 Apr 2016 at 07:14 Subject: [PSF-Community] Sprinting at PyCon US 2016 To: <psf-community@python.org>
Are you coming to PyCon US? Have you thought about sprinting?
The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5) of coding with many Python projects and their maintainers. And if you're coming to PyCon, taking part in the Sprints is easy!
You don’t need to change your registration* to join the Sprints. There’s no additional registration fee, and you even get lunch. You do need to cover the additional lodging and other meals, but that’s it. If you’ve booked a room through the PyCon registration system, you'll need to contact the registration team at pycon2016@cteusa.com as soon as possible to request the extra nights. The sprinting itself (along with lunch every day) is free, so your only expenses are your room and other meals.
If you're interested in what projects will be sprinting, just keep an eye on the sprints page on the PyCon web site at https://us.pycon.org/2016/community/sprints/ Be sure to check back, as groups are being added all the time.
If you haven't sprinted before, or if you just need to brush up on sprinting tools and techniques, there will again be an 'Intro to Sprinting' session the evening of June 1, lead by Shauna Gordon-McKeon and other members of Python community. To grab a free ticket for this session, just visit https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-t... .
*Please note that conference registration is sold out, but you do not need a conference registration to come to the Sprints.
_______________________________________________ PSF-Community mailing list PSF-Community@python.org https://mail.python.org/mailman/listinfo/psf-community
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/camillamon%40gmail.com
On Fri, 6 May 2016 at 14:14 Camilla <camillamon@gmail.com> wrote:
I was thinking about holding a Patch Review Party/Sprint, which would provide people unfamiliar with the Python dev process a way to contribute to the project and get familiar with running tests, applying patches and so forth. I have a list of easy-ish patches that I wanted to take a look at and I could expand that and use those as a starting for people who don't have any particular bug tracker issues in mind. I'm not a patch review guru by any means, though. Also not sure if this is a good idea or if this is just late night caffeine talking.
I have absolutely no problem if you want to pitch this idea to new contributors who show up at the sprints! -Brett
2016-04-28 20:07 GMT+01:00 Brett Cannon <brett@python.org>:
No one stepped forward to lead the sprints this year, so I will put myself as the sprint leader and lean on everyone else who appears to help. :)
On Tue, 5 Apr 2016 at 09:36 Brett Cannon <brett@python.org> wrote:
The call has started to go out for sprint groups to list themselves online. Anyone want to specifically lead the core sprint this year? If no one specifically does then I will sign us up and do my usual thing of pointing people at the devguide and encourage people to ask questions but not do a lot of hand-holding (I'm expecting to be busy either working on GitHub migration stuff or doing other things that I have been neglecting due to my GitHub migration work).
---------- Forwarded message --------- From: Ewa Jodlowska <ewa@python.org> Date: Mon, 4 Apr 2016 at 07:14 Subject: [PSF-Community] Sprinting at PyCon US 2016 To: <psf-community@python.org>
Are you coming to PyCon US? Have you thought about sprinting?
The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5) of coding with many Python projects and their maintainers. And if you're coming to PyCon, taking part in the Sprints is easy!
You don’t need to change your registration* to join the Sprints. There’s no additional registration fee, and you even get lunch. You do need to cover the additional lodging and other meals, but that’s it. If you’ve booked a room through the PyCon registration system, you'll need to contact the registration team at pycon2016@cteusa.com as soon as possible to request the extra nights. The sprinting itself (along with lunch every day) is free, so your only expenses are your room and other meals.
If you're interested in what projects will be sprinting, just keep an eye on the sprints page on the PyCon web site at https://us.pycon.org/2016/community/sprints/ Be sure to check back, as groups are being added all the time.
If you haven't sprinted before, or if you just need to brush up on sprinting tools and techniques, there will again be an 'Intro to Sprinting' session the evening of June 1, lead by Shauna Gordon-McKeon and other members of Python community. To grab a free ticket for this session, just visit https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-t... .
*Please note that conference registration is sold out, but you do not need a conference registration to come to the Sprints.
_______________________________________________ PSF-Community mailing list PSF-Community@python.org https://mail.python.org/mailman/listinfo/psf-community
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/camillamon%40gmail.com
On 6 May 2016, at 14:38, Brett Cannon wrote:
On Fri, 6 May 2016 at 14:14 Camilla <camillamon@gmail.com> wrote:
I was thinking about holding a Patch Review Party/Sprint, which would provide people unfamiliar with the Python dev process a way to contribute to the project and get familiar with running tests, applying patches and so forth. I have a list of easy-ish patches that I wanted to take a look at and I could expand that and use those as a starting for people who don't have any particular bug tracker issues in mind. I'm not a patch review guru by any means, though. Also not sure if this is a good idea or if this is just late night caffeine talking.
I have absolutely no problem if you want to pitch this idea to new contributors who show up at the sprints!
-Brett
Camilla, I would be happy to support your effort. I find it a wonderful idea! Carol Carol Willing Research Software Engineer, Project Jupyter @ Cal Poly Director, Python Software Foundation
2016-04-28 20:07 GMT+01:00 Brett Cannon <brett@python.org>:
No one stepped forward to lead the sprints this year, so I will put myself as the sprint leader and lean on everyone else who appears to help. :)
On Tue, 5 Apr 2016 at 09:36 Brett Cannon <brett@python.org> wrote:
The call has started to go out for sprint groups to list themselves online. Anyone want to specifically lead the core sprint this year? If no one specifically does then I will sign us up and do my usual thing of pointing people at the devguide and encourage people to ask questions but not do a lot of hand-holding (I'm expecting to be busy either working on GitHub migration stuff or doing other things that I have been neglecting due to my GitHub migration work).
---------- Forwarded message --------- From: Ewa Jodlowska <ewa@python.org> Date: Mon, 4 Apr 2016 at 07:14 Subject: [PSF-Community] Sprinting at PyCon US 2016 To: <psf-community@python.org>
Are you coming to PyCon US? Have you thought about sprinting?
The coding Sprints are the hidden gem of PyCon, up to 4 days (June 2-5) of coding with many Python projects and their maintainers. And if you're coming to PyCon, taking part in the Sprints is easy!
You don’t need to change your registration* to join the Sprints. There’s no additional registration fee, and you even get lunch. You do need to cover the additional lodging and other meals, but that’s it. If you’ve booked a room through the PyCon registration system, you'll need to contact the registration team at pycon2016@cteusa.com as soon as possible to request the extra nights. The sprinting itself (along with lunch every day) is free, so your only expenses are your room and other meals.
If you're interested in what projects will be sprinting, just keep an eye on the sprints page on the PyCon web site at https://us.pycon.org/2016/community/sprints/ Be sure to check back, as groups are being added all the time.
If you haven't sprinted before, or if you just need to brush up on sprinting tools and techniques, there will again be an 'Intro to Sprinting' session the evening of June 1, lead by Shauna Gordon-McKeon and other members of Python community. To grab a free ticket for this session, just visit https://www.eventbrite.com/e/introduction-to-open-source-the-pycon-sprints-t... .
*Please note that conference registration is sold out, but you do not need a conference registration to come to the Sprints.
_______________________________________________ PSF-Community mailing list PSF-Community@python.org https://mail.python.org/mailman/listinfo/psf-community
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/camillamon%40gmail.com
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/willingc%40willingconsult...
participants (7)
-
Brett Cannon -
Camilla -
Carol Willing -
Nick Coghlan -
R. David Murray -
Stephen J. Turnbull -
Terry Reedy