<div dir="ltr">I fine with Google docs or anything else. </div><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 class="HOEnZb"><div class="h5"><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">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>