<div dir="ltr"><div class="gmail_default" style="font-size:large">Hi All</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">I would definitively recommend this. With JSR 354 (Money) we basically did the same. Collaboration is easy, effective and it is also very easy to spread things for feedback and to remove things, if they were closed/moved (e.g. with a EDR). For final uniform formatting (especially title numbering, which is not supported by Google Docs), links etc. Asciidcoc is definitively the better solution.</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">Cheers,</div><div class="gmail_default" style="font-size:large">Anatole</div><div class="gmail_default" style="font-size:large"><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-09-05 12:22 GMT+02:00 Antoine Sabot-Durand <span dir="ltr"><<a href="mailto:antoine@sabot-durand.net" target="_blank">antoine@sabot-durand.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
<br>
To pursue the discussion we had during last meeting, I really think we should use both tools for the workshop. that’s how I see things :<br>
<br>
In early stage in the workshop the working doc is changing fast and could probably content ideas that will disappear in future version (impossible or breaking backward compatibility).<br>
This phase needs fast collaboration between people knowing that the doc content is volatile and more in “brain storm” than in “part of the final spec” mode. For these reason I think we should set this working phase in Google Drive. It will be easier to collaborate synchronously on the doc and separate the very early draft to more advance phase.<br>
<br>
When an agreement (we have to define that yet) will be reached on this doc, it will be converted in Asciidoc (the plugin works nicely) and integrated to the spec website. The change will course continue but if we didn’t missed big mistake there will be less of them and they could be done thru PR.<br>
<br>
WDYT ?<br>
<br>
Antoine<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><span style="font-family:arial;font-size:small"><b>Anatole Tresch</b></span><div style="font-family:arial;font-size:small">Java Lead Engineer, JSR Spec Lead<br>Glärnischweg 10<br>CH - 8620 Wetzikon</div><div style="font-family:arial;font-size:small"><br></div><div style="font-family:arial;font-size:small"><i>Switzerland, Europe Zurich, GMT+1</i></div><div style="font-family:arial;font-size:small"><i>Twitter: @atsticks</i></div><div><i style="font-family:arial;font-size:small">Blogs: </i><font face="arial"><i><a href="http://javaremarkables.blogspot.ch/" target="_blank">http://javaremarkables.blogspot.ch/</a></i></font></div><div style="font-family:arial;font-size:small"><i>Google: atsticks<br>Mobile +41-76 344 62 79</i></div></div>
</div>