In the wake of at DemoCamp 3 last night, we had another on-line meeting this morning about the state of DrProject. Our original aim was to release it at the end of January; we're now looking at the first week of March, and it may slip again. Here's the current to-do list:
None of this detracts from the fact that we've come a long way in a very short time: DrProject is very usable, and impressed a lot of people last night who aren't particularly easy to impress.
- Our Kid templates are too slow: 2-3 seconds per page. This is only partly Kid's fault---as Chris Lenz pointed out, our current wiki formatter is creating HTML, which Kid then tries to validate. We hope to fix this with a two-pronged attack: writing a new wiki formatting engine (which we really want to do anyway), and getting Kid's maintainers to add a "don't bother to validate" flag.
- The mail subsystem still isn't hooked up. Exim vs. Sendmail is part of the problem, but so is the code that was written last summer.
- We still don't have any screencasts (which have quickly become one of the things that separates the pros from the amateurs). Pat Smith has tried various tools, but none of the free ones generate Flash and record audio at the same time. The latest beta of Wink is next on his list; if that doesn't work by week's end, we'll spring for Camtasia.
- We haven't figured out what to do about RSS authentication (but then, neither has anyone else). We must use the user accounts on the underlying Unix system, rather than doing our own provisioning, so we either figure out a secure way to get a dozen different blog readers to pass user IDs and passwords to us (unlikely), or place a bet on one of the open source identity management "standards" being bruited about. You can probably hear the lack of enthusiasm in my voice...
- Documentation. The user guide isn't done, the installation notes are incomplete, the scripting examples don't exist---in short, we're looking like a typical open source project.
- Finally, there are a bunch of smaller issues: modifying the CSS style sheets so that pages printed from Firefox aren't squeezed into a two-centimeter column, making the logo display properly in IE, and so on.