From ezio.melotti at gmail.com Sun Sep 6 13:21:06 2015 From: ezio.melotti at gmail.com (Ezio Melotti) Date: Sun, 6 Sep 2015 14:21:06 +0300 Subject: [core-workflow] GSoC-powered bugs.python.org improvements Message-ID: Hi, As you might be aware, during the summer we had two GSoC students (mentored by Hieu Nguyen and me) working on bugs.python.org (b.p.o). Shiyao (mentored by me) worked on: * a Mercurial plugin for b.p.o -- this allows to see, download/apply, and generate/upload patches from/to b.p.o. Source @ https://bitbucket.org/introom/hg-cpydev -- based on previous work by Nick Coghlan and Mercurial core-dev Pierre-Yves David; * patch analysis for b.p.o -- this allows b.p.o to analyze and extract metadata from patches that can be used to e.g. find all the patches that affect a specific file, or determine if a patch contains tests or docs changes. Source @ https://bitbucket.org/introom/python-dev/src -- based on previous work by anatoly techtonik and me; * a Docker image for b.p.o -- this should make things easier for folks who want to hack on the tracker itself. Source @ https://bitbucket.org/introom/docker-b.p.o; Chau (mentored by Hieu) worked on adding a REST interface to Roundup. This lays the foundations for easily developing future tools and enhancements for b.p.o, including better stats, dashboards, Kallithea/Phabricator integration, console-based roundup client, etc. Source @ https://bitbucket.org/kinggreedy1991/roundup-bpo . A more detailed report about Shiyao work can be found at https://bpaste.net/show/6da721ff90db . A more detailed report about Chau work can be found at https://bpaste.net/show/7e2303d2aa7a . The Docker image and the Mercurial plugin can already be used (even though they should probably be reviewed in detail, added to hg.python.org, and documented in the devguide). The patch analysis and REST interface still need to be reviewed in detail and integrated. After testing the REST interface on b.p.o, the plan is to backport it to upstream Roundup. Since both me and Hieu are currently fairly busy with work, any help is more than welcomed. I would also like to take this opportunity to thank Shiyao and Chau for all the work they did, Hieu for volunteering as mentor, and Nick and R. David for sharing their ideas and suggestions about the projects. Best Regards, Ezio Melotti From willingc at willingconsulting.com Sun Sep 6 16:45:45 2015 From: willingc at willingconsulting.com (Carol Willing) Date: Sun, 6 Sep 2015 07:45:45 -0700 Subject: [core-workflow] GSoC-powered bugs.python.org improvements In-Reply-To: References: Message-ID: <55EC5199.5020809@willingconsulting.com> Congrats to Shiyao and Chau for a productive GSoC. I'm looking forward to taking a look at the work that you have done. Thanks to Ezio and Hieu for serving as mentors and organizing these projects. Ezio, please let me know if there are specific next steps that would be most helpful. Bravo again Shiyao and Chau. Warmly, Carol On 9/6/15 4:21 AM, Ezio Melotti wrote: > Hi, > As you might be aware, during the summer we had two GSoC students > (mentored by Hieu Nguyen and me) working on bugs.python.org (b.p.o). > > Shiyao (mentored by me) worked on: > * a Mercurial plugin for b.p.o -- this allows to see, > download/apply, and generate/upload patches from/to b.p.o. Source @ > https://bitbucket.org/introom/hg-cpydev -- based on previous work by > Nick Coghlan and Mercurial core-dev Pierre-Yves David; > * patch analysis for b.p.o -- this allows b.p.o to analyze and > extract metadata from patches that can be used to e.g. find all the > patches that affect a specific file, or determine if a patch contains > tests or docs changes. Source @ > https://bitbucket.org/introom/python-dev/src -- based on previous work > by anatoly techtonik and me; > * a Docker image for b.p.o -- this should make things easier for > folks who want to hack on the tracker itself. Source @ > https://bitbucket.org/introom/docker-b.p.o; > > Chau (mentored by Hieu) worked on adding a REST interface to Roundup. > This lays the foundations for easily developing future tools and > enhancements for b.p.o, including better stats, dashboards, > Kallithea/Phabricator integration, console-based roundup client, etc. > Source @ https://bitbucket.org/kinggreedy1991/roundup-bpo . > > A more detailed report about Shiyao work can be found at > https://bpaste.net/show/6da721ff90db . > A more detailed report about Chau work can be found at > https://bpaste.net/show/7e2303d2aa7a . > > The Docker image and the Mercurial plugin can already be used (even > though they should probably be reviewed in detail, added to > hg.python.org, and documented in the devguide). The patch analysis > and REST interface still need to be reviewed in detail and integrated. > After testing the REST interface on b.p.o, the plan is to backport > it to upstream Roundup. > > Since both me and Hieu are currently fairly busy with work, any help > is more than welcomed. > > I would also like to take this opportunity to thank Shiyao and Chau > for all the work they did, Hieu for volunteering as mentor, and Nick > and R. David for sharing their ideas and suggestions about the > projects. > > Best Regards, > Ezio Melotti > _______________________________________________ > core-workflow mailing list > core-workflow at python.org > https://mail.python.org/mailman/listinfo/core-workflow > This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct From ncoghlan at gmail.com Mon Sep 7 00:40:56 2015 From: ncoghlan at gmail.com (Nick Coghlan) Date: Mon, 7 Sep 2015 08:40:56 +1000 Subject: [core-workflow] GSoC-powered bugs.python.org improvements In-Reply-To: <55EC5199.5020809@willingconsulting.com> References: <55EC5199.5020809@willingconsulting.com> Message-ID: On 7 September 2015 at 00:45, Carol Willing wrote: > Congrats to Shiyao and Chau for a productive GSoC. I'm looking forward to > taking a look at the work that you have done. Thanks to Ezio and Hieu for > serving as mentors and organizing these projects. Hear, hear! > Ezio, please let me know if there are specific next steps that would be most > helpful. And also whether there are areas where PSF grants may help in getting these contributions integrated into the production services and documentation. Regards, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia From bcannon at gmail.com Mon Sep 7 03:03:18 2015 From: bcannon at gmail.com (Brett Cannon) Date: Mon, 07 Sep 2015 01:03:18 +0000 Subject: [core-workflow] the Misc/NEWS problem In-Reply-To: References: <55C33014.40708@egenix.com> <20150806194604.D704D250FDE@webabinitio.net> <20150808201755.8198A250FB5@webabinitio.net> Message-ID: I forgot to follow up here that there was nary a peep from python-committers about the proposal of keeping NEWS entries in the issue tracker, so we have a green light to implement this idea. On Mon, Aug 10, 2015, 15:39 Brett Cannon wrote: > I have told python-committers of our plan to make sure it won't lead to a > revolt. > > On Sat, 8 Aug 2015 at 14:25 Brett Cannon wrote: > >> On Sat, Aug 8, 2015 at 1:18 PM R. David Murray >> wrote: >> >>> On Sat, 08 Aug 2015 17:44:04 -0000, Brett Cannon >>> wrote: >>> > OK, assuming David's in agreement then I think this approach wins with >>> the >>> > comma-separated field for commits that the hg hook for Roundup >>> auto-appends >>> > to and of course the field to enter the NEWS entry. >>> > >>> > Now the next question is how easy/hard is it to implement this, how >>> long >>> > will it take, and who is willing to do the work? With this in hand we >>> can >>> > propose it to python-committers for 3.6 since the NEWS file should be >>> easy >>> > enough to back-fill to this approach while its still small. >>> >>> Yes I agree this is the best approach, assuming we can get it >>> implemented. The advantage of #4, though, is that Ezio already did the >>> work. >>> >>> I'm *willing* to do the roundup work, but I don't know as I have the >>> required time, at least for the next month. Part of the trick is the >>> need to get a test instance set up...there was work done at PyCon and >>> after at making a tracker-in-a-box, so I'd need to find out where that >>> was at and learn how to use it (or finish it, if needed). The code >>> itself is probably a half-day job, probably including enhancing the hook >>> to update the commits field. But together with getting a working test >>> instance we're talking a couple days work at least. >>> >> >> Perk of getting the tracker-in-a-box working is it's a one-time cost that >> will be beneficial long term. >> >> I also don't think there is a rush since we still have to convince >> python-committers that this is the right solution. I plan to propose it on >> Monday to the list to make sure we have buy-in. >> >> >>> Writing the NEWS generating script is a not exactly trivial job, but >>> probably wants to wait until we have the REST API. So we'd have >>> upgrading our Roundup to that when it lands on the list as well, with a >>> 3.6 Beta 1 deadline on getting it all done. >>> >> >> Yeah, so we have a bit of time to worry about the generation script. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ezio.melotti at gmail.com Sat Sep 12 21:19:17 2015 From: ezio.melotti at gmail.com (Ezio Melotti) Date: Sat, 12 Sep 2015 22:19:17 +0300 Subject: [core-workflow] GSoC-powered bugs.python.org improvements In-Reply-To: References: <55EC5199.5020809@willingconsulting.com> Message-ID: On Mon, Sep 7, 2015 at 1:40 AM, Nick Coghlan wrote: > On 7 September 2015 at 00:45, Carol Willing > wrote: >> Congrats to Shiyao and Chau for a productive GSoC. I'm looking forward to >> taking a look at the work that you have done. Thanks to Ezio and Hieu for >> serving as mentors and organizing these projects. > > Hear, hear! > >> Ezio, please let me know if there are specific next steps that would be most >> helpful. > > And also whether there are areas where PSF grants may help in getting > these contributions integrated into the production services and > documentation. > I think testing the Mercurial plugin and moving it and its docs to hg.python.org / devguide would be a low-effort first step that anyone can do (perhaps it should be advertised on Python-dev too). Testing the Docker image and updating the tracker docs in the wiki would also be good, but this is mostly for people that hack on the tracker (so basically me and R. David). Reviewing/integrating/testing all the rest is a more complex task, as it requires both time and knowledge of the tracker, and that is something where a PSF grant might indeed help. Best Regards, Ezio Melotti > Regards, > Nick. > > -- > Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia From pierre-yves.david at ens-lyon.org Mon Sep 14 09:59:28 2015 From: pierre-yves.david at ens-lyon.org (Pierre-Yves David) Date: Mon, 14 Sep 2015 00:59:28 -0700 Subject: [core-workflow] Mercurial Sprints Message-ID: <55F67E60.6020201@ens-lyon.org> Greeting, Python people, The mercurial community gather twice in the next 2 months, some of you might be interested to attend. It would be a good opportunity to share use case, paint point and get some bug squashed. This thursday, we'll have a minisprint in San Francisco: - https://mercurial.selenic.com/wiki/201509MiniSprintBayArea From October 23th to 25th we'll have a bigger, global sprint in London: - https://mercurial.selenic.com/wiki/3.6sprint See you there ;-) -- Pierre-Yves David From barry at python.org Wed Sep 30 23:08:10 2015 From: barry at python.org (Barry Warsaw) Date: Wed, 30 Sep 2015 17:08:10 -0400 Subject: [core-workflow] PEP 507 - Git & GitLab Message-ID: <20150930170810.0b609d74@limelight.wooz.org> I'm not subscribed to this list directly, but I read it through Gmane. I've just published PEP 507 which proposes to move CPython development to Git and a hosted (donated or self TBD) GitLab instance. https://www.python.org/dev/peps/pep-0507/ All feedback is of course welcome, and if anybody else wants to hitch their ride to this pony, let me know and I'd be happy to add you as co-author of the PEP. Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: