I fine with Google docs or anything else. 

On 4 September 2014 10:53, Lukáš Fryč <lukas.fryc@gmail.com> wrote:

Yea, I rather meant if we are in brainstorming phase e.g. with Sync spec,

I see a fit for rather collaborative solution,

but I was mistaken with suggesting oksoclap, because it does not offer that level of interactivity as well. :-)

What I meant is sharing a document such as Data Sync Spec on collaborative editor where:

* you can suggest additions / modifications

* you can comment

* comments can be resolved once resolved

* that document is owned and maintained by group of people

such as Google Docs: https://docs.google.com/document/d/1hOsAN5og6dz07-k66ooaGbJ5KrnWJWRyHRelwyjf6bk/edit?usp=sharing

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!

Cheers,

~ Lukas

On Thu, Sep 4, 2014 at 8:31 AM, danielbevenius <daniel.bevenius@gmail.com> wrote:

Lukas and I talked yesterday and he brought up an issue that it is not as
smooth as it could be to contribute to the roadmap. He instead suggested to
have a shared docs which I'll later clean up and include in a pull request.

The current version can be found here and is in raw asciidoc format:
http://oksoclap.com/p/datasync_roadmap

Let me know if this works out better.



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Suggestion-for-DataSync-roadmap-tp9006p9114.html
Sent from the aerogear-dev mailing list archive at Nabble.com.

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev