Hello All,

After a frenzy of activity, I hit a wall.  Ran into some issues that
have precluded me from using Chandler.  I have received some
well-intentioned emails, however, some of the proposed solutions
assume that I am involved at a level much deeper than as simply an
end-user (e.g., requiring the use of Cygwin to do command-line stuff
etc. -- I didn't even know what Cygwin was when I started).

I know Chandler is in the very early stages, but having worked at a
few software companies myself (including as a sales engineer at
Interwoven in the very early days), I would like to make an important
point about "dogfood".

Eating one's own dogfood, i.e., relying on the software that you
write, is one thing when you're talking about say, a graphics package.
 But when it comes to a PIM -- which is intended for the least
technical of computer users, and on which people will plan and run
their lives -- IMHO, there should be a different standard and priority
list.

More than anything, someone must be able to recover (all but the most
recent) data that has been entered.  Server, repository, and
installation issues should be given the highest priority.  It should
never take a high level of sophistication to have the option of
resetting and reinstalling. But if it comes to that, then it should be
easy and bulletproof. (That's where I'm at -- I have an .ics file
waiting to be imported ;-)

I'm sure I will get Chandler back on track soon enough, but this is
really more of a gut check for a broader testing release.

I realize I am the unusual user who will try all the functionality
advertised (and some that isn't) -- multiple shared collections,
syncing to multiple machines, etc.  But, as much as I'd like to think
that I am unique, I am not :-)

Anyway, I don't mean to sound critical or frustrated.  I like
Chandler, was starting to rely on it, miss using it, and can't wait
for the next release + Scooby!

(Dog)Food for thought.

Jim
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to