Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Date: Fri, 12 Oct 2012 15:14:14 +0100
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: sebb <sebbaz@gmail.com>
Cc: general@incubator.apache.org
Subject: Re: ${podling}.incubator.apache.org
Message-ID: <20121012141414.GA9015@tarsus.local2>
References: <20121012073111.GD3769@lp-shahaf.local>
 <CAOGo0VaDQOGAd6RaPQF17U+5nZmx6AX4Rgas1=Ovahg_QKGTSA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAOGo0VaDQOGAd6RaPQF17U+5nZmx6AX4Rgas1=Ovahg_QKGTSA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

sebb wrote on Fri, Oct 12, 2012 at 13:05:06 +0100:
> On 12 October 2012 08:31, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > Do people mind if web sites (and maybe mailing lists) of new podlings
> > live at domains of the form "${podling}.incubator.apache.org"?
> >
> > This is in relation to infra work on streamlining TLP migrations.  (Case
> > in point: CMS TLP migrations.)  This thread is about the
> > externally-visible names, not about implementation details.
> 
> Seems good to me.
> 
> At present the podling websites are implemented as folders within the
> top-level incubator website; this has always struck me as rather
> awkward as it limits what names can be used. (It also makes for messy
> permissions issues as not all podlings use svnpubsub yet, but that
> will of course disappear soon).

Actually there is another problem, it means the incubator site must be
checked out before the podling sites.  But that happens only when we
rebuild the web server...

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org