Workshop organizing guide #489
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@IshaanDesai @carme-hp have I forgotten anything regarding the fields we typically add in the registration and abstract submission forms? |
|
uekerman
requested changes
Jan 20, 2025
Comment on lines
+46
to
+47
| - title: Organizing | ||
| url: /precice-workshop-organization.html |
There was a problem hiding this comment.
Suggested change
| - title: Organizing | |
| url: /precice-workshop-organization.html | |
| - title: Organizing | |
| url: /precice-workshop-organizing.html |
For consistency?
|
|
||
| - "save the date" announcement: one year ahead | ||
| - call for contributions (needs a form): open six months ahead. An early call mainly acts as advertisement. | ||
| - open registration (needs a form): six months ahead. Early registration is important for participants that need a visa application to travel. |
There was a problem hiding this comment.
Sounds too early to me. Of course, early does not hurt. Visa application should only depend on the contribution, not on the registration, no?
| - "save the date" announcement: one year ahead | ||
| - call for contributions (needs a form): open six months ahead. An early call mainly acts as advertisement. | ||
| - open registration (needs a form): six months ahead. Early registration is important for participants that need a visa application to travel. | ||
| - abstract submission deadline and call acceptance: the earlier the better. Can be after the early-bird registration deadline. The call acceptance can be as short as one week after the deadline. |
There was a problem hiding this comment.
Why after the early-bird registration deadline? Should be before, no?
| - abstract submission deadline and call acceptance: the earlier the better. Can be after the early-bird registration deadline. The call acceptance can be as short as one week after the deadline. | ||
| - early-bird registration deadline: important for estimating the number of participants, driven by the catering requirements. | ||
| - request catering offers: typically 1-2 months before the workshop. | ||
| - reserve tables for the workshop dinner: typically 1-2 months before the workshop. |
There was a problem hiding this comment.
Suggested change
| - reserve tables for the workshop dinner: typically 1-2 months before the workshop. | |
| - reserve tables for the workshop dinner: typically 3-4 months before the workshop. |
uekerman
reviewed
Jan 20, 2025
| The abstract submission form should collect: | ||
|
|
||
| - Kind of contribution (talk or poster, if offered) | ||
| - Presenter |
There was a problem hiding this comment.
Suggested change
| - Presenter | |
| - Presenter | |
| - Authors |
There was a problem hiding this comment.
I am not sure if we have collected the list of authors in the past.
On the one hand, it would help us identify where the contribution comes from.
On the other hand, it might be an obstacle to people that first need to discuss a seemingly final authors list (depends on the local culture).
I would suggest having an explicit note next to it:
Suggested change
| - Presenter | |
| - Presenter | |
| - Authors (with the note: "preliminary list, can be modified later") |
uekerman
reviewed
Jan 20, 2025
Co-authored-by: Benjamin Uekermann <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>
Co-authored-by: Benjamin Uekermann <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I thought that such a guide would be useful, especially now that we are organizing a workshop together with collaborators that experience this for the first time.
This is a first draft, we will need to add a lot more.