Just a very, very vague question: When can the public exspect access to a ( surely very leaky ) cleaned up skeleton of ROS?
I mean that we have a running system, without the unchecked ( unclean ) components, so that people can start working again on the clean code.
For example: We can boot and explorer pops up. Nothing more. So we can fix bugs in NTOSKRNL, FREELDR and EXPLORER...
Greetings, Jan Schiefer
I still have a working ROS copy via my old Trunk directory, but I assume that's more than worthless now.
On 1/28/06, Jan Schiefer cheaterjs@gmx.de wrote:
Just a very, very vague question: When can the public exspect access to a ( surely very leaky ) cleaned up skeleton of ROS?
I mean that we have a running system, without the unchecked ( unclean ) components, so that people can start working again on the clean code.
For example: We can boot and explorer pops up. Nothing more. So we can fix bugs in NTOSKRNL, FREELDR and EXPLORER...
Greetings, Jan Schiefer
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
-- "I had a handle on life, but then it broke"
As far as I know, there is suspect code even in NTOSKRNL, HAL and the low-level components.
Jonathan Wilson schrieb:
As far as I know, there is suspect code even in NTOSKRNL, HAL and the low-level components.
Arghl...however I think cleaning up the very basic components is most important.
It may be a psycological effect, but if you have at least something very basic running, you can show that ROS is not entirely dead and that progress is being made...
ROS is maybe one of the most ambitious open source projects, and shouldn't go to coma or even die.
Greetings, Jan Schiefer!