Hi Carlos,
it's just about the static content of the SVN website. Wiki (Confluence) is
something completely separate. I didn't know we have a real Blog, I guess it's
just static content that looks like a blog. But that would be part of the
migration too.
So I guess it's ok to order the repo and I would just start setting up a
"maven-site" branch and start working on this. It doesn't matter if we decide
not to use it, I would like to learn how the other projects using this approach
have their fine looking sites generated this way.
Chris
________________________________
Von: carlos.rov...@gmail.com <carlos.rov...@gmail.com> im Auftrag von Carlos
Rovira <carlos.rov...@codeoscopic.com>
Gesendet: Freitag, 7. Oktober 2016 00:02:17
An: dev@flex.apache.org
Betreff: Re: [Website] Proposal for the Git Site
Hi Chris,
I think steps are the right ones, and the name os ok. But I want to
understand the scope right. I saw the discussion about Markdown or Adoc.
But first I want to know what things are included in this migration. Is the
wiki? the blog as well? the website?
In case the website is included, I asked before, about to install a
Wordpress instance. I have skills on that and can help.
So for me, steps are right, but want to know more about what pieces are
included.
Thanks
2016-10-06 11:57 GMT+02:00 Christofer Dutz <christofer.d...@c-ware.de>:
> Ok .. so Infra said, that renaming the repo would be a problem, but that
> there shouldn't be any collisions with the SVN repo. So we could call it
> "flex-site" ... Any objections against me requesting infra to setup that
> "flex-site" repo?
>
>
> Chris
>
> ________________________________
> Von: Christofer Dutz <christofer.d...@c-ware.de>
> Gesendet: Donnerstag, 6. Oktober 2016 09:23:09
> An: dev@flex.apache.org
> Betreff: [Website] Proposal for the Git Site
>
> Hi,
>
>
> in order to proceed on this topic, I would like to propose the following
> means of action:
>
> 1. I request a new git repo for our project (flex-site.apache.org or
> whatever name we give it)
>
> 2. I create a maven branch in there and start implementing things as a
> maven site
>
> 3. I create a maven-asf-site branch
>
> 4. I create a buildbot job to publish the site to that maven-asf-site
> branch
>
>
> Others can add their versions of site generation to dedicated branches
> ("xyz") to that repo too. Then they would also create buildbot build jobs
> to publish "xyz" to "xyz-asf-site" ... we do a little discussion on the
> options and pick one, finish the implementation and merge that branch to
> master/develop and adjust the corresponding build job to publish to
> "asf-site". After that we ask Infra to rename the repo and activate the
> gitpubsub thingy to use the new asf-site branch content as our project
> website.
>
>
> What do you think?
>
>
> Chris
>
--
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.
