[ros-dev] Roadmap I'm sticking to

[Aleksey Bragin]

As the message says, it's the one I used for directing my own work  
(even the message subject says so!).

I wanted to sum it up and present for discussion for a long time, and  
yesterday's talk gave a nice reason. If more people agree with this  
plan, then it has a chance of becoming one of the project's roadmaps  
for, let's say, "usability" component of the OS. And of course, be  
completed much quicker rather than if I work alone and other would be  
adding new, minor, untested and unnecessary code (no personal  
offense, just a common example).

WBR,
Aleksey.



On Apr 8, 2010, at 5:03 PM, Ged Murphy wrote:

> I'm confused. Is this your personal roadmap or a team roadmap?
>
> If it's a personal roadmap then this highlights one of the main  
> problems
> with reactos. Everyone works as an individual with no team spirit  
> and most
> people work on things which are at best unimportant and at worst  
> completely
> useless to the v1.0 goal.
>
> If it's a team roadmap then aren't they supposed to be discussed  
> and agreed
> upon as a team instead of dictated?
>
> Ged.
>
>
> -----Original Message-----
> From: ros-dev-bounces at reactos.org [mailto:ros-dev- 
> bounces at reactos.org] On
> Behalf Of Aleksey Bragin
> Sent: 08 April 2010 13:54
> To: ReactOS Development List
> Subject: [ros-dev] Roadmap I'm sticking to
>
> 	Hello,
> yesterday we had a usual rant in #reactos-dev regarding organization,
> teaming and development issues, and I explained how I see it. I think
> explaining and discussing here would be beneficial.
>
> I won't spend your time explaining how I came to this roadmap, I will
> go right to it. This roadmap is mainly usage-oriented and doesn't
> cover the kernel (it has its own one).
>
> * Finish wine-based subsystem ("arwinss"), fixing all internal
> (absent in Wine and/or trunk) bugs.
> Milestone 1: user32 and gdi32 known to work and support at least all
> the apps listed in the Wine app compat database.
> * Test as many as possible apps known to work in Wine and determine
> those which fail.
> * Fix failing components (kernel32, ntdll, kernel, CSR, non-synced
> DLLs, etc).
> Milestone 2: ReactOS supporting quite wide amount of applications,
> including major apps like MS Office suites, Open Office, CAD systems,
> Adobe products.
> Decision point: Because other Win32 components are proven to work, NT-
> alike user32, gdi32 and win32k development may be boosted, testing
> simplified.
> * Implement filesystem drivers, using fastfat_new as a universal
> skeleton for FS drivers. Use ntfs3g library and that skeleton to
> develop an NTFS IFS driver.
> Milestone 3: ReactOS with NTFS support (quite important for end
> users, thus separated into a standalone milestone).
> * Total rewrite of networking, using NT's one as a model.
> Milestone 4: ReactOS with a rock-stable networking. Ability to host
> database servers, web and FTP servers.
> * Release 1.0 and profit ;)
>
>
> So that's what I'm sticking to so far. I don't expect everyone to
> agree, but if more people are involved, achieving these milestones
> will happen faster. Also, they don't really have to go in a sequence,
> all of that may be done simulteneously (e.g. filesystem drivers must
> be developed against Windows 2003; kernel32 and ntdll could be fixed
> first using winetests without waiting for arwinss to be complete;
> networking could be again tested in existing ReactOS and Windows).
>
> Comments, improvements are welcome.
>
> WBR,
> Aleksey Bragin.
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev