Hi all
I agree that forking should be avoided at all costs. Of course it will be unavoidable for lower level DLLs such as user32. I'm getting the tail end of this discussion so someone please fill me in if I'm missing some big issues. The big deal with be source control differences between the two projects - we'll probably have to come up with a document on this to clarify things.
Regards Jason
--- Steven Edwards steven_ed4153@yahoo.com wrote:
--- "Dimitrie O. Paun" dpaun@rogers.com wrote:
I think forking them does no one no favours, either Wine for
ReactOS.
If our code is OK, tweaking it to work around bugs in ReactOS is
a
very, very bad idea: -- you end up with a system capable of running just some
tweaked
apps -- it diminishes incentive to fix the real problem -- we end up with a forked codebase Similarly, if we have problems in our codebase, we'd appreciate fixes, or at least to know about it. This is the entire reason to want
our
stuff to be portable -- to have other people test the code and
report
(or even fix) problems. If you fork the code, you also cut the
stream
of patches flowing into Wine.
In the end we both lose. Even if you don't care about Wine, I
can't
see how forking anything is a good idea for ReactOS.
Dont get me wrong I dont think it is either. I just dont make the policy as to how we are going to handle this in ReactOS. I am all for us working together as much as possible with little or no forking but its going to take some work to setup a system that will work for both partys.
I will start by setting up a box that does weekly builds for Mingw/ReactOS.
Thanks Steven
Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com _______________________________________________ Ros-kernel mailing list Ros-kernel@reactos.com http://reactos.geldorp.nl:8080/mailman/listinfo/ros-kernel
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com