From: Maxence G. <max...@in...> - 2003-02-24 21:39:50
|
> Make some incredibly minimum directory layout suggestions and minimal > project documentation (something like text file called "description.txt" in > the root of each module). Then get a ton of code up there. Deal with the > consequences later. The number of community projects with intricate and > beautiful submission specifications and no useful code or users far > outweighs the number of useful projects bogged down by bad indentation and > planning. I don't think uploading a ton of code and deal with consequences *later* is the easy way : someone will have to sort the functions, and try to give some consistency for the functions of a module. This can be very difficult when it means finding the good functions among hundreds. What about this other way : let's find some topics for modules (strings, lists, ...), then for each topic ask everyone what functions are missing and useful, then upload them or code them. Otherwise, I'm afraid the mess in the libraries will result in mess in programs using them. Building stable libraries will make them more usable : I don't think anyone would use a library whose interface is always changing. -- Maxence Guesdon1 |