For authors

For both submitted and accepted papers, authors must use the new JFP LaTeX class file for Episciences (jfp-epi, available here, currently v1.2). The jfp-epi class is a thin skin over the actively maintained acmart class, but mimicking the visual style of the old JFP class. The LaTeX distribution includes detailed instructions on how to configure jfp-epi for drafts vs. final papers, as well as how to adapt papers written with acmart or the old JFP class to work with the new JFP class.

We impose only minimal style guidelines on submitted and accepted papers, mainly that sentence case (rather than title case) should be used for the title of the paper, as well as section and subsection headings and captions. The use of a particular citation style is not mandated. See the documentation accompanying the class file for details.

First, the submission needs to be uploaded to one of the following open repositories: arXiv, HAL, or Zenodo. Once you have done so, you can create a new JFP submission on Episciences by supplying us with the paper ID and version number of your paper from the corresponding repository.

If your paper is part of a special issue (e.g. extended versions of papers from a specific conference), then please be sure to indicate this on the submission page by selecting the appropriate entry where it says: "Submit in the volume".

If you are submitting a paper that is a special category of paper (e.g. functional pearls, editorials), then please be sure to indicate this on the submission page by selecting the appropriate entry where it says: "Submit in the section".

We expect draft papers to be compiled in "review" mode (the default): this inserts red line numbers into the document, which are very helpful for reviewers. Unfortunately, arXiv does not permit line numbers. Therefore, if you are using arXiv, you should produce two versions of your document. The first version, which you will upload to arXiv, should be compiled without line numbers by placing \documentclass[review=false]{jfp-epi} at the top of your main LaTeX file. The second version should be compiled with line numbers by placing \documentclass{jfp-epi} at the top of your main LaTeX file. For the time being, you can upload that second version directly to JFP/Episciences using the "Cover Letter" field when you submit. (If you want to also submit an actual cover letter, then please merge the cover letter with the line-numbered version of your submission into one PDF.)

If you have uploaded your submission to HAL, you can alternatively submit it to JFP/Episciences as described here, but you can also just follow the standard procedure.

Submission of a paper is taken to imply that it has not been previously published and that it is not being considered for publication elsewhere. Authors should inform the editor of any related papers submitted or published elsewhere.

ORCID provides a unique identifier for researchers and integration with key research workflows such as manuscript submission and grant applications. For accepted papers, all authors must identify themselves via ORCIDs, and include these ORCID links in the final version of the paper (resulting in the author names showing up as hyperlinks to the author's ORCID page). If you don’t already have an ID, you will need to create one. You can register for one directly via https://ORCID.org/register.

For submitted papers, ORCIDs are encouraged but not required.

Copyright for articles published in the Journal of Functional Programming is retained by the authors. Before publication of an accepted article, authors are required to assent to both a the Creative Commons CC-BY license (click here to read the full-text legal code) and also the agreement below with the journal. The Creative Commons license grants general rights to store, publish, distribute, access and make commercial use of the article. The agreement with the journal concerns corrections and republication.

The license was developed by Creative Commons to facilitate open access to, and free use of, original works of all types, and has been adopted by a growing group of authors and artists, as well as the Public Library of Science. Applying this standard license to your work will provide strong legal protection to you and those wishing to use your work, and thus ensure your right to make your work freely and openly available.

Agreement

1. This is an agreement between the Journal of Functional Programming (the "Journal"), and the copyright owner, or co-owner, (the "Owner") of a paper (the "Work") submitted to be published in the Journal.
2. The Owner warrants that s/he has the full power and authority to enter into this Agreement and to grant the rights granted in this Agreement and in the Creative Commons license hereunder. The Owner further warrants that all authors have been advised and have consented to the terms of this agreement and the Owner acts as duly authorized agent of the other authors.
3. The Owner agrees, if the Work is accepted for publication in the Journal, to have it covered by the Creative Commons CC-BY license given here.
4. The Owner agrees that no new version of the article, once it is published in the Journal, will be submitted to arXiv, HAL, or Zenodo without the agreement of the Journal. The Owner agrees to handle all changes or corrections via the assigned editor of their article in the Journal.
5. The Owner agrees that further publication of the Work, with the same or substantially the same content as appears in the Journal, will include an acknowledgment of prior publication in the Journal.

Acknowledgements: These policies are adapted with permission from the journal Logical Methods in Computer Science, whose steering committee we thank.