Version 1.3 – Jul 27th, 2025 Once the proceedings is accepted you'll be provided with a github repository where you will upload the pdfs and the bibtex. The proceedings repo will be derived from this template . You should fork the proceedings and add the files specified below. When the files are ready you can submit a pull request. Your forked proceedings should include: A BibTeX file (described below) with the details of each paper in the proceedings. A collection of PDF files (and, optionally, supplementary files). When you submit pull request you will be asked to fill in this check list. 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 proceedings mlr.press The BibTeX file In titles and author names, please use Latex commands for representing special characters (such as \'e for an acute accent on e . For mathematics use standard latex inside two $ marks, e.g. $\int_{x=1}^z x^2 \text{d}x$. Note : The contents of each field must be valid BibTeX (i.e., make sure characters are escaped correctly) . All of the conference and paper details are contained in a single BibTeX file. You can name it whatever you like but we suggest you use some association with the conference name (e.g., icml13.bib ) There are two types of entry that must appear in the BibTeX file: There must be a single @Proceedings entry with the conference details. It must include the following fields: booktitle : the citation to the volume (e.g. Proceedings of the Twenty First International Conference on Machine Learning) name : the long name of the conference (e.g. International Conference on Machine Learning) shortname the abbreviation for the conference (without the year, e.g., ICML) year : the year of the conference (e.g., 2013) editor : the editors’ names (in “Lastname, Firstnames” format, separated by “and”) volume : the PMLR number assigned to your conference/workshop start : the first day of the conference/workshop in YYYY-MM-DD format. end : the last day of the conference/workshop in YYYY-MM-DD format. address : the location of the conference in venue, city, country format. conference_url : the URL of the conference website. conference_number : if the conference is part of a series, give the number in the series here. Other fields may be present in the @Proceedings entry but these will be ignored at present. booktitle : the citation to the volume (e.g. Proceedings of the Twenty First International Conference on Machine Learning) name : the long name of the conference (e.g. International Conference on Machine Learning) shortname the abbreviation for the conference (without the year, e.g., ICML) year : the year of the conference (e.g., 2013) editor : the editors’ names (in “Lastname, Firstnames” format, separated by “and”) volume : the PMLR number assigned to your conference/workshop start : the first day of the conference/workshop in YYYY-MM-DD format. end : the last day of the conference/workshop in YYYY-MM-DD format. address : the location of the conference in venue, city, country format. conference_url : the URL of the conference website. conference_number : if the conference is part of a series, give the number in the series here. Other fields may be present in the @Proceedings entry but these will be ignored at present. There must be at one @InProceedings entry for each paper. Each entry must have the following fields: title : The title of the paper author : The paper’s authors in “Lastname, Firstnames” format, separated by “and”. Do not use unicode characters, use the LaTeX equivalents. pages : The page numbers in “startpage–endpage” format abstract : The paper’s abstract. It can include maths in valid LaTeX. Make sure there are no special characters in the abstract, such as those arising from copying and pasting ligatures from the pdf. You can use <em> tags for emphasis. You can use <b> for bold. You can use <ul> tags for bullets. You can use <ol> for numerated lists. Other fields may also appear in the @InProceedings entries but these will be ignored at present. title : The title of the paper

author : The paper’s authors in “Lastname, Firstnames” format, separated by “and”. Do not use unicode characters, use the LaTeX equivalents. pages : The page numbers in “startpage–endpage” format abstract : The paper’s abstract. It can include maths in valid LaTeX. Make sure there are no special characters in the abstract, such as those arising from copying and pasting ligatures from the pdf. You can use <em> tags for emphasis. You can use <b> for bold. You can use <ul> tags for bullets. You can use <ol> for numerated lists. It can include maths in valid LaTeX. Make sure there are no special characters in the abstract, such as those arising from copying and pasting ligatures from the pdf. You can use <em> tags for emphasis. You can use <b> for bold. You can use <ul> tags for bullets. You can use <ol> for numerated lists. Other fields may also appear in the @InProceedings entries but these will be ignored at present. The identifiers should be in the form lastnameYY where lastname is the lowercase last name of the first author and YY is the last two digits of the year of the conference. If two papers share the same identifier under this scheme, they must be disambiguated by appending one of a , b , c , etc. to the conflicting identifiers (e.g., reid12a and reid12b ). Please do not use UTF-8 charcters in these names (or the file names). ASCII only. The Papers and Supplementary Material The paper PDFs must have a filename corresponding to the identifier of its BibTeX entry. For example, the PDF for the reid12a entry must have filename reid12a.pdf . These should all appear in the same directory as the BibTeX file describing all the entries. Make sure all supplementary filenames for a paper with ID lastnameYY begin with the same ID but end with the suffix -supp (e.g., The PDF supplementary should be named lastnameYY-supp.pdf ). These should appear in the same directory as the BibTeX file you provide us. Use whichever file extension is most appropriate (e.g., .pdf for PDF files) Please do not provide a single zipped file with supplementary material in it. This provides a poor experience for the user. For software and video see sections below on Software and videos . For example, suppose the paper with identifier reid12b had a supplementary PDF file with proofs. You should give us a file named reid12b-supp.pdf . The generated site for the reid12b entry will contain a link titled supplementary to the files reid12b-supp.pdf . Sample BibTeX file and papers Below is a sample of a BibTeX file for the 2nd International Conference on Examples (ICE’13) in 2013. It has been given volume number 57 and is edited by Jane Smith and Joe Bloggs. It contains three papers. It was provided as part of a gzipped tarball 1 ice13.tar.gz along with the PDF and supplementary files. The contents of the tarball is: ice13.bib (The BibTeX file below) jones13a-supp.pdf (Supplementary proofs for jones13a ) The content of the BibTeX file ice13.bib is: Sectioned Proceedings We also support publishing in sections. To publish your proceedings in sections, add the following field to the proccedings bibtex entry. And then to each bibtex entry add a field defining the section e.g. If you reviewed your proceedings using openreview, then you might like to have the reviews linked to from the proceedings. If you require this, you need to add a section to each bib entry specifying the openreview code. e.g. Software Availability Many papers have associated code provided. You can provide a link to a url that specifies the code. If you require this, you need to add a section to each bib entry specifying the openreview code. e.g. Video Availability Please don't send videos as supplementary material. Instead you can provide a link to a url that specifies the video location. If you require this, you need to add a section to each bib entry specifying the openreview code. e.g.