As part of our effort to lower the barier to Designers and other non-programmers to provide feedback in our issue queue - they should be able to chime in, without learning how to use CVS, patch commands and other workflows part of the reviewing an issue activity. I believe this doesn't only benefit the non-programmers though, it also adds lots of speed to any review that needs to be done in the initial phase of many interface patches.

I believe this removes a very large initial boundary, that keeps many designers from spending time on this project. And also keeps many programmers from reviewing patches, since it takes some time to just see what its about. We have tried to remove the boundary with screenshots, but we learned that screenschots are unable to provide context or progression as much as real working demo's do.

Due to the previous restraints of the testing framework it was unable to make this step, but from my understanding we are now able to do this. I would love to hear which steps we need to take.

Comments

jthorson’s picture

jthorson commented
Status: Active » Closed (cannot reproduce)

Closing as an old & obsolete (i.e. pre-git migration) issue in an abandoned issue queue ... feel free to re-open in the Testbot queue if you feel we should keep this active.