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.
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
MDA/MolSSI workshop page with registration #379
MDA/MolSSI workshop page with registration #379
Changes from 3 commits
15b1cb9
e442200
71fd581
989213a
c210408
4c80d70
d59482b
9471a5d
477dd7c
22ad82c
cc7b4d3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to make a single registration button here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added one that looks like this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The timeline works for me (though as a note, May 27 is a Mon, and May 28 is a Tues). I am only changing the date since we say by May XX. That way, we have May 28 to review/decide, and can send notifications out on May 29.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I appreciated the detail to semantics.
I left it as "on May 29 or earlier" to convey that we are keeping it tight. I'd like people to start looking out for notification starting May 29.
The reg form also contains May 29.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We want to tell non-local applicants ASAP if they have been accepted so that they can plan travel (see above). If we wait until June 5+X to tell them, they have less than 2 weeks. The alternative is to tell all non-locals to apply for a bursary, regardless of if they need it, which will add even more to our reviewing load.
We could say that application deadline for non-locals is May 27. However, then we effectively give priority to non-locals as we don't know how many locals want to come.
Therefore, I suggest that we keep a single deadline for all applications and we make this deadline May 27 for everyone. In this way we will have all information when we need it.
If we don't get enough applications we can then extend it until June 5.
Opinions @IAlibay @fiona-naughton @jennaswa @armcdona ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that we should just keep it simple and have one deadline.