Skip to content

Add details on workshop contributions#360

Merged
carme-hp merged 4 commits intomasterfrom
carme-hp-patch-1
Mar 25, 2024
Merged

Add details on workshop contributions#360
carme-hp merged 4 commits intomasterfrom
carme-hp-patch-1

Conversation

@carme-hp
Copy link
Copy Markdown
Member

I have added some more description to explain what kind of contributions to the workshop are expected (as requested by
@uekerman) . I copied the text from last year and I adapted it a bit.

Copy link
Copy Markdown
Member

@MakisH MakisH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think what is missing here is to guide people what is better suited for a talk, and what is better suited for a poster.

We previously encouraged people to only contribute a talk if it is of wider interest (e.g., new adapter or field of application). But I think it would be nice to see more applications or updates on previously presented projects, for which a poster would be better, as you can directly discuss with the person if you are interested, or skip if not.

@carme-hp
Copy link
Copy Markdown
Member Author

Fair point. I tried to make a distinction now.

You do not need to submit a contribution to join this workshop. However, your contributions are very welcome! We are looking for talks and posters that could be beneficial for the wider preCICE community. Are you developing a new adapter? Are you using preCICE for an exciting new application? Are you developing new methods that should not be missing from preCICE? If the answer to any of these questions was yes, we encourage you to submit a brief abstract for a 20 minutes talk and/or a poster.
You do not need to submit a contribution to join this workshop. However, your contributions are very welcome! We are looking for talks and posters that could be beneficial for the wider preCICE community. Are you developing a new adapter? Are you using preCICE for an exciting new application? Are you developing new methods that should not be missing from preCICE? If the answer to any of these questions was yes, we encourage you to submit a brief abstract for a 20 minutes talk.

Are you revisiting one of the classical preCICE use cases? Did you already presented your work in a previous workshop? Then we would be very happy to catch up with your work and we encourage you to present a poster on the workshop.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Are you revisiting one of the classical preCICE use cases? Did you already presented your work in a previous workshop? Then we would be very happy to catch up with your work and we encourage you to present a poster on the workshop.
Are you revisiting one of the classical preCICE use cases? Did you already present your work in a previous workshop? Then we would be very happy to catch up with your work and we encourage you to present a poster on the workshop.

@carme-hp carme-hp merged commit cae92dd into master Mar 25, 2024
@carme-hp carme-hp deleted the carme-hp-patch-1 branch March 25, 2024 11:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants