commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <brit...@apache.org>
Subject Re: Re: [PROPOSAL] Setup up new sandbox component "Commons Text" with git as primary vcs (Was: Re: [sandbox] New sandbox component)
Date Mon, 10 Nov 2014 07:18:04 GMT
Hi,

https://issues.apache.org/jira/browse/INFRA-8595 has already been
resolved... Sorry, I messed that one up. Are you okay if we start using the
commons-text repo and decide how we want to handle git repos for any new
sandbox repos?

Benedikt

2014-11-09 14:53 GMT+01:00 Gary Gregory <garydgregory@gmail.com>:

> This is all reasonable but I do not think this is what our site
> documents.  So let's make sure we either follow our current charter or
> document a new system.
>
> Gary
>
> <div>-------- Original message --------</div><div>From: Emmanuel Bourg
<
> ebourg@apache.org> </div><div>Date:11/09/2014  08:23  (GMT-05:00)
> </div><div>To: Commons Developers List <dev@commons.apache.org>
> </div><div>Subject: Re: [PROPOSAL] Setup up new sandbox component "Commons
> Text" with
>   git as primary vcs (Was: Re: [sandbox] New sandbox component) </div><div>
> </div>Le 09/11/2014 13:43, Gary Gregory a écrit :
>
> > How would you know that commons-text is a sandbox component? You would
> not
> > if it is git, unless the URL has 'sandbox' in it.
>
> It's a sandbox component because its site will state so. I still think
> using a special directory layout or naming scheme for the sandbox
> components is a bad idea, it just makes the transition to proper, the
> vcs and the site management more complicated.
>
> Emmanuel Bourg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message