Re: [chandler-dev] World readable documentation for Chandler rearchitecture

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