Berker Peksag added the comment: > They are on a path to be a developer, so if they want to use it I don't see > why they shouldn't.
It creates an unnecessary confusion. I don't want to check https://docs.python.org/devguide/developers.html everytime I want to commit a stale/old patch to be honest. Note that sometimes their usernames are different than their real names which make the whole process more time consuming. I see the assigned to field as "I'm going to commit this" and it looks like other developers see it as the same: http://bugs.python.org/issue21578 > If we are going to do anything with the assigned to field, I think we should > just remove it. I can live without it but I guess we need to discuss it on core-workflow first? I'd prefer applying a three line patch rather than starting a long thread on core-workflow :) _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue593> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org https://mail.python.org/mailman/listinfo/tracker-discuss Code of Conduct: https://www.python.org/psf/codeofconduct/
