Dear Doug Baskins: Are you planning to open-source your new version of Judy?
If so, a good practice is to go ahead and publish what you've got, even if it doesn't compile, is ugly, doesn't really show what you mean, and so on. This practice of "release early, release often" has a lot of good effects, one of which is to assure people that the ultimate result, when it arrives, will be open-source. This sort of thing could be important for some long-term plans. For example, I have a scheme in mind for a new data structure, inspired by the success of JudyTrees but probably quite different in its design. If I'm sure that your next project will be open source, then I think of you as a partner -- two different teams exploring adjacent areas of the design space. If I think that you (or someone) might assert exclusive rights over your next project, then I think of that project as a potentially dangerous competitor to mine, and I want to withhold information from you. My own project is in such a nascent stage that it is hardly worth mentioning and I wouldn't want to waste your time with it until I've done some actual experiments so I can report real numbers. But I thought I would mention it so as to encourage you to "work in public" by publishing your incomplete work, in order to elicit such cooperation from people other than me who may already have more to offer. Regards, Zooko Wilcox-O'Hearn ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
