Skip to content

Commit

Permalink
Merge pull request #895 from mepa/2024-author-invitation
Browse files Browse the repository at this point in the history
Update author invitation email template for 2024
  • Loading branch information
mepa committed Apr 26, 2024
2 parents 18b20b2 + 99bfef8 commit 82a60c3
Showing 1 changed file with 18 additions and 8 deletions.
26 changes: 18 additions & 8 deletions publisher/mail/templates/author-invitation.txt.tmpl
Original file line number Diff line number Diff line change
@@ -1,24 +1,34 @@
Dear {{to_name}},
Dear @firstname @lastname,

Congratulations on having your abstract, "{{title}}", accepted for this year's event -- we look forward to seeing your poster or presentation! As in the past, {{proceedings['title']['acronym']}} {{proceedings['year']}} will release a conference proceedings prior to the start of the conference, and you are invited to contribute a full-length paper (up to 8 pages, not including references) expanding on your abstract.
Congratulations on having your abstract, "@title" accepted for this year's event -- we look forward to seeing your poster or presentation! As in the past, SciPy 2024 will release a conference proceedings after the end of the conference, and you are invited to contribute a full-length paper (up to 6000 words (about 8 pages), not including references) expanding on your abstract. Note: this is optional and not required for you to present at the conference.

The proceedings are aimed at highlighting significant contributions to scientific computing in Python, including but not limited to:
- methods for high performance computing in Python
- data-driven algorithms and products created with Python
- domain-specific applications of Python in any field of research
- significant improvements to existing scientific Python packages

Papers must be submitted as pull requests via GitHub by May 28th, 2020. At that point, the five-week open review period will begin. During this time, members from the proceedings committee and the scientific Python community at large will provide feedback, which should be addressed through discussion on GitHub and by updating the pull request. Further instructions can be found here:
Papers must be submitted as pull requests via GitHub by May 31st, 2024. At that point, the eight-week open review period will begin. Papers must be complete before they are submitted (e.g. no missing or half-written sections). During this time, members from the proceedings committee and the scientific Python community at large will provide feedback, which should be addressed through discussion on GitHub and by updating the pull request. Further instructions can be found here:
https://github.com/scipy-conference/scipy_proceedings#instructions-for-authors

A webinar with walkthrough and Q&A on how to submit to the proceedings will be offered on May 3rd, 2024. Sign up can be found here:
https://www.eventbrite.ca/e/scipy-proceedings-2024-quickstart-and-authoring-tutorial-tickets-876683101757

When submitting a paper to the proceedings, you may be contacted by the Proceedings Chairs to assist in reviewing other papers.

After the conference, you will have the opportunity to submit electronic copies of your poster or talk slides for archiving with {{proceedings['title']['acronym']}}. Further information about submitting slides and posters can be found here: https://github.com/scipy-conference/scipy_proceedings#instructions-for-slides
After the conference has ended, you will have the opportunity to submit electronic copies of your poster or talk slides for archiving with SciPy. Further information about submitting slides and posters can be found here: https://github.com/scipy-conference/scipy_proceedings#instructions-for-slides

Yours,
The {{proceedings['title']['acronym']}} {{proceedings['year']}} Proceedings Committee
{{for n in proceedings['editor']}}
{{n}}
{{endfor}}
The SciPy 2024 Proceedings Committee
Co-chairs / Editors:
Meghann Agarwal
Amey Ambade
Chris Calloway
Rowan Cockett
Sanhita Joshi
Charles Lindsey
Hongsup Shin
--
Unsubscribe


0 comments on commit 82a60c3

Please sign in to comment.