[ros-dev] Nevermind

Casper Hornstrup ch at csh-consult.dk
Mon Aug 29 16:31:11 CEST 2005



> -----Original Message-----
> From: ros-dev-bounces at reactos.com [mailto:ros-dev-bounces at reactos.com] On Behalf Of Rick
> Langschultz
> Sent: 29. august 2005 15:25
> To: ReactOS Development List
> Subject: [ros-dev] Nevermind
> 
> Since I heard of reactos, i have always considered it one day
> replacing my Windows 2000 and XP boxes. Because ReactOS was going to
> be an open-source alternative to the Windows NT API I felt that it
> had and has serious potential to hinder or greatly replace Microsoft
> Windows. I have suggested several ideas both through IRC (freenode)
> and email messages how the computing world does things. I understand
> that ReactOS is still in pre-production, and planning for the next
> release is greatly important to the community development and testing
> of the operating system, however I fail to grasp the concept behind
> the hindrance of ideas being passed the the development community.

Which hindrance?

> Some development plans I have talked about were:
>      1 - A 64 bit journaling file system with a SQL-like back-end.
>           Lookout WinFS; there that plan went down the drain.
>      2 - Implementing an instant messenger server for developers and
> users to talk on, realtime, without IRC.
>           Maybe not quite MSN Messenger, but why not? iChat even
> uses .mac.
>      3 - Implementing an OpenLDAP back-end to the website.
>          Active Directory has nothing on you... Plan knocked out again.
> 
> i would rather stick with something close minded like closed source
> software than having no ideas be recognized at all.
> I only suggest things like this because Microsoft will always be
> releasing newer software that will leave reactos in the dust if they
> not heed the advice of all, not just me, their developers, testers,
> and users.
> 
> Why not; right? why envision something and it fail to be realized,
> waste of time if i ever knew it...

Most of the suggestions you make requires several man-years of work to be
implemented. If you want to make any of them happen, you need to do more
than describing them on a mailing list. First of all, you should prioritize
them after level of importance. How important is a WinFS like service when
there are no applications written to use it? Which problems would your
instant messenger server solve that couldn't be solved with existing
technologies? What problems would using OpenLDAP on the website solve?
Then when you have prioritized your ideas, pick the one at the top of the
list and do whatever is needed to implement it. There are several way to
do this:
1) Implement it yourself
2) Convince other developers to implement it
3) Pay other developers to implement it

What they all have in common is that you take the initiative to make it
happen.

Casper




More information about the Ros-dev mailing list