<div dir="ltr">Hey team,<div><br></div><div>I've proposed following change to the Conflict Resolution part of the Data Sync roadmap after recent discussions about Data Sync.</div><div><br></div><div>I'm very interested in feedback from all the specific SDK teams, in terms of whether the whole idea matches the visions you have for Data Sync and whether we are able to leverage (and/or extend) platform specific tools.</div><div><br></div><div><br></div><div>Changes contains following additions:</div><div><br></div><div><ul class="" style="padding:0px 0px 0px 2em;margin-top:0px;color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,'Segoe UI',Arial,freesans,sans-serif;font-size:14px;line-height:22.399999618530273px;margin-bottom:0px!important"><li>Dec 2014<ul class="" style="padding:0px 0px 0px 2em;margin-top:0px;margin-bottom:0px"><li>Partial Updates</li><li>SPDY</li></ul></li><li>Jan 2015<ul class="" style="padding:0px 0px 0px 2em;margin-top:0px;margin-bottom:0px"><li>Batch API</li></ul></li></ul></div><div><br></div><div>You can read the doc directly here (starting with 0.2.0):</div><div><br></div><div><a href="https://github.com/lfryc/aerogear.org/blob/partial-updates-spdy-batches/docs/planning/roadmaps/AeroGearConflictResolution.asciidoc#020-dec-2015-partial-updates-spdy">https://github.com/lfryc/aerogear.org/blob/partial-updates-spdy-batches/docs/planning/roadmaps/AeroGearConflictResolution.asciidoc#020-dec-2015-partial-updates-spdy</a><br></div><div><br></div><div><br></div><div>Please leave any comment right in PR:</div><div><br></div><div><a href="https://github.com/aerogear/aerogear.org/pull/386">https://github.com/aerogear/aerogear.org/pull/386</a></div><div><br></div><div><br></div><div>Thanks!</div><div><br></div><div>~ Lukas</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 4, 2014 at 11:00 AM, Daniel Bevenius <span dir="ltr"><<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I fine with Google docs or anything else. </div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On 4 September 2014 10:53, Lukáš Fryč <span dir="ltr"><<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yea, I rather meant if we are in brainstorming phase e.g. with Sync spec,<div>I see a fit for rather collaborative solution,</div>
<div><br></div><div>but I was mistaken with suggesting oksoclap, because it does not offer that level of interactivity as well. :-)</div>
<div><br></div><div><br></div><div>What I meant is sharing a document such as Data Sync Spec on collaborative editor where:</div><div><br></div><div>* you can suggest additions / modifications</div><div>* you can comment<br>
</div><div>* comments can be resolved once resolved</div><div>* that document is owned and maintained by group of people</div><div><br></div><div>such as Google Docs: <a href="https://docs.google.com/document/d/1hOsAN5og6dz07-k66ooaGbJ5KrnWJWRyHRelwyjf6bk/edit?usp=sharing" target="_blank">https://docs.google.com/document/d/1hOsAN5og6dz07-k66ooaGbJ5KrnWJWRyHRelwyjf6bk/edit?usp=sharing</a></div>
<div><br></div><div><br></div><div>But I don't see a point into bringing other technology if it should not help us be more productive, so tell me if I'm mistaken!</div><div><br></div><div><br></div><div>Cheers,</div>
<div><br></div><div>~ Lukas</div><div><br></div><div><br></div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 4, 2014 at 8:31 AM, danielbevenius <span dir="ltr"><<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Lukas and I talked yesterday and he brought up an issue that it is not as<br>
smooth as it could be to contribute to the roadmap. He instead suggested to<br>
have a shared docs which I'll later clean up and include in a pull request.<br>
<br>
The current version can be found here and is in raw asciidoc format:<br>
<a href="http://oksoclap.com/p/datasync_roadmap" target="_blank">http://oksoclap.com/p/datasync_roadmap</a><br>
<br>
Let me know if this works out better.<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Suggestion-for-DataSync-roadmap-tp9006p9114.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Suggestion-for-DataSync-roadmap-tp9006p9114.html</a><br>
Sent from the aerogear-dev mailing list archive at Nabble.com.<br>
<div><div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>