Update spec.html

Author: lawrennd

spec.html

@@ -7,15 +7,22 @@
   <div id="wrapper">
     <h1 id="jmlr-wcp-proceedings-specification">PMLR Proceedings Specification</h1>
 
-    <p><em>Version 1.23 – Jun 28th, 2022</em></p>
+    <p><em>Version 1.3 – Jul 27th, 2025</em></p>
 
-    <p>To publish a proceedings with PMLR, the organisers will need to provide the editors with:</p>
+    <p>Once the proceedings is accepted you'll be provided with agithub repository where you will upload the pdfs and the bibtex.</p>
+
+    <p>The proceedings repo will be derived on this <a href="https://github.com/mlresearch/proceedings-template/">this template</a>.</p>
+
+    <p>You shouild <a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo">fork the proceedings</a> and add the files specified below. When the files are ready you can submit a pull request.</p>
+    
+    <p>Your forked proceedings should include:</p>
 
     <ol style="list-style-type: decimal">
       <li>A BibTeX file (described below) with the details of each paper in the proceedings.</li>
       <li>A collection of PDF files (and, optionally, supplementary files).</li>
     </ol>
 
+    <p>When you submit pull request you will be asked to fill in <a href="https://github.com/mlresearch/proceedings-template/blob/main/.github/pull_request_template.md">this check list.</p>
     <p>The following specification is for simple conference proceedings that consist of one or more papers that are to be displayed in page order with links to associated PDF and supplementary files. If you need any clarifications, or need to publish proceedings with special sections, awards, multiple cycles, or other features, please email <a href="javascript:GoAddress('proceedings','mlr.press');">proceedings<img src=/assets/images/atr.gif border=0>mlr.press</a></p>
 
     <h3 id="the-bibtex-file">The BibTeX file</h3>
@@ -182,10 +189,6 @@ <h3 id="video-links">Video Availability</h3>
 <div class="footnotes">
 <hr />
 
-<ol>
-  <li id="fn1"><p>Note: gzipped tarballs are not the only way you can send material. For larger conferences, we recommend sharing a Dropbox directory or otherwise putting the files up on a server we can have access to.<a href="#fnref1">↩</a></p></li>       
-      
-</ol>
 </div>
 
     </div>