domains / families / research / uist-artifact-evaluation

uist-artifact-evaluation

separate

Use when packaging the artifacts behind a UIST paper — code, toolkits, hardware design files, and datasets — first as anonymous review-time evidence that the system is real, then as a public release engineered for reuse, in a venue with no formal badge committee doing the checking for you.

When to use

• packaging UIST paper artifacts
• preparing review-time evidence
• engineering public releases for reuse
• packaging hardware design files
• packaging datasets and models
• packaging toolkits and authoring systems

When not to use

• formal badge committee checking

Skill page

Source