I floated a proposal on stdlib-sig to create a file named
Misc/maintainers.rst. The purpose of this file is to collect knowledge
about who knows which modules well enough to make decision about issues
in the tracker when the participants in the issue aren't sure, and to
write down the community knowledge about who has special interest and
expertise in specific topic areas.
This proposal was met with approval and, after a couple of small
modifications of the proposal, no dissent; so I've created the skeleton
of the file. I've filled in some of the blanks where I had personal
knowledge, was told info on IRC, from the two referenced PEPs, and
from PEP 11.
Feel free to respond with comments about the header text, but more
importantly let me know what you know about who (especially if it is you)
should be listed for each module, platform, and topic, and feel free to
suggest additional topics. My goal is to record the community knowledge.
Another topic of discussion that is orthogonal to filling in the table is
whether or not to publish it outside the repository. Jesse would like to
see it included in the Python Documentation, and Georg has suggested the
possibility of creating a separate, sphinx-based, automatically-uploaded
document collection in the repository to contain this and related
information (Misc/devdocs?).
The module list was built from the py3k documentation module index, with
the addition of 'pybench' from PEP 291. If there are other modules/tools
that are missing, or submodules that should be broken out into
separate lines, please let me know.
After the initial flurry of updates and comments dies down I will check
this in.
--David
----------------------------------------------------------------------
Maintainers Index
=================
This document cross references Python Modules (first table) and platforms
(second table) with the Tracker user names of people who are experts
and/or resources for that module or platform. This list is intended
to be used by issue submitters, issue triage people, and other issue
participants to find people to add to the nosy list or to contact
directly by email for help and decisions on feature requests and bug
fixes. People on this list may be asked to render final judgement on a
feature or bug. If no active maintainer is listed for a given module,
then questionable changes should go to python-dev, while any other issues
can and should be decided by any committer.
The last part of this document is a third table, listing broader topic
areas in which various people have expertise. These people can also
be contacted for help, opinions, and decisions when issues involve
their areas.
If a listed maintainer does not respond to requests for comment for an
extended period (three weeks or more), they should be marked as inactive
in this list by placing the word 'inactive' in parenthesis behind their
tracker id. They are of course free to remove that inactive mark at
any time.
Committers should update this table as their areas of expertise widen.
New topics may be added to the third table at will.
The existence of this list is not meant to indicate that these people
*must* be contacted for decisions; it is, rather, a resource to be used
by non-committers to find responsible parties, and by committers who do
not feel qualified to make a decision in a particular context.
See also `PEP 291`_ and `PEP 360`_ for information about certain modules
with special rules.
.. _`PEP 291`: http://www.python.org/dev/peps/pep-0291/
.. _`PEP 360`: http://www.python.org/dev/peps/pep-0360/
================== ===========
Module Maintainers
================== ===========
__future__
__main__ gvanrossum
_dummy_thread brett.cannon
_thread
abc
aifc r.david.murray
array
ast
asynchat josiahcarlson
asyncore josiahcarlson
atexit
audioop
base64
bdb
binascii
binhex
bisect
builtins
bz2
calendar
cgi
cgitb
chunk
cmath
cmd
code
codecs
codeop
collections
colorsys
compileall
configparser
contextlib
copy
copyreg
cProfile
crypt
csv
ctypes theller
curses
datetime
dbm
decimal
difflib
dis
distutils tarek
doctest
dummy_threading brett.cannon
email barry
encodings
errno
exceptions
fcntl
filecmp
fileinput
fnmatch
formatter
fpectl
fractions
ftplib
functools
gc
getopt
getpass
gettext
glob
grp
gzip
hashlib
heapq
hmac
html
http
imaplib
imghdr
imp
importlib brett.cannon
inspect
io pitrou, benjamin.peterson
itertools
json
keyword
lib2to3 benjamin.peterson
linecache
locale
logging vsajip
macpath
mailbox
mailcap
marshal
math
mimetypes
mmap
modulefinder theller, jvr
msilib
msvcrt
multiprocessing jnoller
netrc
nis
nntplib
numbers
operator
optparse aronacher
os
ossaudiodev
parser
pdb
pickle
pickletools
pipes
pkgutil
platform lemburg
plistlib
poplib
posix
pprint
pstats
pty
pwd
py_compile
pybench lemburg
pyclbr
pydoc
queue
quopri
random
re
readline
reprlib
resource
rlcompleter
runpy
sched
select
shelve
shlex
shutil
signal
site
smtpd
smtplib
sndhdr
socket
socketserver
spwd
sqlite3
ssl
stat
string
stringprep
struct
subprocess astrand (inactive)
sunau
symbol
symtable
sys
syslog
tabnanny
tarfile
telnetlib
tempfile
termios
test
textwrap
threading
time
timeit
tkinter gpolo
token
tokenize
trace
traceback
tty
turtle gregorlingl
types
unicodedata
unittest michael.foord
urllib
uu
uuid
warnings
wave
weakref
webbrowser georg.brandl
winreg
winsound
wsgiref pje
xdrlib
xml loewis
xml.etree effbot (inactive)
xmlrpc loewis
zipfile
zipimport
zlib
================== ===========
================== ===========
Platform Maintainer
------------------ -----------
AIX
Cygwin jlt63
FreeBSD
Linux
Mac ronaldoussoren
NetBSD1
OS2/EMX aimacintyre
Solaris
HP-UX
================== ===========
================== ===========
Interest Area Maintainers
------------------ -----------
algorithms
ast/compiler
autoconf
bsd
buildbots
data formats
database
documentation georg.brandl
GUI
i18n
import machinery brett.cannon
io pitrou, benjamin.peterson
locale
makefiles
mathematics marketdickinson, eric.smith
memory management
networking
packaging
release management
time and dates
testing michael.foord
threads
unicode
windows
================== ===========
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com