On Wed, Apr 23, 2014 at 8:36 AM, Patrick Ohly <[email protected]>wrote:
> On Fri, 2014-04-18 at 23:51 +0200, Emiliano Heyns wrote: > > On Fri, Apr 18, 2014 at 10:37 PM, Ohly, Patrick > > <[email protected]> wrote: > > I don't think we have consensus on the revised terminology. My > > updated readme will need further changes. > > > > I understand that it will; I'll keep tracking those changes. I feel I > > sort of have a grasp on things now, and I want to start writing while > > it's fresh in my mind. If the conceptual model that I have in my head > > is wrong, it'll need revising anyhow. If the model is OK but the > > terminology is off, that should be easy enough to fix. I find it > > easier in general to have something flawed out for correction than to > > try and aim for perfection before starting; it's easier to point out > > flaws than to built something without flaws. I don't mind rework. > > Okay. I was just worried that you might get disappointed when the > terminology changes again. > > I'm a scrum master at work; I tend to prefer flawed products over perfect concepts. I've pushed out a new version at http://reichenhack.github.io/syncevolution.html that now adds google sync; I'd love it if someone could go over it to see if there are mistakes left. I know there are many commands that con be combined; I intend to add that as a separate section as soon as I know the verbose explanation is correct. If that turns out to be the case, then these are the next steps: 1. OAuth2 for Google 2. Compact command lines, setting up multiple configs in one go 3. Start rewriting the other HOWTO's I find strewn about building off this one. Regards, Emile
_______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
