[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Łukasz Langa added the comment: Thanks, everyone! ✨ 🍰 ✨ -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Łukasz Langa added the comment: New changeset fb6074f5d71a6f9802bad97a129378c9556ed8d3 by Miss Islington (bot) in branch '3.9': bpo-44830: [doc] Restore missing Mozilla devguide link (GH-27818) (GH-27821) https://github.com/python/cpython/commit/fb6074f5d71a6f9802bad97a129378c9556ed8d3 -

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

miss-islington added the comment: New changeset ad16f93942a398ca1ec9bba54bb9c53a4e121e75 by Miss Islington (bot) in branch '3.10': bpo-44830: [doc] Restore missing Mozilla devguide link (GH-27818) https://github.com/python/cpython/commit/ad16f93942a398ca1ec9bba54bb9c53a4e121e75 --

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Change by miss-islington : -- pull_requests: +26286 pull_request: https://github.com/python/cpython/pull/27821 ___ Python tracker ___ __

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Change by miss-islington : -- pull_requests: +26285 pull_request: https://github.com/python/cpython/pull/27820 ___ Python tracker ___ __

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Łukasz Langa added the comment: New changeset 942d1a4284e9341df47c48d7c63e921136dc9719 by Jack DeVries in branch 'main': bpo-44830: [doc] Restore missing Mozilla devguide link (GH-27818) https://github.com/python/cpython/commit/942d1a4284e9341df47c48d7c63e921136dc9719 -- ___

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: @terry.reedy ok, a PR to restore the docs with the new link is open. -- ___ Python tracker ___ ___

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Change by Jack DeVries : -- pull_requests: +26283 pull_request: https://github.com/python/cpython/pull/27818 ___ Python tracker ___

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Terry J. Reedy added the comment: Fixing the link now, given that it is possible, and someone someday writing a new doc to replace it are different issues. This issue is about the link. -- ___ Python tracker _

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Thomas Grainger added the comment: Depends on the redirect type they create. If it's temporary we should keep the same URL, if it's permanent or otherwise has bookmark updating semantics we should update the URL to follow the redirect On Wed, 18 Aug 2021, 21:40 Jack DeVries, wrote: > > Jack

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: All right, consider the needle in the haystack officially found. This page has the same content as the missing page: https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html Thank you @buhtz for opening an issue with Mozilla; they are eventually going to dep

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: I am pretty sure that Mozilla moved to a new content management system and they've been refreshing a lot of content on their site. I would assume that any lingering presence of this article is just growing pains and it'll all be removed in due time. I might be w

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Terry J. Reedy added the comment: https://support.mozilla.org/en-US/kb/contributors-guide-writing-good-bug still has a link to https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines but the fact that they moved the latter to https://github.com/mdn/archived-content/blob/mai

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Thomas Grainger added the comment: It looks like it got archived here https://github.com/mdn/archived-content/blob/main/files/en-us/mozilla/qa/bug_writing_guidelines/index.html -- nosy: +graingert ___ Python tracker

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Terry J. Reedy added the comment: Problems with linking to archive.org Wayback machine. 1. They have limited bandwidth. 2. Production linking, as opposed to research like Jack did to find the 'missing' page, stretches the meaning of 'fair use'. Potential problems with external docs. 1. Don't

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: > If Jack wants to pick this up, I'd merge it. I might be interested but I'm not sure if I will have the time. I'm not "calling dibs" if anyone else wants to go ahead with this solution. -- ___ Python tracker

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: I agree that linking to the wayback machine is clunky. I just sent a message out to the python-ideas mailing list to solicit more suggestions. The discourse thread didn't get much response. I guess that at some point, if there is no consensus, it wouldn't be a b

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Łukasz Langa added the comment: New changeset b6a6d99a0ba3796a9d7d4fe8612b640f90e6d7f9 by Senthil Kumaran in branch '3.10': [3.10] bpo-44830 - Remove the broken Broken Mozilla devguide link. (GH-27664) (GH-27666) https://github.com/python/cpython/commit/b6a6d99a0ba3796a9d7d4fe8612b640f90e6d7f

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Łukasz Langa added the comment: I merged the 3.10 backport but leaving the bug open since only removing the 404 link isn't really fixing the problem. Linking to the Wayback Machine feels off to me. I would rather support making a similar document in our own docs, using the removed document as

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: I'm pretty much a novice, Senthil, so I don't know how much a review from me is worth but removing the broken link seems best! -- ___ Python tracker _

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Senthil Kumaran added the comment: @Jack, if you review this backport - https://github.com/python/cpython/pull/27666 , I can merge this PR. -- ___ Python tracker ___

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: @mark.dickinson, Steven D'Aprano suggested just linking to the wayback machine on discuss.python.org. What do you think of that? https://discuss.python.org/t/alternate-article-for-how-to-wite-good-bug-report/10040/2?u=jdevries3133 -- _

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Senthil Kumaran added the comment: New changeset 6a6bcf16370beff2e0d1a034661654d5c335b5ee by Miss Islington (bot) in branch '3.9': bpo-44830 - Remove the broken Broken Mozilla devguide link. (GH-27664) (GH-27665) https://github.com/python/cpython/commit/6a6bcf16370beff2e0d1a034661654d5c335b5

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Change by Senthil Kumaran : -- pull_requests: +26155 pull_request: https://github.com/python/cpython/pull/27666 ___ Python tracker ___ _

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +26154 pull_request: https://github.com/python/cpython/pull/27665 ___ Python tracker _

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Senthil Kumaran added the comment: New changeset ebecffdb6d5fffa4249f9a813f1fc1915926feb5 by Senthil Kumaran in branch 'main': bpo-44830 - Remove the broken Broken Mozilla devguide link. (GH-27664) https://github.com/python/cpython/commit/ebecffdb6d5fffa4249f9a813f1fc1915926feb5 --

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: I created a discourse thread for people to propose alternatives:: https://discuss.python.org/t/alternate-article-for-how-to-wite-good-bug-report/10040 It's be a good idea to merge @orsenthil's PR which just removes the broken link right away. Then, we can keep

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Change by Senthil Kumaran : -- keywords: +patch nosy: +orsenthil nosy_count: 3.0 -> 4.0 pull_requests: +26153 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27664 ___ Python tracker

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Mark Dickinson added the comment: > do you feel like that new article is a good drop-in replacement for the old > one? No really, no. :-( I also now see that the new article has a (broken) link to the old article, which makes me think that maybe the removal of the old article was unintenti

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Jack DeVries added the comment: For reference, it looks like Wayback Machine has a snapshot of the old article for reference: https://web.archive.org/web/20210613191914/https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines @mark.dickinson, do you feel like that new artic

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

Mark Dickinson added the comment: A bit more Googling found this: https://support.mozilla.org/en-US/kb/contributors-guide-writing-good-bug -- ___ Python tracker ___ _

[issue44830] Broken Mozilla devguide link in "Dealing with Bugs" doc section

New submission from Mark Dickinson : The "Bug Report Writing Guidelines" link in the "Dealing with Bugs" doc section (https://docs.python.org/3/bugs.html) looks broken. The linked URL is https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines, but that gives me a "Page not