Hi,
OK, so this one's a bit more technical. ;-)
* More "process": I'm not the only one who says "I'll do X" and then
disappears for awhile before anything materializes. I don't know a good
solution for getting partially-working code out, but I hope that more people
will be willing to discuss approaches, problems and even incorrect code.
Sometimes someone with an idea doesn't have the time to do it, and
sometimes another pair of eyes will spot problems you miss.
* More rewrites: Alas, we still have some work to do on this front. Some of
the hazy areas of the code are clearing up, but I don't think the current
code structure (you know, what file contains particular code) always makes
sense. On that note, we still need more "internal documentation."
* Learning curve: Many people have commented that it's a bit steep to
start developing on ht://Dig. OK, help me out here--what can I do to
help? Would it help to bring up smaller projects (that need to be
done) that can serve as steps up the curve? More discussion of what
the core developers are doing?
I'm really enthused about 2000 and what we can get done--I think the
project is really picking up some steam! Let me know what I can do to
help you! (That's my responsibility after all!)
Cheers,
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
