<div dir="ltr">Dear Publication Chairs,<br><br>We encountered an issue in which the affiliation information caused our paper to exceed the page limit. Accordingly, prior to the deadline, we submitted an inquiry to TAPS Support with the source files of the paper attached. We subsequently received a response from Mr. Neeraj Kumar of the support team, stating, "We are looking into this and will get back to you with our suggestions at the earliest." However, we have not yet received any further communication and are still awaiting their response.<br><br>Under these circumstances, we would greatly appreciate your guidance on how best to proceed. Please also let us know if there are any additional steps we should take on our part in the meantime.<br><br>Best regards,<br>Minwook Kim</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">2026년 8월 16일 (일) 오전 6:58, Chenhao Ye <<a href="mailto:chenhaoy@cs.wisc.edu">chenhaoy@cs.wisc.edu</a>>님이 작성:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div style="direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Hi authors,</div>
<div style="font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)" dir="ltr">
<br>
</div>
<div style="font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
We noticed that the camera-ready version of your paper has not yet been submitted through TAPS, and the submission deadline has already passed. Please complete your submission as soon as possible to avoid delaying the proceedings publication process.</div>
<div style="font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)" dir="ltr">
<br>
</div>
<div style="font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
If you encounter any technical difficulties, please contact TAPS support (<a href="mailto:tapssupport@aptaracorp.com" target="_blank">tapssupport@aptaracorp.com</a>) and also let us know so that we are aware of the issue.</div>
<div style="font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)" dir="ltr">
<br>
</div>
<div style="font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Best,</div>
<div style="font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Chenhao & Duo</div>
<div style="direction:ltr;font-family:Aptos,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div id="m_-4633002452245178563mail-editor-reference-message-container">
<div>
</div>
<div style="padding:3pt 0in 0in;border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentcolor currentcolor">
<div style="text-align:left;font-family:Aptos;font-size:12pt;color:black">
<b>From: </b>HotStorage 2026 HotCRP <<a href="mailto:noreply-hotstorage26@hotcrp.com" target="_blank">noreply-hotstorage26@hotcrp.com</a>><br>
<b>Date: </b>Saturday, August 1, 2026 at 21:20<br>
<b>To: </b>Minwook Kim <<a href="mailto:ace@snu.ac.kr" target="_blank">ace@snu.ac.kr</a>>; Kyu-Jin Cho <<a href="mailto:bori19960@snu.ac.kr" target="_blank">bori19960@snu.ac.kr</a>>; Jin-Soo Kim <<a href="mailto:jinsoo.kim@snu.ac.kr" target="_blank">jinsoo.kim@snu.ac.kr</a>><br>
<b>Cc: </b><a href="mailto:chairs26@hotstorage.org" target="_blank">chairs26@hotstorage.org</a> <<a href="mailto:chairs26@hotstorage.org" target="_blank">chairs26@hotstorage.org</a>>; Chenhao Ye <<a href="mailto:chenhaoy@cs.wisc.edu" target="_blank">chenhaoy@cs.wisc.edu</a>>; <a href="mailto:duo.zhang@sk.com" target="_blank">duo.zhang@sk.com</a> <<a href="mailto:duo.zhang@sk.com" target="_blank">duo.zhang@sk.com</a>><br>
<b>Subject: </b>[HotStorage 2026] HotStorage’26 Camera-Ready Instructions<br>
<br>
</div>
</div>
<div style="font-size:11pt">Dear authors,<br>
<br>
Congratulations again on the acceptance of your paper to HotStorage’26!<br>
Please follow the instructions below when preparing your camera-ready<br>
submission. *We highly recommend completing the eRights Form (action #2)<br>
as soon as possible, as it takes time for ACM Digital Library to process<br>
it before you can submit the final paper.*<br>
<br>
The camera-ready deadline is **Wednesday, August 12, 2026, Anywhere on<br>
Earth (AoE)**.<br>
<br>
1. Format the paper properly<br>
<br>
- Template: Please prepare your final paper using the latest ACM<br>
template version 2.19 with 10pt font (i.e., your LaTeX file should use<br>
`\documentclass[sigconf,10pt]{acmart}`). You can download the template<br>
from<br>
<a href="https://urldefense.com/v3/__https://www.hotstorage.org/2026/files/hotstorage2026_paper_template.zip__;!!Mak6IKo!L20nMz9GlzeLiaWpA4BngvuRYWLMzu_AOyecJ_XpqD2SgBUCma8Zd2SCx1i3dtHlNrhWZx5Mgi24-fb6x6LchA-5p58UVo8$" target="_blank">https://urldefense.com/v3/__https://www.hotstorage.org/2026/files/hotstorage2026_paper_template.zip__;!!Mak6IKo!L20nMz9GlzeLiaWpA4BngvuRYWLMzu_AOyecJ_XpqD2SgBUCma8Zd2SCx1i3dtHlNrhWZx5Mgi24-fb6x6LchA-5p58UVo8$</a> <br>
. We apologize that previously the HotStorage’26 Call for Papers pointed<br>
to an older version of the ACM template. If you used that version for<br>
your original submission, please update your camera-ready paper to<br>
version 2.19.<br>
<br>
- Title: The camera-ready paper title should contain only the paper’s<br>
actual title. Please do not include the submission type, such as<br>
"Regular" or "Position," in the camera-ready version.<br>
<br>
- Page limit: You can add one additional page to the camera-ready paper.<br>
<br>
- Metadata: Make sure to include the proper CCS Concepts, Keywords, and<br>
copyright information (see #2 below).<br>
<br>
<br>
2. Complete ACM eRights Form<br>
<br>
The authors should have received ACM eRights forms from a separate<br>
email. Please complete this form promptly and carefully; the title,<br>
author names, affiliations, and other metadata entered in eRights should<br>
be accurate and consistent with the camera-ready version. If you have<br>
not received this email, please let us know. *Authors whose forms are<br>
pending will be unable to upload their final papers.*<br>
<br>
The eRights form will require the ORCID of all authors. Authors who do<br>
not already have one should register at <a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fORCID.org&c=E,1,mfemALGW8Vp0ZVAWxZ5IhWNd9yLbfMXkd9YNjAko5k5DwxxYBljVrkoXyC4Jh8SL6Iur5Pypb0ZG71nuJIGtRlIxmmjEuD-a0DzlG0SfBX2RG0NySVghcg,,&typo=1&ancr_add=1">ORCID.org</a> first.<br>
<br>
After completing the eRights forms, the authors will be emailed the<br>
rights text (bibliographic strip, ISBN, DOI, etc.). Authors must include<br>
this text in their paper.<br>
<br>
As rights management emails are sent from an automated system, these may<br>
wind up in SPAM folders. Please make sure the SPAM filter allows emails<br>
from <a href="mailto:rightsreview@acm.org" target="_blank">rightsreview@acm.org</a>.<br>
<br>
<br>
3. Submit the final version through TAPS<br>
<br>
Final papers will be processed through The ACM Production System (TAPS).<br>
After authors complete their eRights forms, they will receive a separate<br>
email from TAPS within 12 hours. The TAPS email will contain<br>
instructions for uploading source, supplementary, and auxiliary files<br>
for processing. Please keep an eye on the emails from<br>
<a href="mailto:tapsadmin@aptaracorp.awsapps.com" target="_blank">tapsadmin@aptaracorp.awsapps.com</a><br>
<br>
You may find the detailed workflow with TAPS at<br>
<a href="https://urldefense.com/v3/__https://authors.acm.org/proceedings/production-information/taps-production-workflow__;!!Mak6IKo!L20nMz9GlzeLiaWpA4BngvuRYWLMzu_AOyecJ_XpqD2SgBUCma8Zd2SCx1i3dtHlNrhWZx5Mgi24-fb6x6LchA-5MXQAT3Y$" target="_blank">https://urldefense.com/v3/__https://authors.acm.org/proceedings/production-information/taps-production-workflow__;!!Mak6IKo!L20nMz9GlzeLiaWpA4BngvuRYWLMzu_AOyecJ_XpqD2SgBUCma8Zd2SCx1i3dtHlNrhWZx5Mgi24-fb6x6LchA-5MXQAT3Y$</a><br>
<br>
Best wishes,<br>
Chenhao Ye & Duo Zhang<br>
HotStorage’26 Publication Chairs<br>
</div>
</div>
</div>
</blockquote></div>