On 24 March 2014 20:53, "Martin v. Löwis"
Am 24.03.14 01:33, schrieb PJ Eby:
I think it would be a good idea to check with Jason and other PyPA volunteers to see if there is anyone else who can handle the moves. I'd prefer we didn't lose the history, since my comments on those issues (and the closed ones, too) often contain key information about use cases and design decisions that may not be available elsewhere, even from my memory. ;-) But, since I'm no longer in the lead on development, I think it would be better for someone closer to the future of things to do the prioritizing of what, if anything, to transfer as an issue or keep as documentation.
Yet alternatively, I could set the tracker to read-only, and keep it up for any foreseeable future.
The reason I'm bringing this up is two-fold: 1. some people started using the tracker to distribute spam 2. some people apparently still think that the system is active, and continue reporting issues there.
Both problems would be resolved by setting the tracker to read-only; shutting it down is actually not necessary (although it would slightly reduce our maintenance efforts).
That sounds good to me. I've also filed https://bitbucket.org/pypa/setuptools/issue/174/ to decide on a longer term solution. If Jason decides to review/migrate issues, it may be necessary to turn developer write access back on to allow issues to be marked as closed once they have been dealt with appropriately. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia