SciPy Proceedings

This is the repository for submitting to and managing the Proceedings for the
Annual Scientific Computing with Python Conference.
This repository is a home for authors, reviewers and editors to collaboratively
create the proceedings for the conference.
You can find more information about the proceedings’ organising principles below.
All communication between authors and reviewers should be civil and
respectful. There are no exceptions to this rule. Please see the
SciPy2022 Code of Conduct
for more info.
You can find the schedule for 2022 below.
Please use @-mentions in issues and pull requests(PRs) to contact the proceedings Co-Chairs.
If you are an Author, please see Instructions for Authors.
If you are a Reviewer, please see Instructions for Reviewers.
If you are an Editor, please see Instructions for Editors.
If you are a Publisher, please see Instructions for Publishers.
If you are Submitting Slides, please see Instructions for Slides.

Organising Principles: Openness

Overall, the SciPy proceedings are organised to be a fully open proceedings.
We aim to combine the best aspects of open source development, open peer review,
and open access publication.

Built by and for Open Source Communities on Open Source Tech

The technologies used for running the conference are themselves developed in the
open and built on open source tools.
Open Development:

with many people contributing code over more than a decade
- many contributors start as authors submitting to the proceedings
- provides a natural pathway for new members to join the proceedings committee
technologies are managed via public, open source GitHub repositories:
- build system: https://github.com/scipy-conference/scipy_proceedings
- server: https://github.com/scipy-conference/procbuild

The systems for running the conference are built on top of open source tools:

build system:
- LaTeX
- ReStructured Text (reST)
- Python: docutils, lxml, pygments, pytest
server:
- Flask & waitress
- pyzmq
- Docker
- Python: asyncio

Open Peer Review meets Open Source Code Review

The entire submission and review procedure occurs through public PRs attached to
identifiable individuals.

Authors and reviewers are encouraged to work collaboratively to improve
submissions throughout the review process, much like open source code-review.
Reviews are collaborative, aiming to improve the publication quality. This is
possible because the content was already vetted by the program committee.
Conversations occur attached to people’s real GitHub usernames and are open to
the public.
- This allows for a transparent open review process.
- This holds authors and reviewers accountable and encourages civil communication practices.

Open Access for an Open Community

The papers are published as true Open Access (OA) articles with Creative Commons
Attribution (CC By) license.

There are no article processing charges barring authors from submitting papers.
- Reviewers and co-chairs volunteer their time.
- Services with free tiers (like GitHub and Heroku) allow distributing the
  underlying technologies with minimal cost.
Papers are openly available at http://conference.scipy.org/proceedings/, with
no pay walls barring consumption or author processing charges.
From 2010 onward, papers have DOIs (making them easily citable) and are also
openly available from those DOIs.

The community is involved in the entire process for creating the proceedings,
which ensures relevance to the community that created them.

Papers are submitted by authors who will be presenting talks and posters at the
annual SciPy conference. Because we know the content is relevant to the SciPy
community, review can focus on improving papers, not vetting them.
Reviewers are invited by the editors, but community members may volunteer to
review papers that interest them. The only barrier to participation is having
a GitHub account.

Contacting the Proceedings Co-Chairs

The most effective way to contact the Proceedings Co-Chairs for issues related to this GitHub repository is to use GitHub’s issues and “@”-mentioning the Co-Chairs.
In 2022, the Proceedings Co-Chairs are

Meghann Agarwal (@mepa)
Chris Calloway (@cbcunc)
Dillon Niederhut (@deniederhut)
David Shupe (@stargaser)

Timeline for 2022

In addition to the following list, we break up the deadlines in the respective documents for authors and reviewers.

April 5: Authors invited to submit full papers
May 27: 1st Draft for Submission
May 27–June 23: Open Review Period
May 27: Reviewers Assigned
June 16: Initial Complete Review
June 30: Final Recommendation and Comprehensive Review Deadlines
July 4: Final Author Revision Deadline
July 6: Final Editorial Decisions for Proceedings Contents Deadline
July 30: Time Window for Publishing Conference Ready Proceedings

Instructions for Authors

Please submit your papers by 23:59 PST of the 1st Draft for Submission
Deadline.
Submit your papers as an ReStructured Text file via PR against this repository.
During the Open Review Period authors should work with their reviewers to refine
and improve their submission.
Proceedings Co-Chairs have final say in determining whether a paper is to be
accepted to the proceedings.
Authors should respond to all the reviewers’ comments.
Authors should default to modifying their papers in response to reviewers’
comments.
Authors may not agree with the reviewers comments or may not wish to implement
the suggested changes. In those cases, the authors and reviewers should
attempt to discuss this in the PR’s comment sections. It is important to
remember in these cases that we expect all communication between authors and
reviewers to be civil and respectful.
In the event that authors and reviewers are deadlocked, they should alert the
Proceedings Co-Chairs to this situation. As always, the Proceedings Co-Chairs
have final say in whether to accept or reject a paper.

Author Deadlines

April 5: Authors invited to submit full papers
May 27: 1st Draft for Submission
May 27–June 30: Open Review Period
July 4: Final Author Revision Deadline
July 6: Final Editorial Decisions for Proceedings Contents Deadline

General Information and Guidelines for Authors:

Papers are formatted using reStructuredText.
Example papers are provided in papers/00_bibderwalt and papers/00_vanderwalt.
- These papers provide examples of how to:
  - Label figures, equations and tables
  - Use math markup
  - Include code snippets
- For your paper to be found by the build system at http://procbuild.scipy.org
  your PR needs to have a title that begins with “Paper:”. If you do not do
  this, the co-chairs will change your title on your behalf.
- Authors may include a project or consortium (e.g. The Jupyter Project)
- There must be at least one corresponding author, and this must be a specific person with a valid email address
- Authors of papers from previous SciPys may change their name on their published work by contacting the Proceedings Co-chairs
- All citations that have DOIs should include those DOIs in the paper’s
  references section, see mybib.bib.
- All figures and tables should have captions.
- Figures and tables should be positioned inline, close to their explanatory text.
- License conditions on images and figures must be respected (Creative Commons,
  etc.).
- Images and figures should be reasonably sized and formatted for viewing online; typically a few hundred kilobytes and less than 1 MB.
- Code snippets should be formatted to fit inside a single column without
  overflow.
- Avoid custom LaTeX markup where possible.
- Do not modify any files outside of your paper directory.
- The compiled version of the paper (PDF) should be at most 8 pages,
  including figures but not including references.
Author Workflow

Below we outline the steps to submit a paper.
Before you begin, you should have a GitHub account. If we refer to <username>
in code examples, you should replace that with your GitHub username.
More generally, angle…