Mailing-List: contact gump-help@jakarta.apache.org; run by ezmlm
Message-ID: <401A6C24.3070508@latte.harvard.edu>
Date: Fri, 30 Jan 2004 09:37:24 -0500
From: "Mark R. Diggory" <mdiggory@latte.harvard.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.6a) Gecko/20031030
MIME-Version: 1.0
To: Gump code and data <gump@jakarta.apache.org>
Subject: Re: [proposal] Is it time for gump.apache.org?
References: <589085D2-532C-11D8-9237-000393D2CB02@apache.org>
In-Reply-To: <589085D2-532C-11D8-9237-000393D2CB02@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Well, to loop back into other discussions related to this.

1.) there is the interest by the repository folks to setup 
"repo.apache.org", with the repository directory structure they've 
outlined. Maven users are also interested in seeing this usable as a 
compatable maven repository.

2.) We would like to see a uniform location for developer nightly builds 
for apache projects using Maven, directory structure is very important 
in this case though. Automation via gump would also be of the highest 
benefit.

So my question is: would gump.apache.org be where the continuous build 
process got dumped out to or would it be where the gump project website 
resided.

if its for the continuous build contents, what are thoughts about 
something generic like

builds.apache.org or nightly.apache.org
distributions.apache.org

-Mark

Stefano Mazzocchi wrote:
> First of all, let me say that I'm *very* impressed by the work done on 
> Python Gump. It's *sweet*! I think it's about time that we switch away 
> from the old shell+xslt version that is much harder to maintain and adapt.
> 
> Second, I have root access on moof.apache.org and would love to help 
> setup a pygump installation there, making the official apache one and 
> finally retiring the one on nagoya which was slow as hell.
> 
> Moreover, it always bothered me that gump was under the supervision of 
> the jakarta PMC while it is a much more general purpose project, but Sam 
> and I agreed that until Gump had its own community, a top level domain 
> would have been a bad idea.
> 
> I think that Gump does have enough traction for becoming top level.
> 
> So, here is my proposal:
> 
>  1) install pygump on moof.apache.org
> 
> [macosx box located at apple, not huge but should be enough since it's 
> currently doing nothing.. note that we are waiting for new shiny boxes 
> that are coming from IBM, so if our needs grow, we will have plenty of 
> room to grow without effecting the ASF infrastructure (one of those 
> boxes was conceived for gump explicitly)]
> 
>  2) initiate the burocratic process to get Gump as a Top Level Domain
> 
> [I volunteer to help that process]
> 
> What do you think?
> 
> -- 
> Stefano.

-- 
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu