development strategy
Moderator: Moderator Team
development strategy
i think we the reactos community alongside with its developers should have more discussions and reviews about the reactos software development strategy to have more solid planning so developers can prioritize the most important things to be look out first only like making the os completely stable and just take care of the secondary needs when its already in its beta stage because developers just cant handle many things the same time, so we can speed its development and no more delays... hoping everyone gets involve in the discussion
Re: development strategy
The developers appear to set their own priorities based on their individual preferences (always subject to change, of course), their individual expertise, and discussions among themselves. The developers are aware of the features the ReactOS community would like and they take that into consideration when they choose the work to take on but they will not let the forum community tail wag the ReactOS Project dog. I'm ok with that.
When developers write about their current work in the blogs or the forums they are making a gift to the community. I appreciate their articles. Yes, I wish they would outline a project roadmap but creating one then following it has not served the ReactOS project well in the past. Z98 recently stated, "We also do not give estimates for completion for anything." (See Raymond Chen's article Once you announce a date, you're already late in his blog The Old New Thing.) The ReactOS developers prefer making progress happen over talking about what might happen. There is a saying I once heard from the late Louis Rukeyser (I paraphrase from memory), "He who makes crystal-ball predictions must learn to eat a lot of crushed glass".
See the current objectives for version 0.4 in the ReactOS wiki. (These objectives are subject to change. Notice that there is no hint of when version 0.4 of ReactOS will be released.)
Also, for the curious, here are the issues/bugs currently marked Fix Version: 0.4.0 in ReactOS's JIRA bugtracker.
"If you want to hear God laugh, tell Him your plans."--proverb
When developers write about their current work in the blogs or the forums they are making a gift to the community. I appreciate their articles. Yes, I wish they would outline a project roadmap but creating one then following it has not served the ReactOS project well in the past. Z98 recently stated, "We also do not give estimates for completion for anything." (See Raymond Chen's article Once you announce a date, you're already late in his blog The Old New Thing.) The ReactOS developers prefer making progress happen over talking about what might happen. There is a saying I once heard from the late Louis Rukeyser (I paraphrase from memory), "He who makes crystal-ball predictions must learn to eat a lot of crushed glass".
See the current objectives for version 0.4 in the ReactOS wiki. (These objectives are subject to change. Notice that there is no hint of when version 0.4 of ReactOS will be released.)
Also, for the curious, here are the issues/bugs currently marked Fix Version: 0.4.0 in ReactOS's JIRA bugtracker.
"If you want to hear God laugh, tell Him your plans."--proverb
Re: development strategy
im well aware of all that including the community site where we vote for the course outline of the project , my point is how's the strategy for making the entire development as efficient as much as possible? where is it, right now? and about the blog im always reading it and i dont believe on "elemental-hero jesus christ" but thnx for your comment btw
Re: development strategy
Process management doesn't do anything when there are fundamental bottlenecks in manpower. The existing infrastructure already streamlines quite a few tasks and it's pretty much nearing the limits of what help it can provide. Any attempt to try to tell developers what to work on is a non-starter since the majority of them are volunteers. Even the ones on contract accepted their contracts because the work stipulated in the contract was within their interests. So no, there is no magic solution that will suddenly accelerate ReactOS development.
Re: development strategy
so that means the real problem is still the same, we still have insufficient number of developers, however as a product tester id have to say that i just test the latest build of 0.3.17 of 2015 and comparing it with the very 1st release of 0.3.17, i have to admit im very impressed with the improvements( its almost ready for the beta stage) however our reactos seems to show lot of issues with browsing and drivers that is sometimes not responding "when being run on old computers or computers with low specs( pentium4 or much weaker hardware ) and so far the rest is pretty much really good to go already, all it needs is to be more compatible with windows apps without encountering some errors
Re: development strategy
A optimization work is needed in reactos, so as you can see from the gsoc page in reactos wiki a rewrite of network drivers is planned, and hope someone will take it in charge.arlon1 wrote:however our reactos seems to show lot of issues with browsing and drivers that is sometimes not responding "when being run on old computers or computers with low specs( pentium4 or much weaker hardware )
But modern browsers are really more complex and slower compared with first one, you can't expect performance with the last version of firefox on a pc that is designed to run netscape 4.
Z98 wrote:So no, there is no magic solution that will suddenly accelerate ReactOS development.
One solution was suggested by the comunity, involve want-to-be-developer on easy tasks creating a sort of
intenal gsoc. A quick and easy solution is tag jira issues that core-developer don't have time to implement.
It will be also a solution to "grow-up" new developer. just select a tag, mark some issues and inform the comunity what
this mean.
Re: development strategy
dear tonix,
yeah your right but not just the network drivers but also some other external hardware drivers as well and there are times it lags and when the lags kicks in, the entire screen is like completely frozen and when that happens, refreshing it doesn't work and the only solution is to forced restart the computer again but in much newer powerful computers specifically design for gaming, majority of the people don't encounter these problems .My point is; developers should test-run all their builds and finished products on old computer or computers with low specs to see all the most common issues to it. So what's your opinion tonix?
memberlist.php?mode=viewprofile&u=10747
yeah your right but not just the network drivers but also some other external hardware drivers as well and there are times it lags and when the lags kicks in, the entire screen is like completely frozen and when that happens, refreshing it doesn't work and the only solution is to forced restart the computer again but in much newer powerful computers specifically design for gaming, majority of the people don't encounter these problems .My point is; developers should test-run all their builds and finished products on old computer or computers with low specs to see all the most common issues to it. So what's your opinion tonix?
memberlist.php?mode=viewprofile&u=10747
Re: development strategy
My opinion is: there are no finished product at this time, reactos need stability, and only after it's acquired, performance.arlon1 wrote:dear tonix,
yeah your right but not just the network drivers but also some other external hardware drivers as well and there are times it lags and when the lags kicks in, the entire screen is like completely frozen and when that happens, refreshing it doesn't work and the only solution is to forced restart the computer again but in much newer powerful computers specifically design for gaming, majority of the people don't encounter these problems .My point is; developers should test-run all their builds and finished products on old computer or computers with low specs to see all the most common issues to it. So what's your opinion tonix?
memberlist.php?mode=viewprofile&u=10747
Ever with newer pc and commercial operating system this append, and reactos is still in Alfa.
That is the first motivation leaving reactos is still in alfa.
Re: development strategy
Going a little deep the memory manage of reactos in unfinished and o,n sytem with low memory resouces, arrive at a memory saturation is easy, especially with application that consume a lot of it as web browsers.
Also the cache manager is not perfect, the component that should preserve memory.
The drivers have some bugs that shuold be fixed, and also kernel support for drivers has bugs and hacks.
it's really to early to think about pc with limited resources.
Also the cache manager is not perfect, the component that should preserve memory.
The drivers have some bugs that shuold be fixed, and also kernel support for drivers has bugs and hacks.
it's really to early to think about pc with limited resources.
Re: development strategy
lets say they're already workin on the drivers and memory management issue, aside from the bugs and windows apps compatibility issues, what else are the major problems that needs attention? and btw do you like the idea of reactos being integrated with another browser aside from internet explorer ?
yeah, thx for clearing up some of the misunderstood stuffs about the reactos.
yeah, thx for clearing up some of the misunderstood stuffs about the reactos.
Re: development strategy
There many area of reactos that need attention, is a big and complex project check the bugtrucker to have an idea...arlon1 wrote:lets say they're already workin on the drivers and memory management issue, aside from the bugs and windows apps compatibility issues, what else are the major problems that needs attention? and btw do you like the idea of reactos being integrated with another browser aside from internet explorer ?
yeah, thx for clearing up some of the misunderstood stuffs about the reactos.
Internet explorer is in reactos because windows has internet explorer and because wine project has developed it,
is not the "true" internet explorer but a compatible implementation.
Windows does'nt have other browser integreted, so probably also the official reactos will not have other one.
But in future i hope there will be other reactos distribution with integrated other software,
in same way that linux have many distribution.
In reactos already exist an integrated app manager to download firefox and other browsers.
Re: development strategy
The "Wine/ReactOS Internet Explorer" actually uses the rendering engine from Firefox, if that helps.
Re: development strategy
if they can use something based on firefox, don't you think its better if they just based it from chromium ?Black_Fox wrote:The "Wine/ReactOS Internet Explorer" actually uses the rendering engine from Firefox, if that helps.
Re: development strategy
i know but the project's goal is to have a windows operating system that can run all our favorite windows app that we need and not to completely make a carbon copy of microsoft windows that might get us sued, in other words we are making our own version of windows. And plzz do more explanation on the reactos' integrated app manager .. i haven't check this feature yet.Tonix wrote:There many area of reactos that need attention, is a big and complex project check the bugtrucker to have an idea...arlon1 wrote:lets say they're already workin on the drivers and memory management issue, aside from the bugs and windows apps compatibility issues, what else are the major problems that needs attention? and btw do you like the idea of reactos being integrated with another browser aside from internet explorer ?
yeah, thx for clearing up some of the misunderstood stuffs about the reactos.
Internet explorer is in reactos because windows has internet explorer and because wine project has developed it,
is not the "true" internet explorer but a compatible implementation.
Windows does'nt have other browser integreted, so probably also the official reactos will not have other one.
But in future i hope there will be other reactos distribution with integrated other software,
in same way that linux have many distribution.
In reactos already exist an integrated app manager to download firefox and other browsers.
Re: development strategy
Unless I myself re-write huge amounts of code to replace the Firefox components in ReactOS with Chromium equivalents, my answer to your speculative question means nothing to anybody whose opinion matters.arlon1 wrote:if they can use something based on firefox, don't you think its better if they just based it from chromium ?
Here is some background (as I understand it). ReactOS's browser and HTML rendering reuses code from the Wine project. Long ago the devs with the Wine project chose to implement those features by using Firefox code, specifically the Mozilla Gecko engine. Why didn't Wine give Chromium a chance? As Woody Allen once said, "80 percent of success is showing up." Chromium had not shown up. (Not yet existing probably had something to do with that.)
"Talk is cheap. Show me the code."--Linus Torvalds
Who is online
Users browsing this forum: No registered users and 10 guests