Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of nslater@tumbolia.org designates
 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+96GG7caJ+uK2ZKbPa83pVJxULgetabJ1VvgaFaprv75xbxpQ@mail.gmail.com>
References: 
 <CA+96GG7caJ+uK2ZKbPa83pVJxULgetabJ1VvgaFaprv75xbxpQ@mail.gmail.com>
Date: Fri, 12 Oct 2012 11:18:26 +0100
Message-ID: 
 <CA+Y+445E7+p4C+by0=-N8H1o11-oUgS1zTKH0U1F42UEpBrs_A@mail.gmail.com>
Subject: Re: [WEBSITE] Download page for review on staging
From: Noah Slater <nslater@tumbolia.org>
To: cloudstack-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8f5034e82f9e2804cbda0240

--e89a8f5034e82f9e2804cbda0240
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Oct 11, 2012 at 5:57 PM, Chip Childers <chip.childers@sungard.com>wrote:

> Hi all,
>
> I've committed some changes to the incubator.a.o/cloudstack downloads
> page, which can be seen here on the staging site:
>
> http://cloudstack.staging.apache.org/cloudstack/downloads.html
>
> Any comments / concerns with the new structure of the page?
>

Looks great, Chip.

You should probably link to the http and https versions of the Git
repository.

You can check out the code using the git command:


git clone http://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git


Committers should use the secure repository:


git clone https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git


Also, I would not link to the Citrix CloudStack Github repos. This page has
various issues with it, as I have addressed in a previous thread that is
still not resolved. Linking to it from this section only compounds those
issues IMO.

Two thoughts from me:
>
> 1 - Once we do a second ASF release, we'll add a link to the Apache
> release archives in the "Older CloudStack Releases" section.
>

Remember that we'll probably end up with various active release lines, so
the page has to support those. You could have a 5.0.x section, and a 4.0.x
section, for example. If they are active (i.e. we're still releasing minor
updates, bugfixes, then they both need to be prominantly displayed on this
page.) When we make them inactive, we simply remove them from this page,
and from the dist dir. At that point, we can add a link that takes you to
the archived dist dir, but it should be a low key text link at the bottom.


> 2 - Should we include the URLs (and instructions for how to configure)
> for Wido's DEB repo?  And also the yet to be made RPM repo?  Wido,
> obviously you get a veto on this.
>

Yep! But clearly marked out, for obvious reasons.

-- 
NS

--e89a8f5034e82f9e2804cbda0240--