Mark Sapiro writes:
mailman findmember -h Usage: mailman findmember [OPTIONS] PATTERN
IWBNI we had shell completions for bash and zsh at least.
I've been out of it, should have got to this sooner, but GSoC org applications are open until Feb 3, so I'll try to rustle one up.
If anybody is willing to serve as backup org admin and second mentor, please let me know. Qualifications: org admin fills out GSoC paperwork 2-3 times a season, keeps track of mentor-student relations, and usually serves as a mentor. Note: Mailman has never called on a backup org admin in 10+ seasons of GSoC. Mostly second mentors just read email a couple times a week and comment when they have something to contribute. No real Python-specific skills required, mostly hand-holding and occasionally pumping the brakes on hair-brained deviations from proposed work, and I guess you'd be uncomfortable if you're not comfortable with at least one high level language. Python is often characterized as "executable pseudo-code": it's easy to learn enough to mentor. Deep knowledge of Mailman is not needed for most projects (the bash completions project above is an example where zero knowledge is needed). Typically they add a feature, sometimes independent of Mailman internals, instead hooking into a well-defined API.
Obviously Python skills are useful, and most projects will interface with Mailman code. However, it's not uncommon that I've learned Python skills during GSoC, mostly from studying the Mailman code (Barry is not known as the Friendly Language Uncle for Life aka FLUFL for nothing, you know), but often from the student. So it's a learning opportunity for most mentors.
Steve
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan