Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E3FAE200C73 for ; Wed, 26 Apr 2017 00:51:38 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E2A19160BB6; Tue, 25 Apr 2017 22:51:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0FEA9160BB3 for ; Wed, 26 Apr 2017 00:51:37 +0200 (CEST) Received: (qmail 71061 invoked by uid 500); 25 Apr 2017 22:51:37 -0000 Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@groovy.apache.org Delivered-To: mailing list dev@groovy.apache.org Received: (qmail 71051 invoked by uid 99); 25 Apr 2017 22:51:37 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Apr 2017 22:51:37 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 89322C074C for ; Tue, 25 Apr 2017 22:51:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.295 X-Spam-Level: X-Spam-Status: No, score=-0.295 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.796, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=asert-com-au.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 50zHW4l6euA1 for ; Tue, 25 Apr 2017 22:51:35 +0000 (UTC) Received: from mail-io0-f179.google.com (mail-io0-f179.google.com [209.85.223.179]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 5447A5F306 for ; Tue, 25 Apr 2017 22:51:34 +0000 (UTC) Received: by mail-io0-f179.google.com with SMTP id p80so107393740iop.3 for ; Tue, 25 Apr 2017 15:51:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=asert-com-au.20150623.gappssmtp.com; s=20150623; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to; bh=Xd0P7oM0ERd9VTFC+5BBfWy2DTY21Ci7fzTkCRytsgo=; b=sa1nKfo4jekR/HG9haPo6j8dTLDCAeq9SHdWO6VdJ58HLCpusfpxgRUPetICWYfljN i+KR0BbGq4mz+3crEFcFm6SvBYyHgaPnncMgdjltxNMeJPz6ldvMMawGE5+gSnP+kc2q rhG/f0JyS9ralcYmOGT0WJwvQZ6ezF2a8gdWf2nfwwSHnH2CYRhJon2GKhTw2Tdp5E2R PAL+g5OtWTi7Q7CVVoQQd/0YoVZkREqN3tE2SG/GDTWqvd1WyK3v+6R2nSpqArtorp3a 2a/msZd++6iiX7BPUnIPef/D3egC52xvbt8g3q2xL0CE1KQEYOug0DimVBXe/V4Lf3jm lZ2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=Xd0P7oM0ERd9VTFC+5BBfWy2DTY21Ci7fzTkCRytsgo=; b=aBNT0pn4DwrP6+JDGafUKOiRnWwZH5o+jFDJGgy//pI5PhHvTlWPgsJuBLZeXWQvE3 2pzFS6B8SMLC9xgZBQJVPC1mFYATGt+tO1KwRJgN2ogZfzuT3NTcx7JmHxqoDQU1W/vR WHT4shObGiap22nidwBPqietpt+jHK7SXDjfuJ754Tc9kTaxlswFo6ugZppil53QjSPR 1EPsHHolTnOXpuEo5NYk2ugdS/Apte/dytZCHyagtQp+s65ymrEGZKgiJbyoS7P6p7Py Nkqc1OzqI5oefpcJb6OnV5cIX8M8LiArgnk7hHc5jV6frDBt0VfA93k6h6I3Y4y0Fke6 J9Qw== X-Gm-Message-State: AN3rC/4FHHXTx0eLnDJJ+RaMvkwPNSHkXoe2yQ7uVReM3GvMJZQKpckG JT+FLRZu5O28rYZRwPjq5DJmv8X6PA== X-Received: by 10.107.6.224 with SMTP id f93mr18072108ioi.210.1493160692761; Tue, 25 Apr 2017 15:51:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.11.194 with HTTP; Tue, 25 Apr 2017 15:51:32 -0700 (PDT) Reply-To: paulk@asert.com.au In-Reply-To: References: From: Paul King Date: Wed, 26 Apr 2017 08:51:32 +1000 Message-ID: Subject: Re: moving the Groovy website To: dev@groovy.apache.org Content-Type: multipart/alternative; boundary=001a113fb632af5a15054e0590b2 archived-at: Tue, 25 Apr 2017 22:51:39 -0000 --001a113fb632af5a15054e0590b2 Content-Type: text/plain; charset=UTF-8 The history will still be there in the old repo - just not as easily accessible in the new repo if we do a clean slate approach. On Wed, Apr 26, 2017 at 8:43 AM, Guillaume Laforge wrote: > Yeah it's less critical than for our codebase, obviously. > There's not much need to go back'n forth in time, in the history, for the > website. > So I think it's okay if we have to drop the history. > There have 44 contributors to the documentation, but a majority was on > very small changes, like typos, new user groups, and such. Not big bang > changes to the website. > > On Wed, Apr 26, 2017 at 12:30 AM, Paul King wrote: > >> One question I have. How important is the git history of the website? Is >> a clean slate copy of all the files to the new repo acceptable? I'd never >> want to do this for code but is it less of an issue for the site? Note: >> this doesn't affect user guide doco which is versioned in the code repo >> along with the code - I'm talking about the fairly static pages on the site >> (downloads, events, mailing-lists, etc.). >> >> Thanks, Paul. >> >> On Wed, Apr 26, 2017 at 7:57 AM, Paul King wrote: >> >>> >>> One of the action items we've had since joining Apache is to move our >>> website onto Apache infrastructure. We've made changes to our release >>> process to make it easier to publish a new release's documentation onto the >>> site and we are finally getting around to actually moving the site. This >>> will hopefully happen over the next few weeks and our goal will be to make >>> it as seamless as possible. >>> >>> More details will follow - this is just a heads-up for anyone planning >>> to make changes to the site for the next little while. Probably best to >>> pre-announce any such changes and I can give advice as to which repo(s) you >>> should target. We might need to make changes in two places for a very short >>> period. >>> >>> Cheers, Paul. >>> >> >> > > > -- > Guillaume Laforge > Apache Groovy committer & PMC Vice-President > Developer Advocate @ Google Cloud Platform > > Blog: http://glaforge.appspot.com/ > Social: @glaforge / Google+ > > --001a113fb632af5a15054e0590b2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
The history will still be there in the old repo - just not= as easily accessible in the new repo if we do a clean slate approach.

On Wed, Apr 26, = 2017 at 8:43 AM, Guillaume Laforge <glaforge@gmail.com> wro= te:
Yeah it's less c= ritical than for our codebase, obviously.
There's not much need to = go back'n forth in time, in the history, for the website.
So = I think it's okay if we have to drop the history.
There have = 44 contributors to the documentation, but a majority was on very small chan= ges, like typos, new user groups, and such. Not big bang changes to the web= site.

On Wed, Apr 26, 2017 at 12:30 AM, Paul King <paulk= @asert.com.au> wrote:
One question I have. How important is the git history of the we= bsite? Is a clean slate copy of all the files to the new repo acceptable? I= 'd never want to do this for code but is it less of an issue for the si= te? Note: this doesn't affect user guide doco which is versioned in the= code repo along with the code - I'm talking about the fairly static pa= ges on the site (downloads, events, mailing-lists, etc.).

Thanks, Paul.

On Wed, Apr 26, 2017 at 7:57 AM, Paul King <paulk@asert.= com.au> wrote:

One of the action items we've had since joining Apache is= to move our website onto Apache infrastructure. We've made changes to = our release process to make it easier to publish a new release's docume= ntation onto the site and we are finally getting around to actually moving = the site. This will hopefully happen over the next few weeks and our goal w= ill be to make it as seamless as possible.

More de= tails will follow - this is just a heads-up for anyone planning to make cha= nges to the site for the next little while. Probably best to pre-announce a= ny such changes and I can give advice as to which repo(s) you should target= . We might need to make changes in two places for a very short period.

Cheers, Paul.




<= /div>--
Guillaume Laforge
Apache Groovy com= mitter & PMC Vice-President
Developer Advocate @ = Google Cloud Platform


--001a113fb632af5a15054e0590b2--