-
Notifications
You must be signed in to change notification settings - Fork 152
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
Exception for travel fund submission deadline for the Node.js collaboration summit #1254
Comments
+1 for me. |
Given the facts of the matter here, I'm certainly in favor loosening or eliminating the 8-week rule for this event. |
Yeah, as a matter of policy, we should make it clear to everyone, always, that we're outcome-focused, not process-focused. If a rule creates undesirable outcomes, we make exceptions and then fix it. Worth noting here, btw, that the 8-week deadline is described as "default", hence suggesting it can be moved to match requirements. Let's discuss the rest of the issue (delegating to the Node TSC and providing an envelope) during today's call. |
+1 from me as well. |
+1 and we should expedite this |
What's the conclusion from the CPC meeting? |
@joyeecheung, Robin should be reaching you out soon 🙇 |
I just need to know whether we can tell collaborators that the deadline is lifted for this summit and they should apply now. This is time sensitive. |
I'd think they should be applying regardless, just in case. |
Yes, pleas, they should apply, definitely. |
Conclusion of the CPC meeting today was:
|
Thanks, I'll send an email to those who answered about travel fund support in the attendance poll and suggest them to submit the request before Feb 27. |
We're tracking fund estimation requests in #1181, so I'll go ahead and close this. Feel free to reopen or file a new issue if you feel like we haven't properly addressed this. |
It seems we overlooked the flexibility of the default deadline when we reviewed #1230 which landed 3 weeks ago.
Due to organizational overhead, the Node.js collaboration summit was only confirmed 2 weeks ago, which was already 8 weeks from the event dates, and we did not realize the impact of this new rule on the summit during the review. For this summit I propose that we make an exception for the deadline because:
On what exception to make: given that it's time sensitive, it would be more efficient if we can assign a maximum collective budget to this collaboration summit (say 8K or 10.5K) and the Node.js TSC can take on the review and allocate them to applicants for this summit at our discretion, instead of having the CPC review the requests for each individual which only happen once a month. If we go over the budget, we can request additional reviews from the CPC for less prioritized applicants. The reason is:
The text was updated successfully, but these errors were encountered: