Skip to content
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

Closed
tobie opened this issue Oct 2, 2019 · 8 comments
Closed

Help the applicant navigate the silent period #340

tobie opened this issue Oct 2, 2019 · 8 comments
Labels
onboarding tracking onboarding for new/incubating projects

Comments

@tobie
Copy link
Contributor

tobie commented Oct 2, 2019

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:

  • Reception of application
    • Receipt acknowledged within two business days by foundation staff (already in the process).
  • CPC then has a week to decide who the champion is going to be.
  • CPC chooses champion.
    • Foundation staff introduces champion to applicant.
  • CPC then has n weeks to collect input and have discussion about project.
    • Champion to advise applicant of deadline for questions by CPC members.
    • Champion to forward questions to applicant as they're received with the expectation of a fast turnaround (2 business days, max a week).
  • Deadline for the initial set of questions reached
    • Champion to start collecting answer from applicant
    • Champion to advise on deadline by which answers are due (1 week).
  • CPC then has n' weeks to follow-up on answers to questions.
    • CPC may ask follow-up questions, triggering a new round of questions.
  • Once all answers have been received, champion to announce to applicant that the CPC will provide its final answer by date.
  • CPC to make decision
    • Champion to update applicant on decision
  • Etc.
@MylesBorins
Copy link
Contributor

@tobie do the changes in #321 help clarify any of this for you? I think it was intending to solve a number of the points above. If there are things missing we may want to get it included in there or in a follow up PR

@tobie
Copy link
Contributor Author

tobie commented Oct 4, 2019

In part. I think what's missing is:

  • An initial kick-off email to the applicant that lets them know who their champion is. For context, I learnt who my champion was through backchannels that I'm lucky to have. That's a privileged position we shouldn't assume every applicant is in. I believe this happened because it's not clear from the process whether that's the Champion's role or the Application manager's.
  • Clear milestones (with deadlines) by which CPC members should have requested clarification requests and applicants should have replied. Clarification that those milestones should be announced by the champion to the applicant.
  • The notion of a round of questions. During the first round, all topics are allowed, during subsequent rounds, only follow-ups on previous questions are allowed, unless, of course, new information, not disclosed in the application, is suddenly discovered. The goal here is to promote transparency from the applicant and reward it with a funnel-like process in which which progress is well defined.

@mcollina
Copy link
Member

mcollina commented Oct 4, 2019

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).

@mhdawson
Copy link
Member

mhdawson commented Oct 4, 2019

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?

@tobie
Copy link
Contributor Author

tobie commented Oct 6, 2019

Will do, but won't be able to get to it for another couple of weeks.

@tobie
Copy link
Contributor Author

tobie commented Nov 3, 2019

This is still on my radar, but unfortunately not an immediate priority.

@jorydotcom jorydotcom added the onboarding tracking onboarding for new/incubating projects label Jan 14, 2020
@bnb
Copy link
Member

bnb commented Apr 11, 2023

@tobie is this one that still needs to be done?

@tobie
Copy link
Contributor Author

tobie commented Apr 11, 2023

Yeah. I think we want to let @bensternthal settle in and see how much of this could be managed through improves operations.

@tobie tobie closed this as not planned Won't fix, can't repro, duplicate, stale Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
onboarding tracking onboarding for new/incubating projects
Projects
None yet
Development

No branches or pull requests

6 participants