Category:OS/4 Hardware: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
Those wishing to participate, should know that keeping their pages constantly updated is '''vital''' for development of the project: if a confirmed hardware, unexpectedly stop to work between few releases, developers will understand immediately where are bugs and they will fix them as fast as possible, before go on. If a model/laptop/motherboard does not work anymore tomorrow, try to understand and solve causes, between 5 years, it could be very, very difficult, if the gap will include 4000 interim releases! This simple periodic verification technique rather, involve users for very few minutes daily, weekly or at least monthly, but it will be of '''paramount importance''' to the team!  
Those wishing to participate, should know that keeping their pages constantly updated is '''vital''' for development of the project: if a confirmed hardware, unexpectedly stop to work between few releases, developers will understand immediately where are bugs and they will fix them as fast as possible, before go on. If a model/laptop/motherboard does not work anymore tomorrow, try to understand and solve causes, between 5 years, it could be very, very difficult, if the gap will include 4000 interim releases! This simple periodic verification technique rather, involve users for very few minutes daily, weekly or at least monthly, but it will be of '''paramount importance''' to the team!  


This model of developing software, which involves team and users/tester directly, brings to excellent results in short times, and it is more than tested.
This model of developing software, which involves team and users/tester directly, '''brings to excellent results in short times''', and it is more than tested.
   
   
We here, will simply use a more user-friendly version rather than a complex professional development system, hard to manage and to understand for end users.
We here, will simply use a more user-friendly version rather than a complex professional development system, hard to manage and to understand for end users.

Revision as of 16:31, 21 September 2016

This is a list of Hardware tested with the OS/4 project.

This pages's intent is to keep trace of progresses about Phoenix OS/4 development.

All users who are using, are testing or simply desire to test it, can help here team, informing it about compatibility, if model in use is working or not, failures and generally, how bug-fixes go on. Simply keeping trace about progressive svn, time by time. This will inform team about progresses and that tested hardware still works and there are not compatibility issues, backwards-steps, breaks, failures in progress, that potentially, could put in stand-by the development project.

Those wishing to participate, should know that keeping their pages constantly updated is vital for development of the project: if a confirmed hardware, unexpectedly stop to work between few releases, developers will understand immediately where are bugs and they will fix them as fast as possible, before go on. If a model/laptop/motherboard does not work anymore tomorrow, try to understand and solve causes, between 5 years, it could be very, very difficult, if the gap will include 4000 interim releases! This simple periodic verification technique rather, involve users for very few minutes daily, weekly or at least monthly, but it will be of paramount importance to the team!

This model of developing software, which involves team and users/tester directly, brings to excellent results in short times, and it is more than tested.

We here, will simply use a more user-friendly version rather than a complex professional development system, hard to manage and to understand for end users.

Users, once created his own card, specifying all parameters used to start succesfully the operating system, will simply update periodically tested releases, intervening only when and where necessary talking directly to the team for details.

Developers will do their job knowing that all work fine and end-users, newbie or testers will enjoy progresses and they will be also happy to test all releases, feeling themselves an active part of the project.