"Eric S. Raymond" <esr@thyrsus.com> writes: > I told him that we don't have a formal process, but attracting the > attention of someone on python-dev is usually where it starts. Actually, we do: Write a library PEP, see PEP 2. This procedure is rarely executed completely, but I would atleast insist on the maintenance part being clarified in advance - with a clear, up-front indication that the module *will* be removed if it ever becomes unmaintained (of course, if that ever happens, and the module has its usership, threat of removing it might produce a different maintainer). As you can see, I don't care that much about usefulness of the module (although I'm sure others here will); to me, if users say it is useful, and maintenance is clear, and it does not come with a huge C library that you need to build, I'm fine with incorporating it - provided there is somebody I can assign bug reports to. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4