Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: unknown (athena.apache.org: error in processing during lookup of
 pdion@cloudops.com)
MIME-Version: 1.0
In-Reply-To: <70333697-5ACF-4DD6-974D-4EFBB0205EAF@gmail.com>
References: <CC7B59E4-31DE-435A-B443-E65018CF9E94@gmail.com>
	<066B7790-7FD1-4649-84E0-2C6DDCB65A22@gmail.com>
	<70333697-5ACF-4DD6-974D-4EFBB0205EAF@gmail.com>
Date: Thu, 20 Mar 2014 10:33:58 -0400
Message-ID: 
 <CAD97iofqs0toapZ9yzyZM=yDQMbFX9owFjWz0fp8p9c=oTyNpw@mail.gmail.com>
Subject: Re: [DOCS] Re: docs question
From: Pierre-Luc Dion <pdion@cloudops.com>
To: dev@cloudstack.apache.org
Content-Type: multipart/alternative; boundary=001a1133b04ae1272604f50aa8d9

--001a1133b04ae1272604f50aa8d9
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I like this workflow.  I'm not experienced with pull request, hope it's not
be complicated for a doc repo...

Stagging site seams perfect !


Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -

*CloudOps*420 rue Guy
Montr=E9al QC  H3J 1S6
www.cloudops.com
@CloudOps_


On Thu, Mar 20, 2014 at 10:17 AM, sebgoa <runseb@gmail.com> wrote:

> Mainly informing myself for archiving purposes :)
>
> We stand at:
>
> http://docs.cloudstack.apache.org
> http://docs.cloudstack.apache.org/projects/cloudstack-installation
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes
> http://docs.cloudstack.apache.org/projects/cloudstack-administration
>
> That's the cleanest I can make it without creating new CNAMEs or changing
> our repo architecture.
>
> I used those URLs in the new Documentation drop down menu on the site, it
> looks like this in staging:
>
> http://cloudstack.staging.apache.org
>
> and as I am typing this, I realized that I actually published the site so
> it's live, oups....Yell if you see a problem
>
> I kept a link to the old docs called "Obsolete Docs"
>
> PS:
> Thanks, to Pierre Luc, Nux, Geoff and Chris snow who sent pr testing the
> new workflow.
> Thanks to Shankar, Paul, Ian and Tuna for new content already.
>
>
> On Mar 19, 2014, at 1:48 PM, sebgoa <runseb@gmail.com> wrote:
>
> >
> > On Mar 19, 2014, at 12:09 PM, sebgoa <runseb@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> Question #1:
> >> ------------------
> >>
> >> With the new move to RTD we need to agree on a URL naming convention.
> >>
> >> Currently we have one CNAME that points to RTD site (don't worry about
> the content on that page):
> >>
> >> http://docs.cloudstack.apache.org
> >>
> >> Using RTD sub projects features this gives us the following URLs to ge=
t
> to the admin and install guide.
> >>
> >> http://docs.cloudstack.apache.org/projects/cloudstack-installation
> >> http://docs.cloudstack.apache.org/projects/cloudstack-administration
> >>
> >> The cloudstack-installation and cloudstack-administration are not
> changeable, RTD does not allow to change that.
> >>
> >> Are we fine with this ? It seems a bit long to me.
> >>
> >> If we are not fine with this, the alternative is to create other CNAME=
s
> via apache infra to point to those guides.
> >>
> >> Question #2:
> >> ------------------
> >>
> >> What do we want the landing page http://docs.cloudstack.apache.org to
> have ?
> >>
> >> On the cloudstack.apache.org website I was thinking of extending the
> tab to link to each guide. This would work well with a CNAME per guide.
> >> But if we keep a single link to 'DOCS' on our main website, then the
> question of the docs landing page is there.
> >>
> >>
> >> what say you folks ?
> >>
> >
> > To illustrate a bit, check:
> >
> > http://cloudstack.staging.apache.org
> >
> > Then click on the 'documentation' drop down....select 'Doc Root' or
> 'Installation Docs' or 'Release Notes'
> >
> >>
> >> -Sebastien
> >
>
>

--001a1133b04ae1272604f50aa8d9--