Okay guys, some tidbits...

[Richard Campbell]

Okay guys, i have a couple points to make and a couple questions to ask.

1)  I propose that we move all common dlls used by both wine and ROS to 
a seperate repository or module and maybe overhaul them and work on a 
common build system that will work for both the WINE and ReactOS 
projects, as well as other open source projects that need these files.  
What do you guys think of this idea?  Think we could get the WINE 
people's support?

2)  CVS and webhosting, rex, jason, whoever else, can you give me an 
idea of how much bandwidth per month CVS and the reactos websites 
consume?  I might have a possible hosting solution we can use...(OC12, 
p4 1.8, 1 gb RAM rackmount), the only snag is, depending on how much 
bandwidth the combined total uses, we'd have to come up with $10-$30/mo 
to help pay for the solution.  Is this a viable option?

3)  can someone please commit the win32api build needed to build ROS to 
a module in CVS?

[Casper Hornstrup]

>   -----Oprindelig meddelelse-----
>  Fra: ros-general-bounces(a)reactos.com 
>  [mailto:[e-mail]] På vegne af Richard Campbell
>  Sendt: 29. december 2003 12:11
>  Til: ros-general(a)reactos.com
>  Emne: [ros-general] Okay guys, some tidbits...
>  
>  
>  Okay guys, i have a couple points to make and a couple 
>  questions to ask.
>  
>  1)  I propose that we move all common dlls used by both wine 
>  and ROS to 
>  a seperate repository or module and maybe overhaul them and work on a 
>  common build system that will work for both the WINE and ReactOS 
>  projects, as well as other open source projects that need 
>  these files.  
>  What do you guys think of this idea?  Think we could get the WINE 
>  people's support? 
You will never see WINE move away from autoconf and they have good
reasons
for not doing so. WINE needs to be built on many platforms.

I'd hate to see ReactOS depend on autoconf for reasons stated in my
other
mail to ros-kernel.

>   2)  CVS and webhosting, rex, jason, whoever else, can
> you give me an 
>  idea of how much bandwidth per month CVS and the reactos websites 
>  consume?  I might have a possible hosting solution we can 
>  use...(OC12, 
>  p4 1.8, 1 gb RAM rackmount), the only snag is, depending on how much 
>  bandwidth the combined total uses, we'd have to come up with 
>  $10-$30/mo 
>  to help pay for the solution.  Is this a viable option? 
Maybe just the downloadable releases should be hosted there? Sometimes
it is
nice to have easy physical access to the machine and I understand that
we
have this now.

>   
>  3)  can someone please commit the win32api build needed to 
>  build ROS to 
>  a module in CVS? 
Right. IMO, ReactOS should be always be able to be built with the newest
w32api release.

Casper

[Ge van Geldorp]

>   > From: Richard Campbell
>  >
>  > 2)  CVS and webhosting, rex, jason, whoever else, can you give me an
>  > idea of how much bandwidth per month CVS and the reactos websites 
>  > consume?  I might have a possible hosting solution we can 
>  > use...(OC12, p4 1.8, 1 gb RAM rackmount), the only snag is, 
depending
>   > on how much  bandwidth the combined total uses,
> we'd have to come up
>  > with $10-$30/mo to help pay for the solution.  Is this a viable 
option?
>   
>  Maybe just the downloadable releases should be hosted there? 
>  Sometimes it is nice to have easy physical access to the 
>  machine and I understand that we have this now. 
We have total control over reactos.com, I have physical access to it.
Rex has physical access to the CVS box. Both don't cost anything at the
moment.

Just checked the logs for December. Based on the Apache logs, we
generated at least 8 GB of web traffic (which is far more than I had
expected btw). Looking at the size of the mail archives and the number
of subscribers to each list, I estimate we generated about 240 MB for
mail traffic.

Gé van Geldorp.