[python-committers] Roundup to GitHub Issues migration

During the next phase I will work with the WG to sort out all the major issues that we might encounter, and then I will once again reach out to you to gather feedback from the wider audience that follows these mailing lists. Best Regards, Ezio Melotti ___

[python-committers] PEP 595: Improving bugs.python.org

://www.python.org/dev/peps/pep-0588/ The full text of the PEP is include below. We are planning to update the PEP to include the feedback we receive and to update the status of features as we implement them (we also have a Google Summer of Code students working on it). Best Regards, Ezio Melotti

Re: [python-committers] [Python-Dev] PEP 581 (Using GitHub issues for CPython) is accepted

s. (This might also be a symptom of a wider problem caused by the fragmentation of the discussions between the old MLs, discuss, zulip, IRC, GitHub PRs and issues, and IRL meetings, but this is a separate topic.) Best Regards, Ezio Melotti > > The PEP 581 has been (first?) discusse

Re: [python-committers] Steering Council Update for April 2019

On Sun, Apr 28, 2019 at 11:58 PM Guido van Rossum wrote: > > On Sun, Apr 28, 2019 at 2:05 PM Ezio Melotti wrote: >> >> On Sat, Apr 27, 2019 at 10:44 PM Guido van Rossum wrote: >> > >> > On Sat, Apr 27, 2019 at 11:10 AM Victor Stinner >> > wrote

Re: [python-committers] Steering Council Update for April 2019

On Sat, Apr 27, 2019 at 10:44 PM Guido van Rossum wrote: > > On Sat, Apr 27, 2019 at 11:10 AM Victor Stinner wrote: >> >> Would it be possible to discuss these PEPs on python-dev? Or is it a >> deliberate choice to not let non core dev to be involved in the discussion? > > > It was not a

Re: [python-committers] Steering Council Update for April 2019

ker at upfronthosting is gone for good, but nothing is lost, we have backups and can retrieve the patches if we need them. Best Regards, Ezio Melotti > --Berker ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Comments on moving issues to GitHub

rsonally don't care; heck write it from scratch like Warehouse if that's > what it takes), but unless we get some people to step forward to help with > b.p.o then I personally consider it our temporary solution until we figure > out where we're going next with

Re: [python-committers] Let's give commit privileges to Nathaniel J. Smith

+1 On Thu, Jan 25, 2018 at 12:23 AM, Yury Selivanov wrote: > Hi, > > I want to propose granting commit privileges to Nathaniel J. Smith. > He's interested in the idea of becoming a core developer, and given > the quality of his contributionsI think he won't need any

Re: [python-committers] Julien Palard not seen as a core dev on the bug tracker

Done as well! On Mon, Dec 18, 2017 at 3:47 PM, Victor Stinner <victor.stin...@gmail.com> wrote: > Oh, Julien told me that he doesn't have the bug triage permission > neither. Would you mind to allow him to close bugs as well? :-) > > Victor > > 2017-12-18 14:57 GMT+01:00

Re: [python-committers] Julien Palard not seen as a core dev on the bug tracker

the bug tracker: > https://bugs.python.org/user23063 > > His nick name is "mdk". Can someone please fix his bpo account? > Done, and welcome to the team Julien! Best Regards, Ezio Melotti > Devguide: https://devguide.python.org/coredev/#issue-tracker > > Victor

Re: [python-committers] Requirements to get the "bug triage" permission?

On Fri, Dec 8, 2017 at 5:32 PM, Victor Stinner <victor.stin...@gmail.com> wrote: > 2017-12-08 17:19 GMT+01:00 Ezio Melotti <ezio.melo...@gmail.com>: >>> Aha. Maybe we need some tooling, like statistics on contributions to the >>> bug tracker, just to de

Re: [python-committers] Requirements to get the "bug triage" permission?

t of these suggestions seem to help define the process, ISTM they are also making it more bureaucratic. > > R. David Murray <rdmur...@bitdance.com>: >>> Maybe we can give some guide lines on how to behave on the bug >>> tracker? >> >> Enhance the bug triage section

Re: [python-committers] Statistics: growth of core dev number vs growth of the code size/complexity

re were still plenty of low hanging fruits on the bug tracker or other issues to work on. Then Python 3 came, and there was more work to be done. Nowadays the situation is much better, Python is more stable and mature, and what's left is more difficult, obscure, or controversial. There are still new modules and features being added and ISTM that most of the new core devs are working on those (e.g. asyncio/typing/etc), but otherwise finding new easy issues is becoming increasingly more difficult. Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] RFC: Process to become a core developer

