Return-Path: Delivered-To: apmail-avalon-dev-archive@avalon.apache.org Received: (qmail 1727 invoked by uid 500); 20 Feb 2003 01:14:15 -0000 Mailing-List: contact dev-help@avalon.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon Developers List" Reply-To: "Avalon Developers List" Delivered-To: mailing list dev@avalon.apache.org Received: (qmail 1614 invoked from network); 20 Feb 2003 01:14:14 -0000 Received: from fep01-mail.bloor.is.net.cable.rogers.com (66.185.86.71) by daedalus.apache.org with SMTP; 20 Feb 2003 01:14:14 -0000 Received: from [192.168.1.101] ([24.157.133.102]) by fep01-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.06 201-253-122-126-106-20020509) with ESMTP id <20030220011411.EHAA4827.fep01-mail.bloor.is.net.cable.rogers.com@[192.168.1.101]>; Wed, 19 Feb 2003 20:14:11 -0500 Subject: Re: maven-style repository for avalon stuff? From: Jason van Zyl To: Avalon Developers List Cc: board@apache.org In-Reply-To: <200302200051.h1K0pLp07418@localhost.localdomain> References: <200302200051.h1K0pLp07418@localhost.localdomain> Content-Type: text/plain Organization: Zenplex Message-Id: <1045703648.2761.159.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 19 Feb 2003 20:14:08 -0500 Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH PLAIN at fep01-mail.bloor.is.net.cable.rogers.com from [24.157.133.102] using ID at Wed, 19 Feb 2003 20:14:11 -0500 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Wed, 2003-02-19 at 19:51, Greg Stein wrote: > In article , "Leo Simons" > wrote: > >... > > so would it make sense to have http://avalon.apache.org/repository > > contain the avalon jars & dists? It is probably easy as hell for the > > maven peeps to do a > > > > ssh daedalus.apache.org > > cd /www/avalon.apache.org/repository > > scp -r * wherever_it_goes_on_ibiblio > > > > on request, so that ibiblio can remain the primary point of > > distribution. > > Please note that the Board wants to see ASF-operated hardware as the > only, definitive point of distribution. Other sites are free to > *re*distribute, but the primary point should be from an ASF box. I think this needs to be discussed and shouldn't be unilaterally dictated by the board. I think Ibiblio is a valid location ASF artifacts. Part of their mandate is to help proliferate OSS software. They are secure and using them would alleviate an enormous amount of bandwidth from Apache. If all our artifacts were put there imagine the savings on hardware and bandwidth costs. Are we up in the TB area? How much of this is distributions? Could we not strike an agreement with Ibiblio? They've got the horsepower and they are willing to share it. > (today, that means icarus, daedalus, or nagoya; I believe the Maven folk > have some boxen at rackspace.com; when that gets a foo.apache.org name, > and the infrastructure people assume some level of admin capability over > it, then that can be another distro point) There's no way we could afford the bandwidth. We plan on using it for housing the admin app which will forward submitted artifacts to the central repo but we would just get slaughtered. > > All this just temporarily until the infrastructure peeps > > and the peeps looking at a common repository hammer out something more > > solid. > > Maybe this statement is that you see ibibilio as temporary? Not sure how > to read it, but non-ASF-box distribution should be considered a bug to fix > asap, rather than a temporary solution. The ASF shouldn't participate or > condone actions or policies which (potentially) violate software > licenses. The whole repository has been audited now, there isn't a single violation. Dion Gillard saw to that personally going through every artifact on Ibiblio. > Thx, > -g -- jvz. Jason van Zyl jason@zenplex.com http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org For additional commands, e-mail: dev-help@avalon.apache.org