Final Paper Submissions

Instructions to Upload Proceedings’ Version

Submissions Due by February 1st 2017

Please upload your final version into the submission system following the link below.

Use the same username/password from the original submission:

http://hillside.net/sugarloafplop/2016/submission

Template and Copyright Notice

Templates to create your camera-ready copy for the proceedings are available in Word and LaTeX, otherwise ACM might not accept the paper for the digital library.

The recommended template is ACM’s single column format customized for SugarLoafPLoP. An example with SL-PLoP’s copyright notice can be found in this PDF, and the template is provided here:

• Single column format Word template
• Single column format TeX template

Note: Use the following ACM Classification for Categories and Terms ACM Classification

Please use the following text as the copyright notice on the first page.

Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. A preliminary version of this paper was presented in a writers’ workshop at the 11th Latin American Conference on Pattern Languages of Programs (SugarLoafPLoP). SugarLoafPLoP’16, November 16th – 18th, 2016, Buenos Aires, Argentina. Copyright 2016 is held by the author(s). HILLSIDE 978-1-941652-05-3

Alternatively, ACM’s two-column template will also be accepted. In this case, it is of particular importance that you leave sufficient space in the lower left corner of the first column on the first page, to insert the copyright information.

PDF Creation Guidelines

Please produce a camera-ready PDF version (using on a high-resolution output device) of your paper on letter paper size (8 1/2″ x 11″) following the proceedings format above.

Papers should have Type 1 fonts (scalable), not Type 3 (bit-mapped). All fonts MUST be embedded within the PDF file. Any PDF that is not deposited with fonts embedded will need to be corrected. In order to help you through this process, the ACM have created documentation on how to embed your fonts. You will need the ACM Digital Library optimal distiller settings file, ACM.joboptions.

For those creating their PDF using Word’s Save to PDF feature, you need to change one option to embed the fonts. On the Save to PDF dialog, click the “Options” button and check the ISO 19005-1 compliant box. Once done, be sure to check that the fonts are indeed embedded per the instructions on the ACM download file above.

Permission / Release Form

Authors maintain full permission and ownership of their papers in order to do with them as they please. Therefore, for each paper reviewed in the Writers’ Workshops, at least one author must sign the attached Permission / Release form, filling in the details as follows:

If you are signing for your co-authors, please circle the phrase “one agent signs for all co-authors.” at the bottom of the form. Please also mark all permissions you grant: to publish your work in the Hillside standard proceedings, to additionally publish it on the Hillside website (as part of a future repository, still work in progress), and permission for hosting and indexing it in the ACM Digital Library or an equivalent archive.

Download the Permission Release Form

File Naming Guidelines

1. All file names for papers must take the form: <last_name_of_first_author>.pdf
   For example: smith.pdf

   If the first author has more than one submission, add the suffixes -1, -2, etc.
   For example: smith-1.pdf and smith-2.pdf

   For the permission release form add the suffix -releaseform
   For example: smith-releaseform.pdf and smith-2-releaseform.pdf

2. Use lowercase throughout file names — DO *NOT* CAPITALIZE.

3. There are rules for special names.

   1. a hyphenated last name remains hyphenated e.g., Wu Yen-Tse —–> yen-tse

   2. a compound last name takes an underscore e.g., Robert van Gulik —–> van_gulik

   3. accents in last names are omitted e.g., Wolfgang Schr<o with umlaut>der —–> schroder (NOT schroeder)
      or Jean Ren<e with acute> —–> rene (NOT renee)

   4. apostrophes in last names are replaced by an underscore e.g., Elizabeth O’Neill —–> o_neilll

   5. retain periods after abbreviated name elements e.g., Melissa St. Thomas —–> st._thomas

   6. drop suffixes from file names e.g. Corbin Jones Jr. —–> jones

   7. middle names are not used in the filenames; there may be cases that are ambiguous, and you’ll have to decide wether a word is a middle name or a piece of the last name. For example: Jose Perez Garcia —–> perez_garcia