Proposal: Python Info Collective

[webmaster at python.org]

>>>>> "AMK" == Andrew M Kuchling <akuchlin at mems-exchange.org> writes:

    AMK> http://www.vex.net/~x/parnassus/ is *very* nice, and it might
    AMK> be the only solution required.  Apparently a good deal of
    AMK> work has been put into seeding the initial database, and
    AMK> that's important, because it makes the index immediately
    AMK> useful.  Yet I hadn't heard about it until now; is the site
    AMK> still beta?  Did I miss a c.l.py.announce article about it?

    AMK> There are various issues with it -- I don't know how scalable
    AMK> the underlying code is, the graphic design could be simpler,
    AMK> vex.net's reliability and bandwidth are unknown, and we can
    AMK> argue about the classification hierarchy *forever* -- but
    AMK> it's still valuable.

    AMK> We need to just pick a solution and stick with it; Parnassus
    AMK> is as good as any, and has the incalculable advatange of
    AMK> being implemented.  I'd like to encourage everyone who
    AMK> maintains Python code, or writes Python tutorials and docs,
    AMK> to go to http://www.vex.net/~x/parnassus/ .  Is everything
    AMK> you've done in the index?  If not, add the missing items.
    AMK> Can we prominently link to it from python.org, so people
    AMK> begin to use it?

Very interesting!  I hadn't heard about it until Andrew's post either.
I just made an update to the Mailman entry, but it looks like there's
some editorial review for record changes, because the change isn't
effective immediately.  That could be another bottleneck in the
system.

In any event, since the site's been outed, I'll probably add a link
somewhere on the python.org site, but I'd still like Parnassus' author
to get in touch with me...

-Barry