...@yahoo.de
wrote:
You can look at batchee.
Romain configured offline doc (with markdown, but could also be
asciidoc)
and mvn scm-publish
LieGrue,
strub
On Sat, 9/8/14, John D. Ament john.d.am...@gmail.com wrote:
Subject: Re: DeltaSpike docs
On Sat, 9/8/14, John D. Ament john.d.am...@gmail.com wrote:
Subject: Re: DeltaSpike docs plan
To: deltaspike dev@deltaspike.apache.org
Date: Saturday, 9 August, 2014, 15:54
Actually, from digging
around their code, might have
:
Subject: Re: DeltaSpike docs plan
To: deltaspike dev@deltaspike.apache.org
Date: Saturday, 9 August, 2014, 15:54
Actually, from digging
around their code, might have an easier solution, so
long as everyone agrees.
I have a small POC setup here:
https://github.com/johnament
doc (with markdown, but could also be
asciidoc)
and mvn scm-publish
LieGrue,
strub
On Sat, 9/8/14, John D. Ament john.d.am...@gmail.com wrote:
Subject: Re: DeltaSpike docs plan
To: deltaspike dev@deltaspike.apache.org
Date
Actually, from digging around their code, might have an easier solution, so
long as everyone agrees.
I have a small POC setup here:
https://github.com/johnament/deltaspike/commit/402becc0e450e551570107a1661d39e9eb6a43cb
I setup a local VM w/ a SVN repo to test it out. Basically, we can
generate
On 7 Aug 2014, at 18:47, Rafael Benevides benevi...@redhat.com wrote:
Before we have a deal with Michelle's team about these content changes, I
think we should close the two other definitions:
- docs location: move to deltaspike sources, create a new repository, other?
+1 to move to
Em 8/8/14, 6:49, Pete Muir escreveu:
On 7 Aug 2014, at 18:47, Rafael Benevides benevi...@redhat.com wrote:
Before we have a deal with Michelle's team about these content changes, I think
we should close the two other definitions:
- docs location: move to deltaspike sources, create a new
I think we need to convince infra@ that these are all must needed features.
From looking at the code behind CMS, it would appear that it's the one
calling markdown based on the imports in our files. Unless we want to do
something crazy like render asciidoc in markdown format, then hand that
over
I remember that someone said that CMS already supports remote
repositories. Can't we start by having this documents moved soon while
we discuss about the asciidoc rendering ?
Em 8/8/14, 10:53, Gerhard Petracek escreveu:
@john:
the infra team is usually not the blocking part (if there is no
On 1 Aug 2014, at 17:46, Rafael Benevides benevi...@redhat.com wrote:
Hi all,
As you may known, Red Hat docs team was called to help on DeltaSpike docs.
After a long period, they have analyzed the documentation and bring us an
awesome plan that is available here:
Wow, looks like a lot of work was spent on the analysis of the
documentation! Thanks Michelle!
+1 from me for all the suggestions.
On Fri, Aug 1, 2014 at 10:46 AM, Rafael Benevides benevi...@redhat.com
wrote:
Hi all,
As you may known, Red Hat docs team was called to help on DeltaSpike
+1 for me as well. Having the doc source with source code is a must have
IMO.
Antoine Sabot-Durand
Le 4 août 2014 à 17:52, Jason Porter lightguard...@gmail.com a écrit :
Wow, looks like a lot of work was spent on the analysis of the
documentation! Thanks Michelle!
+1 from me for all the
There may be some issues here. For one, does anyone know if the apache CMS
can work in the proposed format? I believe it's a requirement currently to
separate them.
On Fri, Aug 1, 2014 at 12:46 PM, Rafael Benevides benevi...@redhat.com
wrote:
Hi all,
As you may known, Red Hat docs team
Hi
@John: apache cms is extensible enough to work with what we want (even docx
or xls :p). Just need somebody with 1-2 days to hack the rendering and wire
it in perl in the DS cms integratino.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn:
Maybe it's a silly question: Does all Apache project needs to use Apache
CMS ?
Em 8/4/14, 13:51, John D. Ament escreveu:
There may be some issues here. For one, does anyone know if the
apache CMS can work in the proposed format? I believe it's a
requirement currently to separate them.
Almost: http://www.apache.org/dev/cms.html
What's the issue with CMS?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-08-04 20:15 GMT+02:00 Rafael Benevides
It seemed at the first looks that it makes you tight with SVN for repo,
Markdown for format, and doesn't allow you to embed other documents.
Something that came in my mind was to have the documentation as a git
submodule of the DeltaSpike site, that way we can have it linked and
splited at
2014-08-04 18:20 GMT+00:00 Rafael Benevides benevi...@redhat.com:
It seemed at the first looks that it makes you tight with SVN for repo,
true but you don't have to see it if you don't want
Markdown for format,
that's the default only
and doesn't allow you to embed other documents.
It
afaik doing the CMS via svnpubsub is only for convenience. We could
theoretically also generate the html pages somewhere else. But at the end of
the day we need to push it to svn to publish it. This is our way to make sure
we have all in a proper historic context.
LieGrue,
strub
On Monday,
@suggested content changes:
+1
regards,
gerhard
2014-08-01 18:46 GMT+02:00 Rafael Benevides benevi...@redhat.com:
Hi all,
As you may known, Red Hat docs team was called to help on DeltaSpike docs.
After a long period, they have analyzed the documentation and bring us an
awesome plan
Hi all,
As you may known, Red Hat docs team was called to help on DeltaSpike
docs. After a long period, they have analyzed the documentation and
bring us an awesome plan that is available here:
Hi all,
As you may known, Red Hat docs team was called to help on DeltaSpike
docs. After a long period, they have analyzed the documentation and
bring us an awesome plan that is available here:
22 matches
Mail list logo
