Okay, just a thought, these prices would never change, and a fellow dev
has physical access to the machine, but at any rate...i had to offer.
Jason Filby wrote:
Hi Richard
On point 2, as Ge has mentioned, we have physical access to our boxen
now - and everything is available at no cost to the project. I prefer
this even if the hardware offered at a cost from a hosting company is
superior because these companies can change their mind on the prices
at
any time and because of the freedom we have with physical access. But
thanks for checking it out!
Cheers
Jason
Richard Campbell wrote:
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?
_______________________________________________
ros-general mailing list
ros-general(a)reactos.com
http://reactos.com/mailman/listinfo/ros-general
__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
_______________________________________________
ros-general mailing list
ros-general(a)reactos.com
http://reactos.com/mailman/listinfo/ros-general