You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xml.apache.org by Ed Staub <es...@mediaone.net> on 2000/08/17 04:27:22 UTC
Should we outsource the xml.apache.org site?
[Hopefully this won't tick off too many people...]
We (as a group) have been unable to patch or replace bugzilla since it was
taken down over three months ago.
We haven't had a working mail archive for four weeks.
I don't know what the problem is; all I know is that all the committers I've
corresponded with have written "Sorry, I can't do anything about it... we
don't have control".
We really need a functional infrastructure!!!
Does it make sense to outsource the site to, say, sourceforge.net?
-Ed Staub
Re: Should we outsource the xml.apache.org site?
Posted by Mike Pogue <mp...@apache.org>.
+1 for this idea. It's been too long without bug tracking.
Ed Staub wrote:
>
> [Hopefully this won't tick off too many people...]
>
> We (as a group) have been unable to patch or replace bugzilla since it was
> taken down over three months ago.
>
> We haven't had a working mail archive for four weeks.
>
> I don't know what the problem is; all I know is that all the committers I've
> corresponded with have written "Sorry, I can't do anything about it... we
> don't have control".
>
> We really need a functional infrastructure!!!
>
> Does it make sense to outsource the site to, say, sourceforge.net?
>
> -Ed Staub
>
> ---------------------------------------------------------------------
> In case of troubles, e-mail: webmaster@xml.apache.org
> To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
RE: Should we outsource the xml.apache.org site?
Posted by Sander van Zoest <sa...@covalent.net>.
On Thu, 17 Aug 2000, Ed Staub wrote:
> Sander,
>
> I'll be very happy to see it!
> We've been having an extensive redesign discussion on the Xerces-J list over
> the last six weeks.
> Doing it without a collective "memory" has been difficult.
> Do you have an idea of when "shortly" is?
Well, I am pretty much debugging, but you know how that goes. After
I get through that, I think I will throw it up on a test server and
have it run there for a while. I do not know an exact time frame, since
it isn't totally all up to me, but we are getting there.
--
Sander van Zoest [sander@covalent.net]
Covalent Technologies, Inc. http://www.covalent.net/
(415) 536-5218 http://www.vanzoest.com/sander/
RE: Should we outsource the xml.apache.org site?
Posted by Ed Staub <es...@mediaone.net>.
Sander,
I'll be very happy to see it!
We've been having an extensive redesign discussion on the Xerces-J list over
the last six weeks.
Doing it without a collective "memory" has been difficult.
Do you have an idea of when "shortly" is?
Thanks,
-Ed Staub
-----Original Message-----
From: Sander van Zoest [mailto:sander@covalent.net]
Sent: Thursday, August 17, 2000 1:27 AM
To: general@xml.apache.org
Subject: Re: Should we outsource the xml.apache.org site?
On Wed, 16 Aug 2000, Ed Staub wrote:
> We haven't had a working mail archive for four weeks.
I am currently putting finishing touches on an mailing archive for these
lists that should be available shortly. Dirk had already mentioned this
before, but I had to redesign some things, so therefore the delay.
My appologies,
--
Sander van Zoest
[sander@covalent.net]
Covalent Technologies, Inc.
http://www.covalent.net/
(415) 536-5218
http://www.vanzoest.com/sander/
---------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org
Re: Should we outsource the xml.apache.org site?
Posted by Sander van Zoest <sa...@covalent.net>.
On Wed, 16 Aug 2000, Ed Staub wrote:
> We haven't had a working mail archive for four weeks.
I am currently putting finishing touches on an mailing archive for these
lists that should be available shortly. Dirk had already mentioned this
before, but I had to redesign some things, so therefore the delay.
My appologies,
--
Sander van Zoest [sander@covalent.net]
Covalent Technologies, Inc. http://www.covalent.net/
(415) 536-5218 http://www.vanzoest.com/sander/