reflect infrastructure move of bugs.python.org (to server bugs.ams1.psf.io)
Nobody has claimed this yet.
- Dominant language
- Hurl
- Stars
- 124
- Forks
- 67
- Avg merge
- 8h 40m
- Merged PRs (30d)
- 5
Description
At some time the infrastructure for bugs.python.org was moved to a different server.
It is very likely that it was moved off a server from Upfront Systems as still written in the overview, this would need to be corrected. The new server should be added to the list of server (and hopefully with ssh pubkey fingerprints as recommended by #104 :) )
details about the infrastructure move
See this comment: https://github.com/python/psf-infra-meta/issues/4#issuecomment-449401710
And a current ping shows that this is not psf.upfronthosting.co.za anymore:
date -u ; ping -c 1 bugs.python.org
Mi 6. Mär 08:57:38 UTC 2019
PING bugs.python.org (188.166.48.69) 56(84) bytes of data.
64 bytes from bugs.ams1.psf.io (188.166.48.69): icmp_seq=1 ttl=56 time=16.7 ms
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the infrastructure overview and server list referenced in the issue, then read the linked infrastructure-move comment and verify the current bugs.ams1.psf.io details. Done means removing the outdated Upfront Systems reference, adding the new server, and recording SSH public-key fingerprints if they are available.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100