[cdi-dev] Tools : Google Drive vs Asciidoc and Github

John D. Ament john.d.ament at gmail.com
Fri Sep 5 10:36:31 EDT 2014


On Fri, Sep 5, 2014 at 6:22 AM, Antoine Sabot-Durand <
antoine at sabot-durand.net> wrote:

> Hi all,
> 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 :
> 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).
> 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.
> 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.
> WDYT ?
> Antoine
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
> Note that for all code provided on this list, the provider licenses the
> code under the Apache License, Version 2 (
> http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas
> provided on this list, the provider waives all patent and other
> intellectual property rights inherent in such information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140905/13806ccc/attachment.html 

More information about the cdi-dev mailing list