From metatracker at psf.upfronthosting.co.za  Wed Jun  7 15:44:01 2017
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Wed, 07 Jun 2017 19:44:01 +0000
Subject: [Tracker-discuss] [issue589] Add GitHub PR to b.p.o issues using
 GitHub webhooks (depends on issue586)
In-Reply-To: <1464035377.63.0.520552418309.issue589@psf.upfronthosting.co.za>
Message-ID: <1496864641.25.0.26033452551.issue589@psf.upfronthosting.co.za>


Brett C. added the comment:

Can this be closed?

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue589>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Jun  7 16:08:29 2017
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Wed, 07 Jun 2017 20:08:29 +0000
Subject: [Tracker-discuss] [issue630] Add a way for a non-core dev to claim
 an issue
Message-ID: <1496866109.73.0.704174512103.issue630@psf.upfronthosting.co.za>


New submission from Brett C.:

Not sure if this should be a checklist to signify that an issue has been claimed by someone or simply a free-form text field where someone can enter their b.p.o username, but basically have some way that's a bit more formal than someone leaving a comment saying they want to try and tackle an issue.

----------
messages: 3350
nosy: brett.cannon
priority: feature
status: unread
title: Add a way for a non-core dev to claim an issue

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue630>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  8 01:19:11 2017
From: metatracker at psf.upfronthosting.co.za (Maciej Szulik)
Date: Thu, 08 Jun 2017 05:19:11 +0000
Subject: [Tracker-discuss] [issue589] Add GitHub PR to b.p.o issues using
 GitHub webhooks (depends on issue586)
In-Reply-To: <1464035377.63.0.520552418309.issue589@psf.upfronthosting.co.za>
Message-ID: <1496899151.3.0.589755101619.issue589@psf.upfronthosting.co.za>


Maciej Szulik added the comment:

I think we can.

----------
status: testing -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue589>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  8 01:23:41 2017
From: metatracker at psf.upfronthosting.co.za (Maciej Szulik)
Date: Thu, 08 Jun 2017 05:23:41 +0000
Subject: [Tracker-discuss] [issue463] HTTPS only version for login for this
 tracker
In-Reply-To: <1337666026.16.0.0159243982051.issue463@psf.upfronthosting.co.za>
Message-ID: <1496899421.36.0.714723573786.issue463@psf.upfronthosting.co.za>


Maciej Szulik added the comment:

We're currently working with Mark to migrate bpo to a different server. I'll make sure this is fixed along the way.

----------
nosy: +maciej.szulik

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue463>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  8 09:42:45 2017
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Thu, 08 Jun 2017 13:42:45 +0000
Subject: [Tracker-discuss] [issue631] Planet Python,
 https and rendering of the site.
Message-ID: <1496929365.82.0.813360696456.issue631@psf.upfronthosting.co.za>


New submission from St?phane Wirtel:

On the communicating.html page of devguide, there is a link to the planet python site, but this one is only in http. There is a support of https, the certificate seems to be good

$ echo | openssl s_client -servername www.planetpython.org -connect www.planetpython.org:443 2>/dev/null | openssl x509 -noout -dates

notBefore=Apr 27 16:10:00 2017 GMT
notAfter=Jul 26 16:10:00 2017 GMT

but Google Chromium and Firefox tell me that the connection is not fully compliant with https, and in fact, some images or css files are not reachable.

404 error

https://www.planetpython.org/js/iotbs2-key-directors-load.js
https://www.planetpython.org/js/iotbs2-directors.js
https://www.planetpython.org/js/iotbs2-core.js
https://www.planetpython.org/styles/defaultfonts.css

and because these files are missing, the rendering of the website is just ugly.

thank you

----------
files: Screenshot from 2017-06-08 15-42-09.png
messages: 3353
nosy: matrixise
priority: bug
status: unread
title: Planet Python, https and rendering of the site.

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue631>
_______________________________________________________
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2017-06-08 15-42-09.png
Type: image/png
Size: 114260 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20170608/77fdc685/attachment-0001.png>

From metatracker at psf.upfronthosting.co.za  Thu Jun  8 09:44:19 2017
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Thu, 08 Jun 2017 13:44:19 +0000
Subject: [Tracker-discuss] [issue632] planet python,
 not automatically redirected to https
Message-ID: <1496929459.64.0.121019252277.issue632@psf.upfronthosting.co.za>


New submission from St?phane Wirtel:

if we go to http://planetpython.org there is no automatic redirect to https://planetpython.org

thank you

----------
messages: 3354
nosy: matrixise
priority: feature
status: unread
title: planet python, not automatically redirected to https

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue632>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  8 10:17:07 2017
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 08 Jun 2017 14:17:07 +0000
Subject: [Tracker-discuss] [issue632] planet python,
 not automatically redirected to https
In-Reply-To: <1496929459.64.0.121019252277.issue632@psf.upfronthosting.co.za>
Message-ID: <1496931427.5.0.997318459226.issue632@psf.upfronthosting.co.za>


R David Murray added the comment:

The tracker is not planetpython.  Probably the right people to contact about this (or at least a good place to start) is the infrastructure team.

