I have a proposal to put before Matrox which I'd like to discuss here first.
1) A new page on the matrox website titled "Beta Drivers" or similar.
2) A disclaimer which visitors must agree to to enter this page, stating:
a) beta drivers have not been thoroughly tested
b) beta drivers are for experienced users only
c) Matrox accepts no responsiblilty for damage caused
d) Matrox will not provide support for users of beta software
I'm sure the lawyers can come up with something suitable.
3) Every new build of the ICD is posted to this page promptly, i.e. within 24 hours of its creation. This would be in the form of a .zip file containing the updated files and documentation, not the whole powerdesk package.
4) A progress log, updated with every new release, which is both available on the web page (so that users can check if the changes are relevant to them before downloading the files) and included with the download, as a file called "WHATSNEW.TXT" or similar. This file is to contain details of all significant changes since the previous version, split into two sections, one covering performance issues and the other compatability (things that are believed fixed, things that are believed broken). Also, details of the development team's plans (for example which issues they plan to address next, with a realistic timescale).
5) The creation of a database into which users may submit, over the web, details of any compatability issues they may have found, including details of their system specification and the circumstances under which the problem arises. This would allow the development team to better prioritise their work.
6) A period of time (perhaps a few hours each week) during which the driver development team will be available in a public chat situation (i.e a channel on IRC) to discuss current driver issues directly with end users.
These are only suggestions to get things started, the details need to worked out, but what do you all think? Is anyone with me on this?
Smiff
1) A new page on the matrox website titled "Beta Drivers" or similar.
2) A disclaimer which visitors must agree to to enter this page, stating:
a) beta drivers have not been thoroughly tested
b) beta drivers are for experienced users only
c) Matrox accepts no responsiblilty for damage caused
d) Matrox will not provide support for users of beta software
I'm sure the lawyers can come up with something suitable.
3) Every new build of the ICD is posted to this page promptly, i.e. within 24 hours of its creation. This would be in the form of a .zip file containing the updated files and documentation, not the whole powerdesk package.
4) A progress log, updated with every new release, which is both available on the web page (so that users can check if the changes are relevant to them before downloading the files) and included with the download, as a file called "WHATSNEW.TXT" or similar. This file is to contain details of all significant changes since the previous version, split into two sections, one covering performance issues and the other compatability (things that are believed fixed, things that are believed broken). Also, details of the development team's plans (for example which issues they plan to address next, with a realistic timescale).
5) The creation of a database into which users may submit, over the web, details of any compatability issues they may have found, including details of their system specification and the circumstances under which the problem arises. This would allow the development team to better prioritise their work.
6) A period of time (perhaps a few hours each week) during which the driver development team will be available in a public chat situation (i.e a channel on IRC) to discuss current driver issues directly with end users.
These are only suggestions to get things started, the details need to worked out, but what do you all think? Is anyone with me on this?
Smiff
Comment