her core devs and the community in general; 2) reach to the mentor only when necessary (i.e. no one else replied, something import/urgent/"personal"). For GSoC the situation is different: 1) GSoC students have to work on a specific project with specific goals, requirements, and deadlines;

Re: [python-committers] Requirements to get the "bug triage" permission?

ve one more helping hand. If the contributor knows what they are doing and they are helpful, we can "award" them with the triager bit, but this award shouldn't be given for unrelated accomplishments. Becoming a triager is a step to becoming a committer: we bestow them with some respons

Re: [python-committers] Requirements to get the "bug triage" permission?

don't have a well defined procedure and sometimes people keep contributing for weeks before someone realizes they could become triagers. To avoid this, we can either: 1) let contributors know that they could ask for more power if they think they can handle it; 2) be more proactive and check regula

Re: [python-committers] What is a CPython core developer?

en I became less active other people took over with not many repercussions. For more specific areas (e.g. html.parser or Unicode) I still try to participate to the discussions. For the bug tracker I have to commit long-term because other devs lack the time and/or knowledge required to maintain it.

Re: [python-committers] Should I merge a PR that I approved if it was written by a different core developer?

r. If you merge other core devs' patches, you are likely to get blamed when something breaks even if the code wasn't yours, and if the author runs away and you want someone else to blame, you can always find all the reviews by looking at the PR referenced by the changet :) Best Regards, Ezio Melott

Re: [python-committers] Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California

Hi, I signed up but haven't heard any news yet. September is approaching, so it would be great to know if you are still deciding/negotiating or if you already know the names :) Best Regards, Ezio Melotti On Tue, Jun 13, 2017 at 1:04 AM, Lukasz Langa <luk...@langa.pl> wrote: > Hel

Re: [python-committers] Spurious bugs.p.o messages

at least until we discover that there is something that needs to > automated about numbers. > > What I would like is that the BPO issue # in the PR title be a link so it is > easy to jump from PR to BPO. > There are some discussion about it, I think on the core-workflow iss

Re: [python-committers] 4 weeks with the new workflow: what needs changing?

y we will put the image on DockerHub. > Fifth, anything I missed? :) > I find the documentation in the devguide still lacking. I've been trying to improve it, but first I have to figure out all the details of the new workflow. Best Regards, Ezio Melotti __

Re: [python-committers] Mercurial commit url is broken

rks now -- not sure if someone fixed it in the meanwhile. Best Regards, Ezio Melotti > ... which displays short error message: > --- > Usage: /lookup/GITHEXHASH or gitGITHEXHASH (10, 11, or 40 hex characters) > /lookup/HGHEXNODE or hgHGHEXNODE (12 or 40 hex characters) > /lookup/rSVNREV

Re: [python-committers] New Roundup notifications on Git commits?

ould it be possible to mention the author instead of > the commiter? Or maybe mention both? > If GitHub passes the information along (and it probably does), then it should be possible to have both. Please create an issue on the meta-tracker to keep track of this. Best Regar

Re: [python-committers] New Roundup notifications on Git commits?

