I don't think we have a problem here. So far Apache has been using machines offered by collab.net if I'm not mistaken to host all the Web sites and the overall infrastructure (mailing lists, CVS etc.). For them this incurs some costs and administrative headaches obviously. If some projects choose to offload them and host at least their Web site on a different machine, it should be no problem.
We can still maintain the mailing lists, CVS at collab.net as they are right now, but place the Web site on the same machine which hosts cocoondev.org. We can arrange to have cocoon.apache.org point to this machine.
IMO cocoon.apache.org and cocoondev.org should remain separate, preferably the later under the same ASF umbrella:
- cocoon.apache.org should host Cocoon, the project
- cocoondev.org should host applications using Cocoon, which may or may not be free of commercial interests
Using the same infrastructure will help us minimize the administrative costs which translates into more time spent on useful work.
I don't think there's any legal issue having the machine hosted elsewhere, but I may be wrong. Dirk?
Best regards,
--
Ovidiu Predescu <[EMAIL PROTECTED]>
http://webweavertech.com/ovidiu/weblog/
On Thursday, Oct 31, 2002, at 03:04 US/Pacific, Carsten Ziegeler wrote:
Steven Noels wrote:I really value your effort, Steven, and of course of those others helping<snipped good explanation I really value/>
you
in createing cocoondev.org. It's a great idea! And I don't want that you
have to throw away all the effort already put into cocoondev.org.
But, *if* Cocoon becomes a top-level project, I'm not sure if it is also
a good thing to use cocoondev.org as the infrastructure. Now I see
two possible problems:
a) What is hosted where? Is a mailing list hosted at apache or at
cocoondev.org etc. Of course, this might not be a big thing, but
it could confuse others.
We could use cocoondev.org for example for show casing Cocoon
and everything else is hosted at apache.
b) Legal issues. To be honest, I don't know much about legal things,
but I guess that it might make a difference if something is done
on a server hosted by apache or on a server not hosted by apache.
Don't get me wrong, I really like the idea of cocoondev.org and as long
as Cocoon is not a top-level project, it's the only way.
But if we become a top-level project, I really like the idea to "fix
the current problems/shortcommings" here at Apache.
Perhaps we can talk more about this at the gettogether.
Carsten
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
