-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Proposal #1
Comments
CC @sylee957 @anutosh491. |
I would want to update the bio |
Thanks. You should add that to the bio on your profile at https://cfp.scipy.org/2023/me/, but I think we should also include the bios in the "additional information" section as there isn't any other section that asks about who will present (which is obviously an important thing for the reviewers to know). |
The submission deadline is coming up in a couple of weeks, so let's make sure we have something ready to go. I've moved the submission into a Google Doc to make it easier to edit. @sylee957 and @anutosh491 please feel free to edit the document directly https://docs.google.com/document/d/1qyCEOBGQzLkoZnJTNRW7wZB6czsvoLymRV2nA8DBWWQ/edit?usp=sharing. I've only given access to you two so if anyone else wants to review please let me know and I can give you access. For now I've just copied over the text from the 2020 proposal, but we should read through it and modify things. |
@sylee957 @anutosh491 let me know if you're able to take a look at this. The submission deadline is in a week. I plan to take a look today or tomorrow. If you'd like to have a meeting to discuss it let me know. |
I think that the tutorial proposal is fine.
We could discuss about the future to write down the materials assuming the
tutorial is accepted.
2023-02-16, 목 06:48, Aaron Meurer ***@***.***>님이 작성:
@sylee957 <https://github.com/sylee957> @anutosh491
<https://github.com/anutosh491> let me know if you're able to take a look
at this. The submission deadline is in a week. I plan to take a look today
or tomorrow. If you'd like to have a meeting to discuss it let me know.
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIKTPTPFI5HF6FANCRXGPT3WXVFJLANCNFSM6AAAAAATXFADVE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
S.Y. Lee
|
FYI the proposal deadline was extended to March 1. |
I have edited the draft a bit, and submitted it. We can still edit it up to the deadline, so if you want to make any modifications, please let me know so I can update the submission. In particular I added the following to the notes section, since there is no other place in the submission to indicate who the co-presenters are:
@sylee957 @anutosh491 if you want to add something there about yourself, especially about your SymPy expertise, and any prior teaching experience you may have, please do (but again, if you edit the Google doc please ping me either here or in the doc so I know to update the submission). |
Hello Aaron , I read the proposal throughly a couple days back and it looked good to me . I would go through it once again by today and see if there any necessary edits to be made . |
Here is the proposal we used in 2020. It was accepted, but was later cancelled when the conference changed to online-only. I also have the review comments but I don't know if those can be shared publicly, so I will email them to the folks who are planning to co-present.
The deadline to submit the proposal this year is Feb 22. https://www.scipy2023.scipy.org/present
Abstract:
Tutorial Description
Tutorial Outline
Additional Tutorial Information
It looks like the questions for this year are basically the same.
The text was updated successfully, but these errors were encountered: