Re: cvs access

I think that if we're going to move at all, we should move completely
(assuming the initial osworkflow move works out OK of course!). In the long
run it would get terribly confusing if people have to go to sf.net for
mailing lists, java.net for code. And we should try to move sooner rather
than later so that we're settled in before the wave of 2.0 releases hit the
general public.

"Hani Suleiman" <[email protected]> wrote in message
news:[email protected]...
> I think it's time to seriously consider moving to java.net for cvs at
> the very least. sf.net is a complete joke, and yes, I realise that in
> time, java.net might degrade, but over there we'd at least be competing
> with a bunch of other java projects for bandwidth, vs
> java/c/c++/php/ruby/js/python projects.
>
> So, I propose that osworkflow moves first, as a trial test run.
> Opinions?
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01