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

Decide what to do with the legacy setuptools tracker on bugs.python.org #174

Open
ghost opened this issue Mar 24, 2014 · 1 comment
Open

Decide what to do with the legacy setuptools tracker on bugs.python.org #174

ghost opened this issue Mar 24, 2014 · 1 comment

Comments

@ghost
Copy link

@ghost ghost commented Mar 24, 2014

Originally reported by: ncoghlan (Bitbucket: ncoghlan, GitHub: ncoghlan)


MvL pointed out that http://bugs.python.org/setuptools/ is currently still live and needs to be dealt with so people don't get confused about where to report setuptools issues.

@pje pointed out that there is some info on issues there that hasn't yet been replicated in the docs or migrated to this issue tracker, so it likely needs to be reviewed before the instance can be terminated.

MvL suggested making it read-only for the time being. That sounds like a good idea to me, but a better long term resolution is needed.


@ghost
Copy link
Author

@ghost ghost commented Mar 24, 2014

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):


I see several substeps.

  1. Disallow creation of new issues on the setuptools tracker. This might be as simple as setting roundup roles.
  2. There is already a header on each individual issue page, but not on the index page as linked above. If possible, adding a link to the index page would be helpful.
  3. The remaining 58 issues should be addressed - either transferred to bitbucket or closed as wontfix.
  4. Disallow commenting (essentially make the site read-only).

I would like to keep the tracker around for posterity, rather than terminating it. What is the cost of continuing to host the site for reference?

@ghost ghost added major task labels Mar 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant