Return-Path: X-Original-To: apmail-clerezza-dev-archive@www.apache.org Delivered-To: apmail-clerezza-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1E306EAAB for ; Wed, 6 Mar 2013 06:56:59 +0000 (UTC) Received: (qmail 35793 invoked by uid 500); 6 Mar 2013 06:56:58 -0000 Delivered-To: apmail-clerezza-dev-archive@clerezza.apache.org Received: (qmail 35612 invoked by uid 500); 6 Mar 2013 06:56:58 -0000 Mailing-List: contact dev-help@clerezza.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@clerezza.apache.org Delivered-To: mailing list dev@clerezza.apache.org Received: (qmail 35594 invoked by uid 99); 6 Mar 2013 06:56:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 06:56:58 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.86.168.182] (HELO mxout-07.mxes.net) (216.86.168.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 06:56:51 +0000 Received: from mail-la0-f41.google.com (unknown [209.85.215.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6F9BE22E253 for ; Wed, 6 Mar 2013 01:56:29 -0500 (EST) Received: by mail-la0-f41.google.com with SMTP id fo12so7101432lab.0 for ; Tue, 05 Mar 2013 22:56:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:content-type:x-gm-message-state; bh=QgxHqjAv93CFLbPaIbKAdOFdKY6tBf9ISNB9W1WoFxM=; b=PVE9Kd9RlwFQBipnU3BAnqpouDK3bxsuD1OgjiraZTENuxZEusTzA5uQn00ul+LWtO jr+nNIM/F5u8bY+9amJTF9TSEU3tWD5D/y0ve9f8X379wxpnPYI//Odr8w38vs3U910n EDzchoFara2Rh4n6bRLlv75YTPegGDrLFpHsX2aGQcVj+ZBsG/b76tcL+4fFXwIWy8Nn YAlb2Vvpm+XUaUlR4jE0lOF9pxMpyWljwodL4HrbRayl4aX5RTJufdO1D7w0QIFjdsY4 YsG/Y9JcjqnuNvmOtFTImd69ITcOSoHLXOFejHHK827z+a+S8u6Q4z2mR7OFdMP1GqPr 2BGQ== MIME-Version: 1.0 X-Received: by 10.152.122.100 with SMTP id lr4mr24047761lab.28.1362552987958; Tue, 05 Mar 2013 22:56:27 -0800 (PST) Received: by 10.152.8.138 with HTTP; Tue, 5 Mar 2013 22:56:27 -0800 (PST) X-Originating-IP: [112.119.1.147] In-Reply-To: References: Date: Wed, 6 Mar 2013 07:56:27 +0100 Message-ID: Subject: Re: Need some help and info for moving to Git From: =?ISO-8859-1?Q?Reto_Bachmann=2DGm=FCr?= To: dev@clerezza.apache.org Content-Type: multipart/alternative; boundary=f46d042ef661d5df1504d73c16e4 X-Gm-Message-State: ALoCoQle5dwFFgzooMVngn3fph49EGDoxI7WmwlbU+ty1h1X0xe8F/f4kEU24Fb5KsTRWABd/4CK X-Virus-Checked: Checked by ClamAV on apache.org --f46d042ef661d5df1504d73c16e4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Hasan Sorry I missed that, so we should fix our script to check in the data to svn. right? Cheers, Reto On Wed, Mar 6, 2013 at 7:54 AM, Hasan Hasan wrote: > On Wed, Mar 6, 2013 at 7:35 AM, Reto Bachmann-Gm=FCr > wrote: > > > On Tue, Mar 5, 2013 at 6:39 AM, Hasan Hasan wrote: > > > > > Hi Reto > > > > > > An excerpt of [2]: > > > > > > The infrastructure team currently supports two main mechanisms for > > > publishing and maintaining project sites: > > > - svnpubsub, which allows the static contents of a designated svn > folder > > > (example) to automatically published as the project web site at > > > http://project.apache.org/. The project team can use any site build > > > mechanism it wants as long as the above requirements are met. > > > - Apache CMS, which provides a simple browser-based user interface fo= r > > > editing, staging and publishing site content in Markdown, HTML or any > > other > > > source format for which support has been added. See the CMS reference > and > > > adoption for more details. The Apache CMS uses svnpubsub as the > > underlying > > > mechanism for publishing a site. > > > > > > Some projects still use a deprecated site deployment system based on > > > periodic synchronization of static files from people.apache.org to th= e > > > live > > > web servers. This mechanism will be discontinued at the end of 2012, = by > > > which time all projects should have migrated to one of the above site > > > publishing mechanisms. > > > > > > -- end of excerpt -- > > > > > > Thus, if we don't want to use svnpubsub, we have to use Apache CMS. O= r > > am I > > > missing something here? > > > > > > > We can't use it for or clerezza based process as described here: > > http://svn.apache.org/viewvc/clerezza/site/trunk/readme.txt?view=3Dmark= up > > > the deploy.sh script copies site files to /www/ > incubator.apache.org/content/clerezza > which is not allowed anymore. > We may not use people.apache.org to host our site files. > > cheers > hasan > > > > > > > Cheers, > > Reto > > > > > > On Tue, Mar 5, 2013 at 6:07 AM, Reto Bachmann-Gm=FCr > > wrote: > > > > > Hi Hasan > > > > > > I'm not sure about the project layout. But I don't think that a speci= al > > > casing for the site is needed because we don't use svnpubsub. Also I > see > > no > > > harm in adding the site as a normal project to the reactor. Especiall= y > > now > > > when the reactor is no longer the released unit. > > > > > > Cheers, > > > Reto > > > > > > On Mon, Mar 4, 2013 at 11:29 PM, Hasan wrote: > > > > > > > Dear all, > > > > > > > > To move from svn to git we should file a ticket on infra mentioning > the > > > > following [1]: > > > > > > > > project unix name > > > > project layout > > > > portions of svn tree to leave writable (e.g. ASF CMS site sources) > > > > > > > > The project unix name would be clerezza. That's clear. > > > > But how about the project layout and portions of svn tree to leave > > > > writable? > > > > Regarding the portions of svn tree to leave writable, would it be > > > > clerezza/site ? > > > > > > > > Note that the infrastructure team currently supports two main > > mechanisms > > > > for publishing and maintaining project sites [2]: svnpubsub and > Apache > > > CMS > > > > According to [1] Git is not supported by svnpubsub. > > > > > > > > So please help me with answering the questions above and other task= s > > for > > > > moving to git [3]. > > > > > > > > [1]: http://www.apache.org/dev/infra-contact#requesting-graduation > > > > [2]: http://www.apache.org/dev/project-site#intro > > > > [3]: https://git-wip-us.apache.org/docs/switching-to-git.html > > > > > > > > cheers > > > > hasan > > > > > > > > > > --f46d042ef661d5df1504d73c16e4--