The Wayback Machine - https://web.archive.org/web/20201215131334/https://github.com/python/devguide/pull/348
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refresh tracker page on where to file issues #348

Merged
merged 2 commits into from Mar 24, 2018
Merged

Conversation

@willingc
Copy link
Collaborator

@willingc willingc commented Mar 23, 2018

Partially addresses #120.

This PR is prompted by recent discussion on "core mentorship" list. It's a refresh of the section.

  • expand introduction to clarify bugs.python.org and bpo refer to the issue tracker and include devguide issue tracker location
  • migrate text to bullets in "check if issue exists section" for easier reader scanning
  • remove the reference to Javascript and nosy list as it's confusing for those newer to the contributing. It is covered well in the nosy list reference on the triaging page.
  • Add a heading for "understanding issue progress and status"
  • Move section on "Disagreement" above the triaging sections and edit tone
  • reflow text and fix minor grammar issues
@willingc
Copy link
Collaborator Author

@willingc willingc commented Mar 23, 2018

@csabella If you have any comments or would like to review, I would appreciate it.

tracker.rst Outdated
`issue tracker`_. The `issue tracker`_ is also commonly referred to as
`bugs.python.org` and `bpo`. Documentation bugs can also be reported there.

You can report bugs with how the issue tracker functions to the `meta tracker`_.

This comment has been minimized.

@csabella

csabella Mar 23, 2018
Contributor

For some reason, I don't find the line about the meta tracker easy to read. First time through, I had read it twice to understand what was being said. Maybe 'You can report bugs with the issue tracker itself to the meta tracker.'?

This comment has been minimized.

@willingc

willingc Mar 24, 2018
Author Collaborator

Thanks for the suggestion. Will update.

in modules which you have a working knowledge. Search for the name of a module
in the issue tracker or use the `advanced search`_ to search for specific
components (e.g. "Windows" if you are a Windows developer, "Extension Modules"
if you are familiar with C, etc.). Finally you can use the "Random issue" link

This comment has been minimized.

@csabella

csabella Mar 23, 2018
Contributor

The random button has been broken for awhile and I have an open ticket on the Meta Tracker. It opens a new issue daily, but stays the same for the whole day. So, I made a Python program to open random issues for myself. :-)

This comment has been minimized.

@willingc

willingc Mar 24, 2018
Author Collaborator

Cool, feel free to link to the source for your open issue generator here in this issue. Other folks may find it helpful themselves.

This comment has been minimized.

@csabella

csabella Mar 25, 2018
Contributor

I don't have it published anywhere since it was just a quick script. Should I upload it my github account and link to it there? Here it is, so maybe I should polish it first? I download the csv file manually so that I don't hit the server every time I run the job.

import csv
import random
import time
import webbrowser

file = '/home/cheryl/cpython/buglist_20180211.csv'
browser = webbrowser.get(using='firefox')

with open(file, newline='') as csvfile:
    reader = csv.DictReader(csvfile)
    open_items = [row['id'] for row in reader]

if open_items:
    browser.open_new('https://bugs.python.org')
    time.sleep(0.5)
    for i in range(10):
        choice = random.choice(open_items)
        browser.open(f'https://bugs.python.org/issue{choice}')
        print(choice)
@csabella
Copy link
Contributor

@csabella csabella commented Mar 23, 2018

Thanks @willingc! Looks great!

One thing I couldn't comment on because it wasn't a changed line, but do you think OpenID should be a link?

@willingc
Copy link
Collaborator Author

@willingc willingc commented Mar 24, 2018

Thanks @csabella @brettcannon for the reviews. I appreciate them 👍

@willingc willingc merged commit ca25f50 into python:master Mar 24, 2018
1 check passed
1 check passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@willingc willingc deleted the willingc:trackers branch Mar 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
You can’t perform that action at this time.