Return-Path: X-Original-To: apmail-community-dev-archive@minotaur.apache.org Delivered-To: apmail-community-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6BA51175F6 for ; Thu, 5 Mar 2015 14:43:48 +0000 (UTC) Received: (qmail 53694 invoked by uid 500); 5 Mar 2015 14:43:48 -0000 Delivered-To: apmail-community-dev-archive@community.apache.org Received: (qmail 53462 invoked by uid 500); 5 Mar 2015 14:43:48 -0000 Mailing-List: contact dev-help@community.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@community.apache.org Delivered-To: mailing list dev@community.apache.org Received: (qmail 53450 invoked by uid 99); 5 Mar 2015 14:43:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Mar 2015 14:43:47 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of runseb@gmail.com designates 209.85.212.178 as permitted sender) Received: from [209.85.212.178] (HELO mail-wi0-f178.google.com) (209.85.212.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Mar 2015 14:43:23 +0000 Received: by widem10 with SMTP id em10so36658061wid.0 for ; Thu, 05 Mar 2015 06:42:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=U9N6/1kfI9WyEhmM3yKICyz+xKNoZIamT8Ciak4jDXc=; b=HDFzs4YS1/q0+AH8fJ1R6pajiDHBxyfHbf8cgfhR+Lvg4vxAY+YYv51VlvifJU1IjA D1VquVfAPimujAhb+UFnbs68O3NXCZUofHhWYswBWbLBsGAguq+LM3YeEm9UPSzQtd1j U5R8CzQ+5yoEABVgMMS99k6pWekhrDdqGobK4CJotaUI8N5OhP1ezPa69v0BeQNYi7P/ hDeIPJJ1x/aTyoLkurSpoVc10EpqfcfjSOR7CXUhNE2UfCTzpTbf3McOwI6xDn4NMoUC bIC8V1vDGKS8VXvxwgWHeomZxFZ5zAfblFhj/xPlK3h56a+nCG7bPYqYT8BwOu9X5RKg WUdQ== X-Received: by 10.180.76.178 with SMTP id l18mr22950174wiw.36.1425566557040; Thu, 05 Mar 2015 06:42:37 -0800 (PST) Received: from [10.0.0.3] (131.177.199.178.dynamic.wline.res.cust.swisscom.ch. [178.199.177.131]) by mx.google.com with ESMTPSA id t9sm30020153wia.15.2015.03.05.06.42.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 05 Mar 2015 06:42:35 -0800 (PST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: GitHub Pages From: Sebastien Goasguen In-Reply-To: <54F82070.6000409@apache.org> Date: Thu, 5 Mar 2015 09:42:52 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <64629D0B-C726-4660-8681-0BEE05677EA4@gmail.com> References: <54F82070.6000409@apache.org> To: dev@community.apache.org X-Mailer: Apple Mail (2.1510) X-Virus-Checked: Checked by ClamAV on apache.org So FWIW, I never thought about using github pages for our website. I just tried it. Created an orphaned gh-pages in our repo, pushed that. It got mirrored = right away and now we have: http://apache.github.io/cloudstack/ Based off of: https://github.com/apache/cloudstack/tree/gh-pages Loving it, -sebastien On Mar 5, 2015, at 4:22 AM, Sergio Fern=E1ndez = wrote: > Hi Christopher, >=20 > GitHub Pages is actually powered by Jekyll: http://jekyllrb.com >=20 > So that would mean to add such build method to Apache CMS. >=20 > I'd be more than happy to explore such path. >=20 > On 04/03/15 22:06, Christopher wrote: >> All, >>=20 >> Has any thought been put into leveraging GitHub pages for project >> documentation, static site hosting? A lot of www.apache.org is simple >> static content, as are project pages. Since a lot of projects are now = using >> git, and we mirror projects in GitHub, perhaps we can help the = individual >> projects maintain their site's static content by simply committing to = a >> gh-pages branch for their project? >>=20 >> Since it's just static content which is still hosted and controlled = by ASF, >> but simply placed in a way that GitHub can render it from the = mirrors, I >> don't think there's too many issues of concern, but wasn't sure if >> anybody's put any thought into it. I know it would certainly be = easier for >> some projects than using the existing CMS system with SVN (especially = those >> otherwise developing exclusively with Git). >>=20 >> It might "just work" today, but I haven't tried it. I'd be willing to = work >> with INFRA to help experiment with it, though (especially if we = wanted to >> try out the CNAME feature). >>=20 >> More info: https://pages.github.com/ >>=20 >> -- >> Christopher L Tubbs II >> http://gravatar.com/ctubbsii >>=20 >=20 > --=20 > Sergio Fern=E1ndez > Partner Technology Manager > Redlink GmbH > m: +43 660 2747 925 > e: sergio.fernandez@redlink.co > w: http://redlink.co