for your merge > got rejected due to the bad cert then it would have been dropped. > Today I also spotted and fixed another issue, and verified that now the messages are showing up on bpo (see e.g. http://bugs.python.org/issue29557#msg287801). Let me know if there are other issues. Best

Re: [python-committers] Discussions on PRs

; Discussion on the PRs would then only be for code review > aspects. > Yes, discussions on the PRs replace the discussions we had on Rietveld -- they should only be about the code review. Best Regards, Ezio Melotti > Thanks, > -- > Marc-Andre Lemburg > eGenix.com

Re: [python-committers] New Roundup notifications on Git commits?

I've been keeping an eye on the tracker logs and saw no errors. If you are still having problems after the SSL fix let me know. On Mon, Feb 13, 2017 at 8:16 PM, Brett Cannon wrote: > There was an issue up until sometime on Sunday where the SSL cert for > bugs.python.org was

Re: [python-committers] My cavalier and aggressive manner, API change and bugs introduced for basically zero benefit

it becomes to follow all the new features that get introduced. As for what would get me involved again, for my case there's not much else you can do -- I just need to find more free time, catch up with development (mails, tools, features, etc) and then try to keep up. Best Regards, Ezio Melotti [0]:

Re: [python-committers] commit privs given to Maciej Szulik for bugs.python.org work

On Sat, Dec 24, 2016 at 12:37 AM, Victor Stinner wrote: > 2016-12-23 19:07 GMT+01:00 Brett Cannon : >> Maciej has been helping Ezio, David, and me out with updates to >> bugs.python.org for the GitHub migration and he's reached a point where we >> are

Re: [python-committers] Making the PSF CoC apply to core developers

ight however serve as a remainder to people that disregard (intentionally or not) these principles, and help shaping the image of our community for external people -- including potential new members of our community. Best Regards, Ezio Melotti [0]: "A code of conduct is a set of ru

Re: [python-committers] Deprecation Policy PEP

On Sat, Jan 30, 2016 at 4:08 AM, Martin Panter wrote: >> What and when to deprecate >> == >> >> * The number of releases before an API is removed is decided >> on a case-by-case basis depending on widely used the API is > > depending on [how] widely

Re: [python-committers] We will be moving to GitHub (hopefully) in 2016

t. > > In the specific case of Roundup, does the linkifier have the "date of > comment" info available? If so, it could fairly readily assume that > hashes prior to the cutover date are hg ones, and later ones are for > git. By looking at the code I don't see it readily av

Re: [python-committers] emails from bugs.python.org are marker as spam

ate a GMail filter and check "never send to spam". The issue is also being discussed at http://psf.upfronthosting.co.za/roundup/meta/issue562 Best Regards, Ezio Melotti > Yury ___ python-committers mailing list python-committers@python.org

Re: [python-committers] Proposed core developer for contributing to multiprocessing

Hi, On Fri, Jan 9, 2015 at 11:47 PM, M.-A. Lemburg m...@egenix.com wrote: On 09.01.2015 23:26, Ezio Melotti wrote: Hi, On Fri, Jan 9, 2015 at 1:09 PM, M.-A. Lemburg m...@egenix.com wrote: BTW: How about having an incubator phase for new core devs ? The new candidate will get commit rights

Re: [python-committers] Proposed core developer for contributing to multiprocessing

(but that shouldn't happen). Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Mark Lawrence

that a try yet. Best Regards, Ezio Melotti Scattergun pinging of open issues is one of the easiest, but also one of the ones with a high hidden cost in annoying people - for developers, it may mean getting dozens of email notifications, for issue submitters, it may lead to anticipation

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

. (And FTR I don't think I'm wasting my time -- if anything I'm sharpening my already nearly-limitless patience ;). Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python

Re: [python-committers] The evolution of HTMLParser

On Wed, Nov 20, 2013 at 10:34 PM, Antoine Pitrou anto...@python.org wrote: On mer., 2013-11-20 at 21:57 +0200, Ezio Melotti wrote: Now I'm working on #13633 (Automatically convert character references in HTMLParser [1]), and I'm planning to add a convert_charrefs boolean flag

Re: [python-committers] Zachary Ware for commit access?

to the team. I can also help supervising him if necessary. Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] [Infrastructure] [Pydotorg] XSS security issue

the code of roundup is hardly their domain. Ezio Melotti (cc'd) did a lot of work on the Python installation of roundup, so he may have a better idea. We have a security mailing list but that is mainly intended for security issues in the language: secur...@python.org secur

Re: [python-committers] Language Summit at EuroPython

informally during the conference if someone is interested. Best Regards, Ezio Melotti If I get a lot of topics I'll inquire about getting a room set aside for a couple of hours. Cheers, /arry ___ python-committers mailing list python-committers@python.org

[python-committers] Language Summit at EuroPython

Hi, are there any plans about doing a language summit at EuroPython this year? Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] hg clone cpython newrepo aborts

On Tue, May 28, 2013 at 9:47 PM, Terry Reedy tjre...@udel.edu wrote: On 5/28/2013 10:19 AM, Dirkjan Ochtman wrote: It's possible something broke with the @-filename. I am planning to change '@' to '_' anyway. What's wrong with just README or README.txt? Best Regards, Ezio Melotti

Re: [python-committers] what's going on with Misc/NEWS?

going to cause more troubles. Best Regards, Ezio Melotti As I side note, before committing I always do an hg diff to check that everything is OK. Misc/NEWS is usually the last file in the diff, so I just copy the first sentence of the entry and use it in the commit message. * this is also valid

Re: [python-committers] Tracker settings for Peter Moody

though they aren't committers (yet :). Correct. The committer flag only controls the icon, as far as I remember. FTR the nosy autocomplete uses both the experts index and the list of tracker users with the is committer flag. Best Regards, Ezio Melotti --David

Re: [python-committers] Anatoly Techtonik's contribution

lawyer? Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Anatoly Techtonik's contribution

the one at the bottom of http://code.google.com/legal/individual-cla-v1.0.html should be used instead of printing/scanning/mailing the agreement (this (or some similar suggestion) already came up a few times here). Best Regards, Ezio Melotti But even if people don't like the explicit steps as I

Re: [python-committers] Anatoly Techtonik's contribution

Hi, On Tue, Jan 1, 2013 at 7:06 PM, Jesse Noller jnol...@gmail.com wrote: On Jan 1, 2013, at 11:54 AM, Ezio Melotti ezio.melo...@gmail.com wrote: Hi, [...] We also discussed about the contributor agreement and IIUC: 1) he signed it already 1.5 years ago but apparently it got lost

Re: [python-committers] Anatoly Techtonik's contribution

the issue is today. AFAIU he's willing to sign it again -- nonetheless the issues mentioned in my previous mail remain. Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python

Re: [python-committers] Anatoly Techtonik's contribution

Hi, On Tue, Jan 1, 2013 at 10:57 PM, Georg Brandl g.bra...@gmx.net wrote: On 01/01/2013 05:54 PM, Ezio Melotti wrote: I say Ezio lets him know that this is the plan since he talked to him recently and is in the no-ban-yet camp. Yesterday I talked to him, informed him about

Re: [python-committers] Anatoly Techtonik's contribution

. I'm willing to make an attempt myself, as I think I have a quite clear idea of the problem. Best Regards, Ezio Melotti cheers, Georg ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python

Re: [python-committers] Anatoly Techtonik's contribution

On Wed, Dec 26, 2012 at 5:07 PM, Łukasz Langa luk...@langa.pl wrote: Dnia 26 gru 2012 o godz. 15:09 Ezio Melotti ezio.melo...@gmail.com napisał(a): The community should ignore the tone of the messages or even the messages themselves and most importantly avoid replies that convey the same

Re: [python-committers] Anatoly Techtonik's contribution

him is already negatively biased and leads us to be less tolerant with him At the end he thanked me for bringing this up with him, and apparently he is willing to improve. Best Regards, Ezio Melotti ___ python-committers mailing list python-committers

Re: [python-committers] Anatoly Techtonik's contribution

On Wed, Dec 26, 2012 at 7:37 PM, R. David Murray rdmur...@bitdance.comwrote: On Wed, 26 Dec 2012 18:20:06 +0200, Ezio Melotti ezio.melo...@gmail.com wrote: On Wed, Dec 26, 2012 at 5:07 PM, Łukasz Langa luk...@langa.pl wrote: I don't want to spell out names but I've had more than one

[python-committers] Commit privileges for Chris Jerdonek

. Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Django running in debug mode on bugs.python.org

, -- Alexandre It used to be set to True but IIRC at some point I changed it to be False. Unless someone changed this intentionally, it's likely that the change got lost when the repo got moved to HG. Best Regards, Ezio Melotti ___ python-committers mailing list

Re: [python-committers] Three wishes for Mercurial-Roundup integration

, on the basis that duplicate bug should be sorted out in the tracker, but the majority here is in favor. I’ll wait a bit for other opinions. Clearly with -1 I meant wishes -= 1, since now even this last one should be fixed ;) (http://hg.python.org/hooks/rev/ebdd1c1c365b) Best Regards, Ezio Melotti

Re: [python-committers] Commit rights for Petri?

FI and he was the most active contributor of the group. Best Regards, Ezio Melotti cheers Antoine. ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Commit rights for Meador Inge

on irc.freenode.net. There you can get real-time updates about commits, new messages posted on the tracker, the buildbots status, and you can also get in touch with other developers. Best Regards, Ezio Melotti -- Meador ___ python-committers mailing

Re: [python-committers] Three wishes for Mercurial-Roundup integration

. It would be useful for the devguide repo too, now that we have a 'devguide' component (and possibly for 'benchmarks' too, as you suggested on #python-dev). Thanks in advance Best Regards, Ezio Melotti ___ python-committers mailing list python-committers

Re: [python-committers] Committer rights for Sandro Tosi

Hi, On 03/08/2011 3.29, Pat Campbell wrote: Hi Ezio: Okay, and yes, please have Sandro submit a contributor agreement. He should have sent it already yesterday morning, via fax. Best Regards, Ezio Melotti Thanks, Pat ___ python-committers

Re: [python-committers] Committer rights for Sandro Tosi

my interactions with him I don't think we need to have any worry about his going crazy with code commits...he's very aware of the need to be conservative and get reviews. Ezio, are you volunteering to be his mentor? If so, then definitely +1. Sure. Best Regards, Ezio Melotti -- R. David

[python-committers] Committer rights for Sandro Tosi

the contributor agreement yet but he will do it as soon as he finds a printer/scanner/camera/fax. Best Regards, Ezio Melotti ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Jean Paul-Calderone Commit Access

On 05/04/2010 16.56, Michael Foord wrote: Hello all, I would like to propose Jean-Paul Calderone (exarkun) for commit access. He is a core-twisted developer and a very experienced Python developer with a passionate belief in good testing. He also regularly comments the issue tracker. Twisted