The effectiveness of a sandbox would be limited - a majority of discovered issues relate to content that is beyond the control of Diigo - but still, a sandbox could be useful for at least the following:
* testing * reporting issues * confirming issues * working around issues * resolving issues * confirming resolution.
On one hand:
* traditionally, routine maintenance of a sandbox is associated with the provider of that sandbox.
On the other hand:
* the nature of Diigo - highlights and annotations authored by users - shifts much of the onus to those users.
(We should tidy up after ourselves :)
= Precaution =
I don't imagine sandboxes being used for closed alpha or beta testing. Use thereof could lead to closed test participants discovering each others' identities. Discovery and discussion between participants is sometimes contrary to the requirements of a test.
Might you provide a sandbox for users of Diigo?
The effectiveness of a sandbox would be limited - a majority of discovered issues relate to content that is beyond the control of Diigo - but still, a sandbox could be useful for at least the following:
* testing
* reporting issues
* confirming issues
* working around issues
* resolving issues
* confirming resolution.
On one hand:
* traditionally, routine maintenance of a sandbox is associated with the provider of that sandbox.
On the other hand:
* the nature of Diigo - highlights and annotations authored by users - shifts much of the onus to those users.
(We should tidy up after ourselves :)
= Precaution =
I don't imagine sandboxes being used for closed alpha or beta testing. Use thereof could lead to closed test participants discovering each others' identities. Discovery and discussion between participants is sometimes contrary to the requirements of a test.
To Top