Daniel Vainsencher <danielv at netvision.net.il> appears to have written:

> If we learned something from the 3.3aModules, it is that for something
> to be accepted, it better come in small, edible bites. People should be
> able to play with it from the beginning. Keep it in mind when you plan
> your releases.
I certainly agree with the 'edible' part; I suspect that 'small' is
tightly related to the digestability.

It gets back to documentation again - if there is clearly understandable
explanations of the intent, architecture and implementation then people
will be able to understand. Then they can review and suggest
improvements. Others can make use of it. Finally, harvesters and guides
can see the value and feel motivated to spend their time (frequently in
very short supply even for those of us unencumbered by the burdens of
employment) to finish the packaging and actually release it.

As Adele Goldberg puts it "If it isn't documented it doesn't exist".

tim
-- 
+================================================================+
|Though a nation watched her falling, yet a world could only cry |
|As they passed from us to Glory , riding fire in the sky.       |
|(Jordin Kare, Fire In The Sky)                                  |
|Farewell Columbia.                                              |
+================================================================+
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim