I get that, i hope that the thing with Sugar yields more interest for Chandler (and Sugar!). And, yep, sometimes you need to look outside your current focus to get recharged on what you are doing.
On another point entirely, i've downloaded the iPhone SDK and have been reading the Cosmo AtomPub API stuff, and wanted to know... If i start working on a _simple_ chandler app for the iPhone (allowing you to read notes), am i stepping on anyone else's dev-toes? I know you wrote the Chandler QE app (which is a great start for the iPhone)... Thanks! jos Jeffrey Harris wrote: > Hey Jos, > > Yup, good point that we don't want to get too side-tracked. > > In the short term, I don't think there's a ton that Sugar's likely to > bring to Chandler's rearchitecture, but in the long run, it's possible > we can share effort (or we can just leverage there work) on persistence. > Also, if they take an interest in just a piece of Chandler (the > Calendar UI, say), more developer eyes there would be a big help to us. > > All in all, I don't imagine Chandler core developers are likely to spend > more than a few hours a week on this sort of collaboration. It turns > out (at least for me, I'm not sure if this is universally true) there's > actually a big boost to my productivity when I do a bit of collaboration > outside, but not too far, from my normal sphere of development thinking. > > So somewhat paradoxically, a little time spent on collaboration (even > with no likely immediate benefits to Chandler) can often be more than > made up for with increased output. > > Sincerely, > Jeffrey > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > Open Source Applications Foundation "chandler-dev" mailing list > http://lists.osafoundation.org/mailman/listinfo/chandler-dev -- Jos Yule Digital Hyakugei _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
