[Rprotobuf-commits] r939 - papers/jss
noreply at r-forge.r-project.org
noreply at r-forge.r-project.org
Mon Apr 13 02:07:19 CEST 2015
Author: edd
Date: 2015-04-13 02:07:19 +0200 (Mon, 13 Apr 2015)
New Revision: 939
Added:
papers/jss/conditional-acceptance-email-2015-04.txt
papers/jss/conditional-acceptance-notes-2015-04.txt
Log:
replies from JSS and TODOs for finalizing, with my notes in notes.txt
Added: papers/jss/conditional-acceptance-email-2015-04.txt
===================================================================
--- papers/jss/conditional-acceptance-email-2015-04.txt (rev 0)
+++ papers/jss/conditional-acceptance-email-2015-04.txt 2015-04-13 00:07:19 UTC (rev 939)
@@ -0,0 +1,61 @@
+From: Editor of the Journal of Statistical Software <editor at jstatsoft.org>
+To: "edd at debian.org" <edd at debian.org>
+Subject: JSS 1313 Conditional Acceptance
+Date: Mon, 6 Apr 2015 19:30:32 +0000
+
+Dear author,
+
+Your submission
+
+ JSS 1313
+
+is conditionally accepted for publication in JSS.
+
+Your manuscript has just finished the post-processing stage. In order to
+continue in the process there are a few changes that need to be made. Attached
+to this email is a comments file where you can find all the necessary changes.
+
+For further questions please see FAQ at http://www.jstatsoft.org/style.
+
+
+Please send the full sources for your submission to the technical editor (
+editor at jstatsoft.org). It should contain:
+
+
+ 1. The full sources of the latest version of the software. (Binary versions
+ can be provided in addition.)
+ 2. The .tex, .bib, and all graphics for the manuscript: where the names of
+ your files should be - your .tex file should be called jssxxx.tex and your
+ .bib file should be called jssxxx.bib. As well as a complied .pdf version
+ of your manuscript.
+ 3. Information on how to replicate the examples in the manuscript. (Typically,
+ this is a self-contained standalone script file that loads/calls/sources
+ the software package from (1). If data or other external files are needed,
+ that are not yet provided with the software package, include these as
+ well.) Please use subdirectories for Figures/ and Code/
+ 4. Please wrap all these files into a single .zip (or .tar.gz) file.
+ 5. Please make sure the .zip files only contains the necessary files. That is,
+ please do not include .aux, .log, etc. files and any unused files such
+ as jss.cls, jss.bst, jsslogo.jpg, etc.
+
+
+Note for R authors: If you have prepared your manuscript using Sweave, the
+files in (2) can be produced by Sweave, those in (3) by Stangle (possibly
+enhancing the comments). Also indicate in your e-mail that Sweave was used and
+the technical editor will provide you with further Sweave-specific information.
+
+Thanks for choosing JSS and contributing to free statistical software.
+
+Best regards,
+
+Jan de Leeuw
+Bettina Grün
+Achim Zeileis
+
+
+
+
+
+
+----------------------------------------------------------------------
+xplain text (us-ascii): JSS 1313 post comments.txt, JSS 1313 [display]
Added: papers/jss/conditional-acceptance-notes-2015-04.txt
===================================================================
--- papers/jss/conditional-acceptance-notes-2015-04.txt (rev 0)
+++ papers/jss/conditional-acceptance-notes-2015-04.txt 2015-04-13 00:07:19 UTC (rev 939)
@@ -0,0 +1,85 @@
+JSS 1313: Eddelbuettel, Stokely, Ooms
+
+RProtoBuf: Efficient Cross-Language Data Serialization in R
+
+---------------------------------------------------------
+For further instruction on JSS style requirements please see the JSS style manual (in particular section 2.1 Style Checklist) at http://www.jstatsoft.org/downloads/JSSstyle.zip
+
+ ## START DEdd: Inserted per copy/paste from jss.pdf:
+
+ 2.1 Style checklist
+
+ A quick check for the most important aspects of the JSS style is given
+ below. Authors should make sure that all of them are addressed in the final
+ version. More details can be found in the remainder of this manual.
+ • The manuscript can be compiled by pdfLATEX.
+ • \proglang, \pkg and \code have been used for highlighting throughout the paper
+ (including titles and references), except where explicitly escaped.
+ • References are provided in a .bib BibTEX database and included in the text by \cite,
+ \citep, \citet, etc.
+ • Titles and headers are formatted properly:
+ – \title in title style,
+ – \section etc. in sentence style,
+ – all titles in the BibTEX file in title style.
+ • Figures, tables and equations are marked with a \label and referred to by \ref, e.g.,
+ “Figure~\ref{...}”.
+ • Software packages are \cite{}d properly.
+
+ ## END DEdd: Inserted per copy/paste from jss.pdf:
+
+Also see FAQ at: http://www.jstatsoft.org/style
+
+For further references please see RECENT JSS papers for detailed documentation and examples.
+---------------------------------------------------------
+
+
+From the editorial team:
+
+o From one reviewer: As far as I can see there's only one difference between
+the two columns of Table 3. It would be nice to highlight this.
+
+ ## DEdd: Done, added a sentence below table and tightened wording in that
+ Table note.
+
+
+Manuscript style comments:
+
+o Code should have enough spaces to facilitate reading. Please include spaces before and after operators and after commas (unless spaces have syntactical meaning).
+
+ ## DEdd: No change, we were good already
+
+o The table in Figure 2 should have row/column labels in sentence
+style. (Only the first word of a label should be capitalized).
+
+ ## DEdd: Done (not sure I like it better)
+
+o In all cases, code input/output must fit within the normal text width of the manuscript. Thus, code input should have appropriate line breaks and code output should preferably be generated with a suitable width (or otherwise edited). E.g., see p. 9.
+
+ ## DEdd: Replaces the Sweave code with its latex output and manually broke the long line
+
+o For bullet lists/itemized lists please use either a comma, semi-colon, or period at the end of each item.
+
+ ## DEdd: Done; one small change
+
+o As a reminder, please make sure that:
+ - \proglang, \pkg and \code have been used for highlighting throughout the paper (including titles and references), except where explicitly escaped.
+
+
+References:
+
+o John Wiley & Sons (not: Wiley, John Wiley & Sons Inc.)
+
+ ## DEdd We only had one 'Wiley' where I removed a stray ".com"
+
+o As a reminder,
+ - Please make sure that all software packages are \cite{}'d properly.
+
+ - All references should be in title style.
+
+ - See FAQ for specific reference instructions.
+
+ ## DEdd Update bibliography to current version numbers, and title styled
+
+Code:
+
+o As a reminder, please make sure that the files needed to replicate all code/examples within the manuscript are included in a standalone replication script.
More information about the Rprotobuf-commits
mailing list