----------
nosy: +r.david.murray
priority: feature -> wish
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue632>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  8 10:18:26 2017
From: metatracker at psf.upfronthosting.co.za (R David Murray)
Date: Thu, 08 Jun 2017 14:18:26 +0000
Subject: [Tracker-discuss] [issue631] Planet Python,
 https and rendering of the site.
In-Reply-To: <1496929365.82.0.813360696456.issue631@psf.upfronthosting.co.za>
Message-ID: <1496931506.96.0.774651178863.issue631@psf.upfronthosting.co.za>


R David Murray added the comment:

As I noted on the other issue, this is the wrong place to report planetpython issues.

----------
nosy: +r.david.murray
priority: bug -> wish
status: unread -> resolved

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue631>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Jun  8 10:51:01 2017
From: metatracker at psf.upfronthosting.co.za (Berker Peksag)
Date: Thu, 08 Jun 2017 14:51:01 +0000
Subject: [Tracker-discuss] [issue631] Planet Python,
 https and rendering of the site.
In-Reply-To: <1496929365.82.0.813360696456.issue631@psf.upfronthosting.co.za>
Message-ID: <1496933461.87.0.21773207663.issue631@psf.upfronthosting.co.za>


Berker Peksag added the comment:

https://github.com/python/planet is probably the better place to report 404 errors.

----------
nosy: +berker.peksag

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue631>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  9 19:33:36 2017
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 09 Jun 2017 23:33:36 +0000
Subject: [Tracker-discuss] [issue633] b.p.o. and the attached PRs
Message-ID: <1497051216.3.0.0426335216539.issue633@psf.upfronthosting.co.za>


New submission from St?phane Wirtel:

in the interface of b.p.o, for an issue, if there is a PR, could we have the attached version of Python ?

for example, with this issue, there are 3 PR https://bugs.python.org/issue29870 but we don't know the affected version of Python.

Is it possible?

Thank you,

St?phane

----------
messages: 3358
nosy: matrixise
priority: feature
status: unread
title: b.p.o. and the attached PRs

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue633>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  9 19:36:10 2017
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 09 Jun 2017 23:36:10 +0000
Subject: [Tracker-discuss] [issue631] Planet Python,
 https and rendering of the site.
In-Reply-To: <1496929365.82.0.813360696456.issue631@psf.upfronthosting.co.za>
Message-ID: <1497051370.0.0.500988405138.issue631@psf.upfronthosting.co.za>


St?phane Wirtel added the comment:

done

https://github.com/python/planet/issues/230

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue631>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  9 19:36:57 2017
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?St=C3=A9phane_Wirtel?=)
Date: Fri, 09 Jun 2017 23:36:57 +0000
Subject: [Tracker-discuss] [issue632] planet python,
 not automatically redirected to https
In-Reply-To: <1496929459.64.0.121019252277.issue632@psf.upfronthosting.co.za>
Message-ID: <1497051417.83.0.567032051321.issue632@psf.upfronthosting.co.za>


St?phane Wirtel added the comment:

transferred to https://github.com/python/planet/issues/231

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue632>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  9 22:10:29 2017
From: metatracker at psf.upfronthosting.co.za (Mariatta)
Date: Sat, 10 Jun 2017 02:10:29 +0000
Subject: [Tracker-discuss] [issue634] Only link PR to the bpo that is in the
 PR title, not the body
Message-ID: <1497060629.6.0.388698227929.issue634@psf.upfronthosting.co.za>


New submission from Mariatta:

Regarding this PR: https://github.com/python/cpython/pull/2054

It has  bpo-30266 in the title, where the PR should be linked to.
But the PR body mentions another bpo number (bpo-25958), as a result this PR is also linked to bpo-25958. This PR should only be linked to bpo-30266.

When linking bpo and GitHub PR I think it should only look at the PR title, and not the body.

----------
messages: 3361
nosy: Mariatta
priority: bug
status: unread
title: Only link PR to the bpo that is in the PR title, not the body

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue634>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Jun  9 22:12:11 2017
From: metatracker at psf.upfronthosting.co.za (Mariatta)
Date: Sat, 10 Jun 2017 02:12:11 +0000
Subject: [Tracker-discuss] [issue634] Only link PR to the bpo that is in the
 PR title, not the body
In-Reply-To: <1497060629.6.0.388698227929.issue634@psf.upfronthosting.co.za>
Message-ID: <1497060731.67.0.270591286164.issue634@psf.upfronthosting.co.za>


Mariatta added the comment:

FYI I just unlinked the PR from bpo-25958

----------
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue634>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Jun 20 06:35:09 2017
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Tue, 20 Jun 2017 10:35:09 +0000
Subject: [Tracker-discuss] [issue633] b.p.o. and the attached PRs
In-Reply-To: <1497051216.3.0.0426335216539.issue633@psf.upfronthosting.co.za>
Message-ID: <1497954909.27.0.869504831433.issue633@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

If you hover with the mouse on the PR NNNN link in the PR list you will see the title which includes e.g. [3.5].
Perhaps it would be better to just display the title in that list.

----------
nosy: +ezio.melotti
status: unread -> chatting

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue633>
_______________________________________________________