Proposal: Python Info Collective

Martijn Faassen m.faassen at vet.uu.nl
Mon Nov 15 12:27:37 CET 1999


Jules Allen <usenet-mm-yyyy at julesallen.com> wrote:
> In article <3d1z9sq2uc.fsf at amarok.cnri.reston.va.us>, Andrew M. Kuchling wrote:
> | The issue of indexing modules is an old one, and I'm still astounded
> | that we've never converged on a solution, though everyone always
> | complains about this.  

> Thanks for the History lesson! This helps put it all in perspective
> but why *something* hasn't been built before now is kind of weird.
> The best part of your story for me is confirmation that open source
> projects don't do well without strong leadership. No ESR or an
> ESR-like figure to crack the whip, no Trove.

Actually, 'strong leadership' is not enough. If someone cracks his whip
impressively in open source but doesn't write any code himself, you won't
get any software in the end. So you need someone who actually takes on
the responsibility for writing the code. :)

[Vaults of Parnassus]

Browses through them eagerly and curiously.  :)

Regards,

Martijn
-- 
History of the 20th Century: WW1, WW2, WW3?
No, WWW -- Could we be going in the right direction?




More information about the Python-list mailing list