Greetings!
First, I appreciate the effort to craft templates for artifact evaluation. The idea is valid and I have come across some folks using them.
However, offering the templates only in LateX, that compiles to pdf, is problematic. Artifact evaluation involves steps like copying and executing commands verbatim. Copying text from a pdf is problematic (possible altered symbols, line-wrap handling, etc.). It is also not possible to view the pdf when running in a container/terminal environment. I am also skeptical of the general accessibility of PDFs when navigating without a mouse. For these reasons, plain text, markdown, and other text-based formats are better suited for artifact instructions.
I am opening this issue to propose extending the templates collection with markdown or similar alternatives.
Greetings!
First, I appreciate the effort to craft templates for artifact evaluation. The idea is valid and I have come across some folks using them.
However, offering the templates only in LateX, that compiles to pdf, is problematic. Artifact evaluation involves steps like copying and executing commands verbatim. Copying text from a pdf is problematic (possible altered symbols, line-wrap handling, etc.). It is also not possible to view the pdf when running in a container/terminal environment. I am also skeptical of the general accessibility of PDFs when navigating without a mouse. For these reasons, plain text, markdown, and other text-based formats are better suited for artifact instructions.
I am opening this issue to propose extending the templates collection with markdown or similar alternatives.