Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define Format for Submissions #13

Closed
katyhuff opened this issue Nov 7, 2013 · 3 comments
Closed

Define Format for Submissions #13

katyhuff opened this issue Nov 7, 2013 · 3 comments

Comments

@katyhuff
Copy link
Member

katyhuff commented Nov 7, 2013

Before you make the announcement about the call for abstracts and papers, you need to define the requirements for the submission format for the abstracts.

Additionally, it is usually also good to be ready at the same time with information about the format and submission process for the papers that will eventually go in the proceedings.

Last year the abstracts had the following requirements :

"""
The 150-300 word abstract should concisely describe software of interest to the SciPy community, tools or techniques for more effective computing, or how scientific Python was applied to solve a research problem. A traditional background/motivation, methods, results, and conclusion structure is encouraged but not required. Links to project websites, source code repositories, figures, full papers, and evidence of public speaking ability are encouraged.

Each abstract will be peer-reviewed by multiple members of the Program Committee Board. Please submit your abstract at the SciPy 2013 website [2] abstract submission form. Abstracts will be accepted for posters or presentations.
"""

@ghost ghost assigned katyhuff Nov 7, 2013
@jaberg
Copy link

jaberg commented Jan 17, 2014

The first paragraph suggests that abstracts themselves (e.g. 150 - 300 words) should have all the sections of a full paper -- is that the intent?

The second paragraph uses "peer-review" in a non-standard way. To me, review by program committee is a non-peer-review approach. Maybe "Abstracts will be reviewed by the Program Committee Board" would be clearer?

Also, @stefanv and I are still not quite ready with the exact protocol for turning abstracts into papers. I think we can say that the authors of accepted abstracts are invited to submit full papers by DATE which will be subject to a peer review process, and published on the conference web page and within the proceedings of SciPy2014. Details of the submission and review process will follow at LINK.

@katyhuff
Copy link
Member Author

Yes, they should have the aspects of a full paper.

We should definitely change peer-review to "will be reviewed by..."

The preliminary protocol description that you describe is fine. Indeed, the last sentence isn't even necessary at this stage. ("Details of the submission and review process will follow at LINK." can wait until we invite folks, if you need more time)

@katyhuff
Copy link
Member Author

katyhuff commented May 9, 2017

closing for age. Handled in 2014.

@katyhuff katyhuff closed this as completed May 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants