7:33 a.m.
Hi,
I feel a bit of the documentation might be misleading and not always that
great to go over.
Instead of adding more and more the README, I think we should (w/in the
REPO) start to write a guide/book on HOWTO.
Regarding the actual format, I think asciidoc comes to mind;
Any thoughts ?
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
8:55 a.m.
+1
We got already almost all the material in the current readme and we can
split that nicely into a howto and then rewriting maybe some parts.
On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf <matzew(a)apache.org>wrote:
Hi,
I feel a bit of the documentation might be misleading and not always that
great to go over.
Instead of adding more and more the README, I think we should (w/in the
REPO) start to write a guide/book on HOWTO.
Regarding the actual format, I think asciidoc comes to mind;
Any thoughts ?
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
10:11 a.m.
On 25 Mar 2014, at 08:55, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
+1
We got already almost all the material in the current readme and we can split that nicely
into a howto and then rewriting maybe some parts.
On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf <matzew(a)apache.org> wrote:
Hi,
I feel a bit of the documentation might be misleading and not always that great to go
over.
Instead of adding more and more the README, I think we should (w/in the REPO) start to
write a guide/book on HOWTO.
+1 to add the doc in the relevant repo
We could alway inlude part of the ascidoc text in aerogear web site with the same
mechanism as shown in this PR:
https://github.com/aerogear/aerogear.org/pull/275
Regarding the actual format, I think asciidoc comes to mind;
Any thoughts ?
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
1:53 p.m.
did we discuss using the wiki, or was that for something else
On Mar 25, 2014, at 5:11 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
On 25 Mar 2014, at 08:55, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
> +1
> We got already almost all the material in the current readme and we can split that
nicely into a howto and then rewriting maybe some parts.
>
>
>
> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
> Hi,
>
> I feel a bit of the documentation might be misleading and not always that great to go
over.
>
> Instead of adding more and more the README, I think we should (w/in the REPO) start
to write a guide/book on HOWTO.
+1 to add the doc in the relevant repo
We could alway inlude part of the ascidoc text in aerogear web site with the same
mechanism as shown in this PR:
https://github.com/aerogear/aerogear.org/pull/275
>
> Regarding the actual format, I think asciidoc comes to mind;
>
>
> Any thoughts ?
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
1:55 p.m.
On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist <lholmqui(a)redhat.com>wrote:
did we discuss using the wiki, or was that for something else
not sure - wiki is nice, but a real guide/book is really something I prefer
for the "official" documentation.
wiki could be:
setup up your XFVZ Database etc
On Mar 25, 2014, at 5:11 AM, Corinne Krych
<corinnekrych(a)gmail.com> wrote:
>
> On 25 Mar 2014, at 08:55, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
>
>> +1
>> We got already almost all the material in the current readme and we can
split that nicely into a howto and then rewriting maybe some parts.
>>
>>
>>
>> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
>> Hi,
>>
>> I feel a bit of the documentation might be misleading and not always
that great to go over.
>>
>> Instead of adding more and more the README, I think we should (w/in the
REPO) start to write a guide/book on HOWTO.
>
> +1 to add the doc in the relevant repo
> We could alway inlude part of the ascidoc text in aerogear web site with
the same mechanism as shown in this PR:
> https://github.com/aerogear/aerogear.org/pull/275
>
>
>>
>> Regarding the actual format, I think asciidoc comes to mind;
>>
>>
>> Any thoughts ?
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
5:03 p.m.
maybe we can use http://jekyllrb.com/
here you are an example http://docs.scala-lang.org/
and source code https://github.com/scala/scala.github.com
Date: Tue, 25 Mar 2014 13:55:43 +0100
From: matzew(a)apache.org
To: aerogear-dev(a)lists.jboss.org
Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation improvements ?
On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
did we discuss using the wiki, or was that for something else
not sure - wiki is nice, but a real guide/book is really something I prefer for the
"official" documentation.
wiki could be: setup up your XFVZ Database etc
On Mar 25, 2014, at 5:11 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
>
>
>
>
>
>
On 25 Mar 2014, at 08:55, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
> +1
> We got already almost all the material in the current readme and
we can split that nicely into a howto and then rewriting maybe some parts.
>> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf
<matzew(a)apache.org> wrote:
> Hi,
>> I feel a bit of the documentation might be misleading and not
always that great to go over.
>> Instead of adding more and more the README, I think we should
(w/in the REPO) start to write a guide/book on HOWTO.
+1 to add the doc in the relevant repo
We could alway inlude part of the ascidoc text in aerogear web site
with the same mechanism as shown in this PR:
> Regarding the actual format, I think asciidoc comes to mind;
>> Any thoughts ?
>> --
> Matthias Wessendorf
>> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
5:08 p.m.
On Tue, Mar 25, 2014 at 5:03 PM, Willy Martin Aguirre Rodriguez <
marti1003(a)hotmail.com> wrote:
maybe we can use http://jekyllrb.com/
yeah - our actual website is already using that:
https://github.com/aerogear/aerogear.org#building
:-)
here you are an example http://docs.scala-lang.org/
and source code https://github.com/scala/scala.github.com
------------------------------
Date: Tue, 25 Mar 2014 13:55:43 +0100
From: matzew(a)apache.org
To: aerogear-dev(a)lists.jboss.org
Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation
improvements ?
On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist <lholmqui(a)redhat.com>wrote:
did we discuss using the wiki, or was that for something else
not sure - wiki is nice, but a real guide/book is really something I
prefer for the "official" documentation.
wiki could be:
setup up your XFVZ Database etc
On Mar 25, 2014, at 5:11 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
>
> On 25 Mar 2014, at 08:55, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
>
>> +1
>> We got already almost all the material in the current readme and we can
split that nicely into a howto and then rewriting maybe some parts.
>>
>>
>>
>> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
>> Hi,
>>
>> I feel a bit of the documentation might be misleading and not always
that great to go over.
>>
>> Instead of adding more and more the README, I think we should (w/in the
REPO) start to write a guide/book on HOWTO.
>
> +1 to add the doc in the relevant repo
> We could alway inlude part of the ascidoc text in aerogear web site with
the same mechanism as shown in this PR:
> https://github.com/aerogear/aerogear.org/pull/275
>
>
>>
>> Regarding the actual format, I think asciidoc comes to mind;
>>
>>
>> Any thoughts ?
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________ aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
11:11 p.m.
Idea for documentation:
Is it possible to use unifiedpush server work in tomcat or jetty?
I don't have much experience about Redhat but about Tomcat or Jetty I know, how to
deploy a war.
maybe there is a equivalent maybe there is a equivalence between applications servers.
Try to add image for doc. screenshots of Jboss
Date: Tue, 25 Mar 2014 17:08:10 +0100
From: matzew(a)apache.org
To: aerogear-dev(a)lists.jboss.org
Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation improvements ?
On Tue, Mar 25, 2014 at 5:03 PM, Willy Martin Aguirre Rodriguez
<marti1003(a)hotmail.com> wrote:
maybe we can use http://jekyllrb.com/
yeah - our actual website is already using that:
https://github.com/aerogear/aerogear.org#building
:-)
here you are an example http://docs.scala-lang.org/
and source code https://github.com/scala/scala.github.com
Date: Tue, 25 Mar 2014 13:55:43 +0100
From: matzew(a)apache.org
To: aerogear-dev(a)lists.jboss.org
Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation improvements ?
On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist <lholmqui(a)redhat.com> wrote:
did we discuss using the wiki, or was that for something else
not sure - wiki is nice, but a real guide/book is really something I prefer for the
"official" documentation.
wiki could be: setup up your XFVZ Database etc
On Mar 25, 2014, at 5:11 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
>
>
>
>
>
>
On 25 Mar 2014, at 08:55, Sebastien Blanc <scm.blanc(a)gmail.com>
wrote:
> +1
> We got already almost all the material in the current readme and
we can split that nicely into a howto and then rewriting maybe some parts.
>> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf
<matzew(a)apache.org> wrote:
> Hi,
>> I feel a bit of the documentation might be misleading and not
always that great to go over.
>> Instead of adding more and more the README, I think we should
(w/in the REPO) start to write a guide/book on HOWTO.
+1 to add the doc in the relevant repo
We could alway inlude part of the ascidoc text in aerogear web site
with the same mechanism as shown in this PR:
> Regarding the actual format, I think asciidoc comes to mind;
>> Any thoughts ?
>> --
> Matthias Wessendorf
>> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
11:14 a.m.
On Tue, Mar 25, 2014 at 11:11 PM, Willy Martin Aguirre Rodriguez <
marti1003(a)hotmail.com> wrote:
Idea for documentation:
Is it possible to use unifiedpush server work in tomcat or jetty?
nope, due to javaee dependencies
I don't have much experience about Redhat but about Tomcat or
Jetty I
know, how to deploy a war.
maybe there is a equivalent maybe there is a equivalence between
applications servers.
it's all on the README of the UnifiedPush Server:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/0.10.1#getti...
1) Database config
2) start server
3) deploy the WAR
* it's that simple (when building the project from scratch: "mvn package
jboss-as:deploy")
* another way is to just copy the WAR file to the
$JBOSS/standalone/deployments folder
No need for screenshots on that
Try to add image for doc. screenshots of Jboss
------------------------------
Date: Tue, 25 Mar 2014 17:08:10 +0100
From: matzew(a)apache.org
To: aerogear-dev(a)lists.jboss.org
Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation
improvements ?
On Tue, Mar 25, 2014 at 5:03 PM, Willy Martin Aguirre Rodriguez <
marti1003(a)hotmail.com> wrote:
maybe we can use http://jekyllrb.com/
yeah - our actual website is already using that:
https://github.com/aerogear/aerogear.org#building
:-)
here you are an example http://docs.scala-lang.org/
and source code https://github.com/scala/scala.github.com
------------------------------
Date: Tue, 25 Mar 2014 13:55:43 +0100
From: matzew(a)apache.org
To: aerogear-dev(a)lists.jboss.org
Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation
improvements ?
On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist <lholmqui(a)redhat.com>wrote:
did we discuss using the wiki, or was that for something else
not sure - wiki is nice, but a real guide/book is really something I
prefer for the "official" documentation.
wiki could be:
setup up your XFVZ Database etc
On Mar 25, 2014, at 5:11 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
>
> On 25 Mar 2014, at 08:55, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
>
>> +1
>> We got already almost all the material in the current readme and we can
split that nicely into a howto and then rewriting maybe some parts.
>>
>>
>>
>> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
>> Hi,
>>
>> I feel a bit of the documentation might be misleading and not always
that great to go over.
>>
>> Instead of adding more and more the README, I think we should (w/in the
REPO) start to write a guide/book on HOWTO.
>
> +1 to add the doc in the relevant repo
> We could alway inlude part of the ascidoc text in aerogear web site with
the same mechanism as shown in this PR:
> https://github.com/aerogear/aerogear.org/pull/275
>
>
>>
>> Regarding the actual format, I think asciidoc comes to mind;
>>
>>
>> Any thoughts ?
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________ aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
_______________________________________________ aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
12:26 p.m.
Created a JIRA to track the work:
https://issues.jboss.org/browse/AGPUSH-571
On Wed, Mar 26, 2014 at 11:14 AM, Matthias Wessendorf <matzew(a)apache.org>wrote:
On Tue, Mar 25, 2014 at 11:11 PM, Willy Martin Aguirre Rodriguez <
marti1003(a)hotmail.com> wrote:
>
> Idea for documentation:
> Is it possible to use unifiedpush server work in tomcat or jetty?
>
nope, due to javaee dependencies
> I don't have much experience about Redhat but about Tomcat or Jetty I
> know, how to deploy a war.
> maybe there is a equivalent maybe there is a equivalence between
> applications servers.
>
it's all on the README of the UnifiedPush Server:
https://github.com/aerogear/aerogear-unifiedpush-server/tree/0.10.1#getti...
1) Database config
2) start server
3) deploy the WAR
* it's that simple (when building the project from scratch: "mvn package
jboss-as:deploy")
* another way is to just copy the WAR file to the
$JBOSS/standalone/deployments folder
No need for screenshots on that
> Try to add image for doc. screenshots of Jboss
>
> ------------------------------
> Date: Tue, 25 Mar 2014 17:08:10 +0100
>
> From: matzew(a)apache.org
> To: aerogear-dev(a)lists.jboss.org
> Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation
> improvements ?
>
>
>
>
> On Tue, Mar 25, 2014 at 5:03 PM, Willy Martin Aguirre Rodriguez <
> marti1003(a)hotmail.com> wrote:
>
> maybe we can use http://jekyllrb.com/
>
>
> yeah - our actual website is already using that:
>
> https://github.com/aerogear/aerogear.org#building
>
> :-)
>
>
> here you are an example http://docs.scala-lang.org/
> and source code https://github.com/scala/scala.github.com
>
>
> ------------------------------
> Date: Tue, 25 Mar 2014 13:55:43 +0100
> From: matzew(a)apache.org
> To: aerogear-dev(a)lists.jboss.org
> Subject: Re: [aerogear-dev] [UnifiedPush Server] Documentation
> improvements ?
>
>
>
>
>
> On Tue, Mar 25, 2014 at 1:53 PM, Lucas Holmquist <lholmqui(a)redhat.com>wrote:
>
> did we discuss using the wiki, or was that for something else
>
>
> not sure - wiki is nice, but a real guide/book is really something I
> prefer for the "official" documentation.
>
> wiki could be:
> setup up your XFVZ Database etc
>
>
>
> On Mar 25, 2014, at 5:11 AM, Corinne Krych <corinnekrych(a)gmail.com>
> wrote:
>
> >
> > On 25 Mar 2014, at 08:55, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
> >
> >> +1
> >> We got already almost all the material in the current readme and we
> can split that nicely into a howto and then rewriting maybe some parts.
> >>
> >>
> >>
> >> On Tue, Mar 25, 2014 at 7:33 AM, Matthias Wessendorf <
> matzew(a)apache.org> wrote:
> >> Hi,
> >>
> >> I feel a bit of the documentation might be misleading and not always
> that great to go over.
> >>
> >> Instead of adding more and more the README, I think we should (w/in
> the REPO) start to write a guide/book on HOWTO.
> >
> > +1 to add the doc in the relevant repo
> > We could alway inlude part of the ascidoc text in aerogear web site
> with the same mechanism as shown in this PR:
> > https://github.com/aerogear/aerogear.org/pull/275
> >
> >
> >>
> >> Regarding the actual format, I think asciidoc comes to mind;
> >>
> >>
> >> Any thoughts ?
> >>
> >>
> >>
> >> --
> >> Matthias Wessendorf
> >>
> >> blog: http://matthiaswessendorf.wordpress.com/
> >> sessions: http://www.slideshare.net/mwessendorf
> >> twitter: http://twitter.com/mwessendorf
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >>
> >> _______________________________________________
> >> aerogear-dev mailing list
> >> aerogear-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________ aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________ aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
3677
days inactive
3678
days old
9 comments
5 participants
participants (5)
-
Corinne Krych -
Lucas Holmquist -
Matthias Wessendorf -
Sebastien Blanc -
Willy Martin Aguirre Rodriguez