Ezio Melotti <[email protected]> added the comment:
Something similar to the "module" field already exists: the nosy list
autocomplete can search for module maintainers and developers can add
themselves if they are interested to specific modules.
One possible option is to move this information from the devguide to the
tracker, so that everyone (including non-developers) can list the modules they
want to maintain.
If this happens, we could also move the "interest areas" to the tracker, and
possibly merge them with and/or use them to replace the "components". The
result would be a few fixed set of tags (module names, interest areas) that can
be used to find people interested to a specific issue and possibly to mark/tag
the issue.
If we want to add another layer of complexity we might also let the user decide
what kind of notification they want to have (auto-assign, auto-nosy, just some
visual hint for potentially interesting issues).
Once people agree on one of these ideas, someone will have to turn it in a
concrete proposal (that should include both the UI changes necessary and how
the whole thing is supposed to work), and then someone will have to implement
it.
>>>> * there are hundreds of modules;
>>> How many exactly? I doubt there is more than hundred.
>> More than two hundreds.
> How many exactly?
209 on the "experts" page, 265 in help('modules'). Note that help('modules')
lists some C _modules (like several _codecs_*) that are not listed on the
"experts" page but otoh it just lists the root of packages, without listing all
the subpackages (e.g. only 'xml' instead of 'xml.dom', 'xml.sax', 'xml.etree').
_______________________________________________________
PSF Meta Tracker <[email protected]>
<http://psf.upfronthosting.co.za/roundup/meta/issue373>
_______________________________________________________
_______________________________________________
Tracker-discuss mailing list
[email protected]
http://mail.python.org/mailman/listinfo/tracker-discuss
