Giving him developer privs will allow him to appear in the "assigned to" list. It has no effect on the tab completion of the nosy field. (Since any tracker id can appear in the nosy field, I presume it is the tab completion you are talking about.) Tab completion is controlled by the experts file in the devguide. We already have non-committers in that list, so you can add him there if there is an appropriate topic, or create a topic if one doesn't already exist.
(I don't use the tab completion feature myself, and in fact I can't seem to get it to work right now, so I'm speaking from theory here...)
On Thu, 19 Feb 2015 14:39:34 +0000, Brett Cannon email@example.com wrote:
Developer privileges should be enough and I can't think of any special docs.
On Thu Feb 19 2015 at 5:35:26 AM Nick Coghlan firstname.lastname@example.org wrote:
I'd like to have Slavek (Fedora/RHEL Python maintainer) appear in the bugs.python.org nosy list entirely for selfish reasons (i.e. I'd like to make it easier for me or anyone else to ask his opinion on issues that may have a downstream impact on Fedora and the Fedora-derived ecosystem)
Do I just need to grant him Developer access on the tracker to make that happen? Or would he have to be accepted as a core developer first?
And as a related meta-question... are there additional tracker admin docs I should be aware of given my level of access?
Noob-tracker-admin-ish'ly yours, Nick.
-- Nick Coghlan | email@example.com | Brisbane, Australia _______________________________________________ core-workflow mailing list firstname.lastname@example.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
core-workflow mailing list email@example.com https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct