You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2016/10/01 13:08:53 UTC
AW: [DISCUSS] Switch the site repo to GIT?
Ok so it turns out that as long as we use the Apache CMS we can't change to GIT. Guess this was the reason for still being on GIT.
I have no idea what we really need the CMS for, but as long as we need this, we seem to be stuck there :-(
Chris
________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Donnerstag, 29. September 2016 18:56:39
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Switch the site repo to GIT?
On 9/29/16, 1:43 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
>Hi guys,
>
>
>as you might know I have been working hard on the site-generation and
>this finally seems to be working nicely. The only problem I have is that
>I can't submit to the site repo from the Build agent as SVN isn't setup
>to allow that. Git however is able to commit without hard-coding
>credentials. Infra suggested to move our site to GIT to resolve this
>issue.
>
>
>I was wondering anyway why this is our only SVN repo. Wouldn't it be cool
>to have everything in one type of repo?
The fact our web site is on SVN isn't a big deal to me, but what is a big
deal is 99% of the time I find the two-step staging/publish workflow
really painful. Related, there is currently no way for the MD5 checker on
the CI server to update the website automatically. If moving to Git gets
us out of that, I'd be for it. Can you provide more info on how folks do
staging when working on big overhauls and why Git doesn't have this
credential issue?
Thanks,
-Alex
AW: [DISCUSS] Switch the site repo to GIT?
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok so I did a little searching:
It seems that in general if you setup a git repo and define an "asf-site" branch in that (of course have Infra register the repo in their system), stuff pushed to that branch is automatically published as website.
I just tested it, the maven site plugin is able to produce html from:
- APT (don't know that)
- XDoc (don't know that)
- Markdown
- FML (don't know that)
- Asciidoctor (After adding the plugin)
So we could write our content in any of these formats.
I found this very helpful page of a fellow Apache project [1].
They said, that Markdown had the advantage of allowing inline HTML. So I understand that this could be ideal for the parts of the site where we need detailed control over the HTML.
Asciidoctor has the advantage of allowing more features (inline graphs and diagrams just to state one thing I really like). So this could be ideal for the parts where we need features over control of the HTML.
So why not simply allow to use both?
I have done some searching and I'd like to propose something:
1. We create a new git repo for the site
2. I setup a maven site project inside that
3. I configure the build to allow multiple types of content
- Markdown (same as github pages)
- Asciidoctor
4. I configure the build to deploy the site to the "asf-site" branch of the same repo
5. We have infra setup the gitpubsub system to stage that somewhere so we can test it
6. We do the Content migration, CSS, HTML fine tuning till we're happy with it
7. We make the new site the official site.
Would that be an option?
Chris
[1] https://cwiki.apache.org/confluence/display/TRAFODION/Modify+Web+Site
________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Sonntag, 2. Oktober 2016 07:14:42
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Switch the site repo to GIT?
It is time to consider getting off of Apache CMS. I think some projects
have done so already. I'd like to know more about what we lose/gain if we
go way from Apache CMS.
Some projects are experimenting with GitHub Pages. I think it should be
considered as well.
-Alex
On 10/1/16, 9:11 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Orher projects using git for the cms what are using?
>Could we switch, for example, to a wordpress cms if we want?
>
>
>
>El sábado, 1 de octubre de 2016, Christofer Dutz
><ch...@c-ware.de>
>escribió:
>
>> Ok so it turns out that as long as we use the Apache CMS we can't change
>> to GIT. Guess this was the reason for still being on GIT.
>>
>>
>> I have no idea what we really need the CMS for, but as long as we need
>> this, we seem to be stuck there :-(
>>
>>
>> Chris
>>
>> ________________________________
>> Von: Alex Harui <aharui@adobe.com <javascript:;>>
>> Gesendet: Donnerstag, 29. September 2016 18:56:39
>> An: dev@flex.apache.org <javascript:;>
>> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
>>
>>
>>
>> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de
>> <javascript:;>> wrote:
>>
>> >Hi guys,
>> >
>> >
>> >as you might know I have been working hard on the site-generation and
>> >this finally seems to be working nicely. The only problem I have is
>>that
>> >I can't submit to the site repo from the Build agent as SVN isn't setup
>> >to allow that. Git however is able to commit without hard-coding
>> >credentials. Infra suggested to move our site to GIT to resolve this
>> >issue.
>> >
>> >
>> >I was wondering anyway why this is our only SVN repo. Wouldn't it be
>>cool
>> >to have everything in one type of repo?
>>
>> The fact our web site is on SVN isn't a big deal to me, but what is a
>>big
>> deal is 99% of the time I find the two-step staging/publish workflow
>> really painful. Related, there is currently no way for the MD5 checker
>>on
>> the CI server to update the website automatically. If moving to Git
>>gets
>> us out of that, I'd be for it. Can you provide more info on how folks
>>do
>> staging when working on big overhauls and why Git doesn't have this
>> credential issue?
>>
>> Thanks,
>> -Alex
>>
>>
>
>--
>
>Carlos Rovira
>Director General
>M: +34 607 22 60 05
>http://www.codeoscopic.com
>http://www.avant2.es
>
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.
AW: AW: [DISCUSS] Switch the site repo to GIT?
Posted by Christofer Dutz <ch...@c-ware.de>.
Well I would suggest to simply let people use the tool they want to use.
I guess both with Jekyll and the maven-site-plugin all "test.md" files will end up as "test.html" files, just the same way a "test.adoc" would become the same "test.html" file.
I wouldn't put up any hard restriction on this. But that's just my opinion.
Currently I would like to take the discussion to the tool for generating the website and here I would strongly prefer the maven-site-plugin, cause it would allow us to integrate the sub-project parts into the rest of the website seamlessly. Every sub-project could provide parts of the total website structure and would work and look the same way.
Chris
________________________________
Von: Josh Tynjala <jo...@gmail.com>
Gesendet: Montag, 3. Oktober 2016 17:56:11
An: dev@flex.apache.org
Betreff: Re: AW: [DISCUSS] Switch the site repo to GIT?
I would indeed prefer Markdown, and I think it would be the better choice
if we want to gain contributors to the documentation because Markdown is
more popular. Regardless, my message was simply to correct some information
that was incorrect. Markdown does not require indentation to format code.
That's one way to do it, but surrounding a block with ``` is perfectly
acceptable too.
- Josh
On Mon, Oct 3, 2016 at 8:47 AM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hey, I'm not really suggesting one over the other. With the
> maven-site-approach we could do all together.
>
>
> Chris
>
> ________________________________
> Von: Josh Tynjala <jo...@gmail.com>
> Gesendet: Sonntag, 2. Oktober 2016 22:43:13
> An: dev@flex.apache.org
> Betreff: Re: AW: [DISCUSS] Switch the site repo to GIT?
>
> It is also possible to use ``` for a code block in markdown. No indentation
> required. You can also specify the language.
>
> ``` actionscript
> code
> ```
>
> - Josh
>
> On Oct 2, 2016 2:54 AM, "Christofer Dutz" <ch...@c-ware.de>
> wrote:
>
> > Well they couldn't give me much info on what others are using, but I dug
> a
> > little myself.
> >
> > So it seems that they use Jekyl to convert Markdown into HTML. There
> > however is a plugin to use Asciidoctor to do the same.
> >
> >
> > Having used both Asciidoctor and Markdown, I think Asciidoctor is far
> more
> > superior when it comes to features. Especially when it comes to the
> syntax,
> > I don't quite like how easy it is to mess up a Markdown file.
> >
> >
> > Just as an example: If you want to output some code, in MD you have to
> > prefix every line of code with four spaces, in adoc you put it in between
> > two "-----" blocks.
> >
> > Lists in MD require you to separate each line with two spaces:
> >
> > * first level
> >
> > * first level
> >
> > * second level
> >
> >
> > In adoc this is:
> >
> > * first level
> >
> > * first level
> >
> > ** second level
> >
> >
> > Markdown does a lot with spaces and Asciidoc does the same with
> > duplicating the important chars. Duplicating important chars doesn't get
> > messed up by the line indenting of IDEs.
> >
> >
> > So how about me investigating how to produce gitpages with asciidoc and
> > having these replace the ApacheCMS pages?
> >
> >
> > Do we have any special stuff in the CMS or is all just static?
> >
> >
> > Chris
> >
> > ________________________________
> > Von: Alex Harui <ah...@adobe.com>
> > Gesendet: Sonntag, 2. Oktober 2016 07:14:42
> > An: dev@flex.apache.org
> > Betreff: Re: [DISCUSS] Switch the site repo to GIT?
> >
> > It is time to consider getting off of Apache CMS. I think some projects
> > have done so already. I'd like to know more about what we lose/gain if
> we
> > go way from Apache CMS.
> >
> > Some projects are experimenting with GitHub Pages. I think it should be
> > considered as well.
> >
> > -Alex
> >
> > On 10/1/16, 9:11 AM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira"
> > <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> > wrote:
> >
> > >Orher projects using git for the cms what are using?
> > >Could we switch, for example, to a wordpress cms if we want?
> > >
> > >
> > >
> > >El sábado, 1 de octubre de 2016, Christofer Dutz
> > ><ch...@c-ware.de>
> > >escribió:
> > >
> > >> Ok so it turns out that as long as we use the Apache CMS we can't
> change
> > >> to GIT. Guess this was the reason for still being on GIT.
> > >>
> > >>
> > >> I have no idea what we really need the CMS for, but as long as we need
> > >> this, we seem to be stuck there :-(
> > >>
> > >>
> > >> Chris
> > >>
> > >> ________________________________
> > >> Von: Alex Harui <aharui@adobe.com <javascript:;>>
> > >> Gesendet: Donnerstag, 29. September 2016 18:56:39
> > >> An: dev@flex.apache.org <javascript:;>
> > >> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
> > >>
> > >>
> > >>
> > >> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de
> > >> <javascript:;>> wrote:
> > >>
> > >> >Hi guys,
> > >> >
> > >> >
> > >> >as you might know I have been working hard on the site-generation and
> > >> >this finally seems to be working nicely. The only problem I have is
> > >>that
> > >> >I can't submit to the site repo from the Build agent as SVN isn't
> setup
> > >> >to allow that. Git however is able to commit without hard-coding
> > >> >credentials. Infra suggested to move our site to GIT to resolve this
> > >> >issue.
> > >> >
> > >> >
> > >> >I was wondering anyway why this is our only SVN repo. Wouldn't it be
> > >>cool
> > >> >to have everything in one type of repo?
> > >>
> > >> The fact our web site is on SVN isn't a big deal to me, but what is a
> > >>big
> > >> deal is 99% of the time I find the two-step staging/publish workflow
> > >> really painful. Related, there is currently no way for the MD5
> checker
> > >>on
> > >> the CI server to update the website automatically. If moving to Git
> > >>gets
> > >> us out of that, I'd be for it. Can you provide more info on how folks
> > >>do
> > >> staging when working on big overhauls and why Git doesn't have this
> > >> credential issue?
> > >>
> > >> Thanks,
> > >> -Alex
> > >>
> > >>
> > >
> > >--
> > >
> > >Carlos Rovira
> > >Director General
> > >M: +34 607 22 60 05
> > >http://www.codeoscopic.com
> > >http://www.avant2.es
> > >
> > >
> > >Este mensaje se dirige exclusivamente a su destinatario y puede contener
> > >información privilegiada o confidencial. Si ha recibido este mensaje por
> > >error, le rogamos que nos lo comunique inmediatamente por esta misma
> vía y
> > >proceda a su destrucción.
> > >
> > >De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> > >comunicamos
> > >que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> > >S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> > >servicio o información solicitados, teniendo usted derecho de acceso,
> > >rectificación, cancelación y oposición de sus datos dirigiéndose a
> > >nuestras
> > >oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> > >necesaria.
> >
> >
>
Re: AW: [DISCUSS] Switch the site repo to GIT?
Posted by Josh Tynjala <jo...@gmail.com>.
I would indeed prefer Markdown, and I think it would be the better choice
if we want to gain contributors to the documentation because Markdown is
more popular. Regardless, my message was simply to correct some information
that was incorrect. Markdown does not require indentation to format code.
That's one way to do it, but surrounding a block with ``` is perfectly
acceptable too.
- Josh
On Mon, Oct 3, 2016 at 8:47 AM, Christofer Dutz <ch...@c-ware.de>
wrote:
> Hey, I'm not really suggesting one over the other. With the
> maven-site-approach we could do all together.
>
>
> Chris
>
> ________________________________
> Von: Josh Tynjala <jo...@gmail.com>
> Gesendet: Sonntag, 2. Oktober 2016 22:43:13
> An: dev@flex.apache.org
> Betreff: Re: AW: [DISCUSS] Switch the site repo to GIT?
>
> It is also possible to use ``` for a code block in markdown. No indentation
> required. You can also specify the language.
>
> ``` actionscript
> code
> ```
>
> - Josh
>
> On Oct 2, 2016 2:54 AM, "Christofer Dutz" <ch...@c-ware.de>
> wrote:
>
> > Well they couldn't give me much info on what others are using, but I dug
> a
> > little myself.
> >
> > So it seems that they use Jekyl to convert Markdown into HTML. There
> > however is a plugin to use Asciidoctor to do the same.
> >
> >
> > Having used both Asciidoctor and Markdown, I think Asciidoctor is far
> more
> > superior when it comes to features. Especially when it comes to the
> syntax,
> > I don't quite like how easy it is to mess up a Markdown file.
> >
> >
> > Just as an example: If you want to output some code, in MD you have to
> > prefix every line of code with four spaces, in adoc you put it in between
> > two "-----" blocks.
> >
> > Lists in MD require you to separate each line with two spaces:
> >
> > * first level
> >
> > * first level
> >
> > * second level
> >
> >
> > In adoc this is:
> >
> > * first level
> >
> > * first level
> >
> > ** second level
> >
> >
> > Markdown does a lot with spaces and Asciidoc does the same with
> > duplicating the important chars. Duplicating important chars doesn't get
> > messed up by the line indenting of IDEs.
> >
> >
> > So how about me investigating how to produce gitpages with asciidoc and
> > having these replace the ApacheCMS pages?
> >
> >
> > Do we have any special stuff in the CMS or is all just static?
> >
> >
> > Chris
> >
> > ________________________________
> > Von: Alex Harui <ah...@adobe.com>
> > Gesendet: Sonntag, 2. Oktober 2016 07:14:42
> > An: dev@flex.apache.org
> > Betreff: Re: [DISCUSS] Switch the site repo to GIT?
> >
> > It is time to consider getting off of Apache CMS. I think some projects
> > have done so already. I'd like to know more about what we lose/gain if
> we
> > go way from Apache CMS.
> >
> > Some projects are experimenting with GitHub Pages. I think it should be
> > considered as well.
> >
> > -Alex
> >
> > On 10/1/16, 9:11 AM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira"
> > <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> > wrote:
> >
> > >Orher projects using git for the cms what are using?
> > >Could we switch, for example, to a wordpress cms if we want?
> > >
> > >
> > >
> > >El sábado, 1 de octubre de 2016, Christofer Dutz
> > ><ch...@c-ware.de>
> > >escribió:
> > >
> > >> Ok so it turns out that as long as we use the Apache CMS we can't
> change
> > >> to GIT. Guess this was the reason for still being on GIT.
> > >>
> > >>
> > >> I have no idea what we really need the CMS for, but as long as we need
> > >> this, we seem to be stuck there :-(
> > >>
> > >>
> > >> Chris
> > >>
> > >> ________________________________
> > >> Von: Alex Harui <aharui@adobe.com <javascript:;>>
> > >> Gesendet: Donnerstag, 29. September 2016 18:56:39
> > >> An: dev@flex.apache.org <javascript:;>
> > >> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
> > >>
> > >>
> > >>
> > >> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de
> > >> <javascript:;>> wrote:
> > >>
> > >> >Hi guys,
> > >> >
> > >> >
> > >> >as you might know I have been working hard on the site-generation and
> > >> >this finally seems to be working nicely. The only problem I have is
> > >>that
> > >> >I can't submit to the site repo from the Build agent as SVN isn't
> setup
> > >> >to allow that. Git however is able to commit without hard-coding
> > >> >credentials. Infra suggested to move our site to GIT to resolve this
> > >> >issue.
> > >> >
> > >> >
> > >> >I was wondering anyway why this is our only SVN repo. Wouldn't it be
> > >>cool
> > >> >to have everything in one type of repo?
> > >>
> > >> The fact our web site is on SVN isn't a big deal to me, but what is a
> > >>big
> > >> deal is 99% of the time I find the two-step staging/publish workflow
> > >> really painful. Related, there is currently no way for the MD5
> checker
> > >>on
> > >> the CI server to update the website automatically. If moving to Git
> > >>gets
> > >> us out of that, I'd be for it. Can you provide more info on how folks
> > >>do
> > >> staging when working on big overhauls and why Git doesn't have this
> > >> credential issue?
> > >>
> > >> Thanks,
> > >> -Alex
> > >>
> > >>
> > >
> > >--
> > >
> > >Carlos Rovira
> > >Director General
> > >M: +34 607 22 60 05
> > >http://www.codeoscopic.com
> > >http://www.avant2.es
> > >
> > >
> > >Este mensaje se dirige exclusivamente a su destinatario y puede contener
> > >información privilegiada o confidencial. Si ha recibido este mensaje por
> > >error, le rogamos que nos lo comunique inmediatamente por esta misma
> vía y
> > >proceda a su destrucción.
> > >
> > >De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> > >comunicamos
> > >que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> > >S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> > >servicio o información solicitados, teniendo usted derecho de acceso,
> > >rectificación, cancelación y oposición de sus datos dirigiéndose a
> > >nuestras
> > >oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> > >necesaria.
> >
> >
>
AW: AW: [DISCUSS] Switch the site repo to GIT?
Posted by Christofer Dutz <ch...@c-ware.de>.
Hey, I'm not really suggesting one over the other. With the maven-site-approach we could do all together.
Chris
________________________________
Von: Josh Tynjala <jo...@gmail.com>
Gesendet: Sonntag, 2. Oktober 2016 22:43:13
An: dev@flex.apache.org
Betreff: Re: AW: [DISCUSS] Switch the site repo to GIT?
It is also possible to use ``` for a code block in markdown. No indentation
required. You can also specify the language.
``` actionscript
code
```
- Josh
On Oct 2, 2016 2:54 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
> Well they couldn't give me much info on what others are using, but I dug a
> little myself.
>
> So it seems that they use Jekyl to convert Markdown into HTML. There
> however is a plugin to use Asciidoctor to do the same.
>
>
> Having used both Asciidoctor and Markdown, I think Asciidoctor is far more
> superior when it comes to features. Especially when it comes to the syntax,
> I don't quite like how easy it is to mess up a Markdown file.
>
>
> Just as an example: If you want to output some code, in MD you have to
> prefix every line of code with four spaces, in adoc you put it in between
> two "-----" blocks.
>
> Lists in MD require you to separate each line with two spaces:
>
> * first level
>
> * first level
>
> * second level
>
>
> In adoc this is:
>
> * first level
>
> * first level
>
> ** second level
>
>
> Markdown does a lot with spaces and Asciidoc does the same with
> duplicating the important chars. Duplicating important chars doesn't get
> messed up by the line indenting of IDEs.
>
>
> So how about me investigating how to produce gitpages with asciidoc and
> having these replace the ApacheCMS pages?
>
>
> Do we have any special stuff in the CMS or is all just static?
>
>
> Chris
>
> ________________________________
> Von: Alex Harui <ah...@adobe.com>
> Gesendet: Sonntag, 2. Oktober 2016 07:14:42
> An: dev@flex.apache.org
> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
>
> It is time to consider getting off of Apache CMS. I think some projects
> have done so already. I'd like to know more about what we lose/gain if we
> go way from Apache CMS.
>
> Some projects are experimenting with GitHub Pages. I think it should be
> considered as well.
>
> -Alex
>
> On 10/1/16, 9:11 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> wrote:
>
> >Orher projects using git for the cms what are using?
> >Could we switch, for example, to a wordpress cms if we want?
> >
> >
> >
> >El sábado, 1 de octubre de 2016, Christofer Dutz
> ><ch...@c-ware.de>
> >escribió:
> >
> >> Ok so it turns out that as long as we use the Apache CMS we can't change
> >> to GIT. Guess this was the reason for still being on GIT.
> >>
> >>
> >> I have no idea what we really need the CMS for, but as long as we need
> >> this, we seem to be stuck there :-(
> >>
> >>
> >> Chris
> >>
> >> ________________________________
> >> Von: Alex Harui <aharui@adobe.com <javascript:;>>
> >> Gesendet: Donnerstag, 29. September 2016 18:56:39
> >> An: dev@flex.apache.org <javascript:;>
> >> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
> >>
> >>
> >>
> >> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de
> >> <javascript:;>> wrote:
> >>
> >> >Hi guys,
> >> >
> >> >
> >> >as you might know I have been working hard on the site-generation and
> >> >this finally seems to be working nicely. The only problem I have is
> >>that
> >> >I can't submit to the site repo from the Build agent as SVN isn't setup
> >> >to allow that. Git however is able to commit without hard-coding
> >> >credentials. Infra suggested to move our site to GIT to resolve this
> >> >issue.
> >> >
> >> >
> >> >I was wondering anyway why this is our only SVN repo. Wouldn't it be
> >>cool
> >> >to have everything in one type of repo?
> >>
> >> The fact our web site is on SVN isn't a big deal to me, but what is a
> >>big
> >> deal is 99% of the time I find the two-step staging/publish workflow
> >> really painful. Related, there is currently no way for the MD5 checker
> >>on
> >> the CI server to update the website automatically. If moving to Git
> >>gets
> >> us out of that, I'd be for it. Can you provide more info on how folks
> >>do
> >> staging when working on big overhauls and why Git doesn't have this
> >> credential issue?
> >>
> >> Thanks,
> >> -Alex
> >>
> >>
> >
> >--
> >
> >Carlos Rovira
> >Director General
> >M: +34 607 22 60 05
> >http://www.codeoscopic.com
> >http://www.avant2.es
> >
> >
> >Este mensaje se dirige exclusivamente a su destinatario y puede contener
> >información privilegiada o confidencial. Si ha recibido este mensaje por
> >error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> >proceda a su destrucción.
> >
> >De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> >comunicamos
> >que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> >S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> >servicio o información solicitados, teniendo usted derecho de acceso,
> >rectificación, cancelación y oposición de sus datos dirigiéndose a
> >nuestras
> >oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> >necesaria.
>
>
Re: AW: [DISCUSS] Switch the site repo to GIT?
Posted by Josh Tynjala <jo...@gmail.com>.
It is also possible to use ``` for a code block in markdown. No indentation
required. You can also specify the language.
``` actionscript
code
```
- Josh
On Oct 2, 2016 2:54 AM, "Christofer Dutz" <ch...@c-ware.de> wrote:
> Well they couldn't give me much info on what others are using, but I dug a
> little myself.
>
> So it seems that they use Jekyl to convert Markdown into HTML. There
> however is a plugin to use Asciidoctor to do the same.
>
>
> Having used both Asciidoctor and Markdown, I think Asciidoctor is far more
> superior when it comes to features. Especially when it comes to the syntax,
> I don't quite like how easy it is to mess up a Markdown file.
>
>
> Just as an example: If you want to output some code, in MD you have to
> prefix every line of code with four spaces, in adoc you put it in between
> two "-----" blocks.
>
> Lists in MD require you to separate each line with two spaces:
>
> * first level
>
> * first level
>
> * second level
>
>
> In adoc this is:
>
> * first level
>
> * first level
>
> ** second level
>
>
> Markdown does a lot with spaces and Asciidoc does the same with
> duplicating the important chars. Duplicating important chars doesn't get
> messed up by the line indenting of IDEs.
>
>
> So how about me investigating how to produce gitpages with asciidoc and
> having these replace the ApacheCMS pages?
>
>
> Do we have any special stuff in the CMS or is all just static?
>
>
> Chris
>
> ________________________________
> Von: Alex Harui <ah...@adobe.com>
> Gesendet: Sonntag, 2. Oktober 2016 07:14:42
> An: dev@flex.apache.org
> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
>
> It is time to consider getting off of Apache CMS. I think some projects
> have done so already. I'd like to know more about what we lose/gain if we
> go way from Apache CMS.
>
> Some projects are experimenting with GitHub Pages. I think it should be
> considered as well.
>
> -Alex
>
> On 10/1/16, 9:11 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> wrote:
>
> >Orher projects using git for the cms what are using?
> >Could we switch, for example, to a wordpress cms if we want?
> >
> >
> >
> >El sábado, 1 de octubre de 2016, Christofer Dutz
> ><ch...@c-ware.de>
> >escribió:
> >
> >> Ok so it turns out that as long as we use the Apache CMS we can't change
> >> to GIT. Guess this was the reason for still being on GIT.
> >>
> >>
> >> I have no idea what we really need the CMS for, but as long as we need
> >> this, we seem to be stuck there :-(
> >>
> >>
> >> Chris
> >>
> >> ________________________________
> >> Von: Alex Harui <aharui@adobe.com <javascript:;>>
> >> Gesendet: Donnerstag, 29. September 2016 18:56:39
> >> An: dev@flex.apache.org <javascript:;>
> >> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
> >>
> >>
> >>
> >> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de
> >> <javascript:;>> wrote:
> >>
> >> >Hi guys,
> >> >
> >> >
> >> >as you might know I have been working hard on the site-generation and
> >> >this finally seems to be working nicely. The only problem I have is
> >>that
> >> >I can't submit to the site repo from the Build agent as SVN isn't setup
> >> >to allow that. Git however is able to commit without hard-coding
> >> >credentials. Infra suggested to move our site to GIT to resolve this
> >> >issue.
> >> >
> >> >
> >> >I was wondering anyway why this is our only SVN repo. Wouldn't it be
> >>cool
> >> >to have everything in one type of repo?
> >>
> >> The fact our web site is on SVN isn't a big deal to me, but what is a
> >>big
> >> deal is 99% of the time I find the two-step staging/publish workflow
> >> really painful. Related, there is currently no way for the MD5 checker
> >>on
> >> the CI server to update the website automatically. If moving to Git
> >>gets
> >> us out of that, I'd be for it. Can you provide more info on how folks
> >>do
> >> staging when working on big overhauls and why Git doesn't have this
> >> credential issue?
> >>
> >> Thanks,
> >> -Alex
> >>
> >>
> >
> >--
> >
> >Carlos Rovira
> >Director General
> >M: +34 607 22 60 05
> >http://www.codeoscopic.com
> >http://www.avant2.es
> >
> >
> >Este mensaje se dirige exclusivamente a su destinatario y puede contener
> >información privilegiada o confidencial. Si ha recibido este mensaje por
> >error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
> >proceda a su destrucción.
> >
> >De la vigente Ley Orgánica de Protección de Datos (15/1999), le
> >comunicamos
> >que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
> >S.A. La finalidad de dicho tratamiento es facilitar la prestación del
> >servicio o información solicitados, teniendo usted derecho de acceso,
> >rectificación, cancelación y oposición de sus datos dirigiéndose a
> >nuestras
> >oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
> >necesaria.
>
>
AW: [DISCUSS] Switch the site repo to GIT?
Posted by Christofer Dutz <ch...@c-ware.de>.
Well they couldn't give me much info on what others are using, but I dug a little myself.
So it seems that they use Jekyl to convert Markdown into HTML. There however is a plugin to use Asciidoctor to do the same.
Having used both Asciidoctor and Markdown, I think Asciidoctor is far more superior when it comes to features. Especially when it comes to the syntax, I don't quite like how easy it is to mess up a Markdown file.
Just as an example: If you want to output some code, in MD you have to prefix every line of code with four spaces, in adoc you put it in between two "-----" blocks.
Lists in MD require you to separate each line with two spaces:
* first level
* first level
* second level
In adoc this is:
* first level
* first level
** second level
Markdown does a lot with spaces and Asciidoc does the same with duplicating the important chars. Duplicating important chars doesn't get messed up by the line indenting of IDEs.
So how about me investigating how to produce gitpages with asciidoc and having these replace the ApacheCMS pages?
Do we have any special stuff in the CMS or is all just static?
Chris
________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Sonntag, 2. Oktober 2016 07:14:42
An: dev@flex.apache.org
Betreff: Re: [DISCUSS] Switch the site repo to GIT?
It is time to consider getting off of Apache CMS. I think some projects
have done so already. I'd like to know more about what we lose/gain if we
go way from Apache CMS.
Some projects are experimenting with GitHub Pages. I think it should be
considered as well.
-Alex
On 10/1/16, 9:11 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Orher projects using git for the cms what are using?
>Could we switch, for example, to a wordpress cms if we want?
>
>
>
>El sábado, 1 de octubre de 2016, Christofer Dutz
><ch...@c-ware.de>
>escribió:
>
>> Ok so it turns out that as long as we use the Apache CMS we can't change
>> to GIT. Guess this was the reason for still being on GIT.
>>
>>
>> I have no idea what we really need the CMS for, but as long as we need
>> this, we seem to be stuck there :-(
>>
>>
>> Chris
>>
>> ________________________________
>> Von: Alex Harui <aharui@adobe.com <javascript:;>>
>> Gesendet: Donnerstag, 29. September 2016 18:56:39
>> An: dev@flex.apache.org <javascript:;>
>> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
>>
>>
>>
>> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de
>> <javascript:;>> wrote:
>>
>> >Hi guys,
>> >
>> >
>> >as you might know I have been working hard on the site-generation and
>> >this finally seems to be working nicely. The only problem I have is
>>that
>> >I can't submit to the site repo from the Build agent as SVN isn't setup
>> >to allow that. Git however is able to commit without hard-coding
>> >credentials. Infra suggested to move our site to GIT to resolve this
>> >issue.
>> >
>> >
>> >I was wondering anyway why this is our only SVN repo. Wouldn't it be
>>cool
>> >to have everything in one type of repo?
>>
>> The fact our web site is on SVN isn't a big deal to me, but what is a
>>big
>> deal is 99% of the time I find the two-step staging/publish workflow
>> really painful. Related, there is currently no way for the MD5 checker
>>on
>> the CI server to update the website automatically. If moving to Git
>>gets
>> us out of that, I'd be for it. Can you provide more info on how folks
>>do
>> staging when working on big overhauls and why Git doesn't have this
>> credential issue?
>>
>> Thanks,
>> -Alex
>>
>>
>
>--
>
>Carlos Rovira
>Director General
>M: +34 607 22 60 05
>http://www.codeoscopic.com
>http://www.avant2.es
>
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.
Re: [DISCUSS] Switch the site repo to GIT?
Posted by Alex Harui <ah...@adobe.com>.
It is time to consider getting off of Apache CMS. I think some projects
have done so already. I'd like to know more about what we lose/gain if we
go way from Apache CMS.
Some projects are experimenting with GitHub Pages. I think it should be
considered as well.
-Alex
On 10/1/16, 9:11 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Orher projects using git for the cms what are using?
>Could we switch, for example, to a wordpress cms if we want?
>
>
>
>El sábado, 1 de octubre de 2016, Christofer Dutz
><ch...@c-ware.de>
>escribió:
>
>> Ok so it turns out that as long as we use the Apache CMS we can't change
>> to GIT. Guess this was the reason for still being on GIT.
>>
>>
>> I have no idea what we really need the CMS for, but as long as we need
>> this, we seem to be stuck there :-(
>>
>>
>> Chris
>>
>> ________________________________
>> Von: Alex Harui <aharui@adobe.com <javascript:;>>
>> Gesendet: Donnerstag, 29. September 2016 18:56:39
>> An: dev@flex.apache.org <javascript:;>
>> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
>>
>>
>>
>> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de
>> <javascript:;>> wrote:
>>
>> >Hi guys,
>> >
>> >
>> >as you might know I have been working hard on the site-generation and
>> >this finally seems to be working nicely. The only problem I have is
>>that
>> >I can't submit to the site repo from the Build agent as SVN isn't setup
>> >to allow that. Git however is able to commit without hard-coding
>> >credentials. Infra suggested to move our site to GIT to resolve this
>> >issue.
>> >
>> >
>> >I was wondering anyway why this is our only SVN repo. Wouldn't it be
>>cool
>> >to have everything in one type of repo?
>>
>> The fact our web site is on SVN isn't a big deal to me, but what is a
>>big
>> deal is 99% of the time I find the two-step staging/publish workflow
>> really painful. Related, there is currently no way for the MD5 checker
>>on
>> the CI server to update the website automatically. If moving to Git
>>gets
>> us out of that, I'd be for it. Can you provide more info on how folks
>>do
>> staging when working on big overhauls and why Git doesn't have this
>> credential issue?
>>
>> Thanks,
>> -Alex
>>
>>
>
>--
>
>Carlos Rovira
>Director General
>M: +34 607 22 60 05
>http://www.codeoscopic.com
>http://www.avant2.es
>
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.
Re: [DISCUSS] Switch the site repo to GIT?
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Orher projects using git for the cms what are using?
Could we switch, for example, to a wordpress cms if we want?
El sábado, 1 de octubre de 2016, Christofer Dutz <ch...@c-ware.de>
escribió:
> Ok so it turns out that as long as we use the Apache CMS we can't change
> to GIT. Guess this was the reason for still being on GIT.
>
>
> I have no idea what we really need the CMS for, but as long as we need
> this, we seem to be stuck there :-(
>
>
> Chris
>
> ________________________________
> Von: Alex Harui <aharui@adobe.com <javascript:;>>
> Gesendet: Donnerstag, 29. September 2016 18:56:39
> An: dev@flex.apache.org <javascript:;>
> Betreff: Re: [DISCUSS] Switch the site repo to GIT?
>
>
>
> On 9/29/16, 1:43 AM, "Christofer Dutz" <christofer.dutz@c-ware.de
> <javascript:;>> wrote:
>
> >Hi guys,
> >
> >
> >as you might know I have been working hard on the site-generation and
> >this finally seems to be working nicely. The only problem I have is that
> >I can't submit to the site repo from the Build agent as SVN isn't setup
> >to allow that. Git however is able to commit without hard-coding
> >credentials. Infra suggested to move our site to GIT to resolve this
> >issue.
> >
> >
> >I was wondering anyway why this is our only SVN repo. Wouldn't it be cool
> >to have everything in one type of repo?
>
> The fact our web site is on SVN isn't a big deal to me, but what is a big
> deal is 99% of the time I find the two-step staging/publish workflow
> really painful. Related, there is currently no way for the MD5 checker on
> the CI server to update the website automatically. If moving to Git gets
> us out of that, I'd be for it. Can you provide more info on how folks do
> staging when working on big overhauls and why Git doesn't have this
> credential issue?
>
> Thanks,
> -Alex
>
>
--
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
http://www.avant2.es
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.