-
Notifications
You must be signed in to change notification settings - Fork 20
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
Update Travel_fellowships.md to add new rounds and rubrics #94
Conversation
malvikasharan
commented
Jun 20, 2022
•
edited
Loading
edited
- Included 2 more rounds
- Included link to rubric
- Create an issue template for the next round
- Tag board members to review and clarify any phrasing that they don't agree with
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.
Thanks, Malvika--most of these changes look good, but the proposed 15 July deadline won't work. BOSC is normally in July, and participants need to know at least a month ahead (preferably more) whether their travel will be covered by the event fellowship. I therefore suggested 15 May (with a 15 June reply date, which is late but probably tolerable). BOSC 2023 will start around July 24.
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 approve updates taking note of @nlharris's requested changes.
Are you sticking with 4 reviews a year, with one of them July 15? |
The pull request currently has:
Perhaps with a strong steer for BOSC applications to go direct to BOSC for a fee waiver/travel help, this would be OK for the travel/event fellowship? |
I've added my suggestions about the budget tracking spreadsheet, and resolved a merge conflict. I think the only outstanding issue is the dates - @nlharris are you still recommending changing the 15 July deadline to 15 May? |
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.
Updated proposed application deadlines (as discussed in most recent OBF Board hangout)
Note also that this line on https://www.open-bio.org/event-awards/ needs to be updated:
|
- [ ] Double check if any application has come through that may need to follow up for any missing detail | ||
|
||
**After the deadline** | ||
|
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.
- Change the deadline listed at the beginning of the application form (currently https://docs.google.com/forms/d/e/1FAIpQLSc1DFilEFV0R0hzsLGI7JkE3UHQgqQQnNXDztvqieE2TmhOMA/viewform) to the next deadline.
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 guess December 1 would be too close for this round. Changed to April 1 2023
Suggested new rounds: |
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 have updated the documents as discussed. Three rounds: 1 April, 1 August, 1 December
I vaguely thought we needed just a simple majority, but it looks like we need full board approval for this one, and modifying that would likely restart the approval process. @nlharris @HLWiencko we'll need your reviews |
@cjfields maybe just stuck on Nomi's change request (which has actually been done) |
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.
See inline suggestions in regard to typos and text improvements.
Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
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 think this is all fine; please go ahead and merge and I will review again.