I understand the downsides to integrating with a third-party provider for to-do lists (I left Vitalist simply because I didn't like their revamped interface). As for existing open source projects, I run Task Freak now (http://www.taskfreak.com), and it has some good features. It's PHP but nicely AJAXed so perhaps some ideas could be borrowed from them.
On 1/23/09, Denise Paolucci <[email protected]> wrote: > > On Jan 23, 2009, at 4:09 PM, zvi wrote: > >> But the sort of integration Jane was talking about is, honestly, >> not at all the sort of feature I think of when speaking of a thing >> called a todo list, and probably quite particular to DW, and I can >> see that it would be all sorts of useful to people who are not me. >> (And I have much love for things that are useful to people who are >> not me.) But the description on the difference list didn't bring to >> mind "a tool to do things zvi doesn't want to do" but rather "a >> tool to do things already being done better in a wide variety of >> other places." > > > In that case, it was probably my clumsy phrasing on the difference > list. :) > > And most of that is because I don't yet know what kind of form I want > something like that to take! This is the kind of thing where our > design process would be something like posting an entry to one of our > user-discussion comms/channels, saying "hey, this is the sort of > thing we want to add, and here's why we think it'd be useful. Do you > guys think you'd use it? If so, how? What immediately comes to mind > as potential applications for something like this? What are we > forgetting to think about? Who out there is doing it right?" > > Then sit back and read and listen to all the comments that come in, > and after a discussion period, pull them together into a potential > spec for the project. Then post *that* and see what people have to > say about it: too much? too little? Too far? Not far enough? What are > we forgetting to think about? What use cases did we forget to take > into account, and how can we design to fit those use cases too? > > Design it flexibly, let people purpose it however they want: that's > the DW way. > > --D > > -- > Denise Paolucci > [email protected] > Dreamwidth Studios: Open Source, open expression, open operations. > Coming soon! > > _______________________________________________ > dw-discuss mailing list > [email protected] > http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss > _______________________________________________ dw-discuss mailing list [email protected] http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss
