-
Notifications
You must be signed in to change notification settings - Fork 171
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
Help the applicant navigate the silent period #340
Comments
In part. I think what's missing is:
|
One of the things the CPC does not want to commit to are deadlines. The key reason is that each application should get enough review time. For the very same reason, having the concept of a "round of questions" is complicated. That can work well after we have received all the questions from all the CPC voting members, and it would take time to collect them all before sending them. I think that would delay things further. Given the above, do you think that having a round of questions would still be useful? (Note that a voting CPC member that cannot ask questions could just... -1 the application, so it might be counterproductive). |
At this point I'd suggest a follow on PR. @tobie would you be able to submit a PR which adds what you think are gaps in the progressions doc? |
Will do, but won't be able to get to it for another couple of weeks. |
This is still on my radar, but unfortunately not an immediate priority. |
@tobie is this one that still needs to be done? |
Yeah. I think we want to let @bensternthal settle in and see how much of this could be managed through improves operations. |
For the applicant, the silent period is a complete blackbox.
What would really help would be for them to understand that there's a clear process happening, and where in this process we currently are. So for example:
The text was updated successfully, but these errors were encountered: