Establishing a Maximum Timeframe for Allocator Due Diligence Review

[NDLABS-Leo]

Proposal: Establishing a Maximum Timeframe for Allocator Due Diligence Review

Background:
Since April and up until now (August), there have been a total of 84 active Allocator channels. However, only about 12 channels have progressed to the second round refill, and only approximately 8 have reached the third round refill (these figures are rough estimates). The current review process has resulted in significant inefficiencies due to the following issues:

1. After the Allocator’s Due Diligence Review issue is created, there are significant delays in feedback from the allocator, and reasons for these delays are often not provided in a timely manner.
2. After the allocator provides specific explanations and proposed solutions, it often takes a long time before a conclusion is reached, leading to uncertainty in the process.
3. Delays in communication between the allocator and the reviewed person after the Allocator’s Due Diligence Review issue is created.
4. The timeframe for RKH to refresh data capacity (dc) after a request is tracked is inconsistent, leading to unpredictable delays in the process.

Proposal:

1. Display the current governance team, reviewer, and RKH personnel, along with their specific roles and responsibilities, on the GitHub repository. This would enable better identification of the appropriate contact person when issues arise, thereby improving efficiency.
2. After a review issue is raised, the allocator must respond within 72 hours. Once the allocator has provided their response, the reviewer must conclude within 2 weeks. If no conclusion is reached within this period, the applicant or a governance team member may tag the issue as “Delayed Review” (governance team assistance is required to add the “Delayed Review” tag). Issues tagged as “Delayed Review” should be commented on under the “Upcoming Allocator Call” issue, and the governance team should reach a conclusive decision on these issues during the meeting.
3. “Allocator Compliance Refresh Requests” for RKH should be executed at least once every 2 weeks to ensure timely updates and avoid unnecessary delays.

Conclusion:
By implementing these measures, we aim to upgrade the Allocator review process, reducing delays and improving overall efficiency. This will not only enhance the experience for applicants but also contribute to the smooth operation of our community.

[Kevin-FF-USA]

Hey Leo,
Thanks for kicking off this proposal. There are some great points outlined, so to build awareness on this and flush out more input I've added to the upcoming agenda for the Allocators Call.

Looking forward to discussing and make this refresh process as simplified as possible for everyone.

[NDLABS-Leo]

Hi, @Kevin-FF-USA
Thank you, we will be on time for the Allocators Call.

[galen-mcandrew]

I appreciate this proposal, and the discussion around it from the governance call. I think the next steps would be some updates to the repo readme with contact info and some SLA target timelines.

[NDLABS-Leo]

Thank you. @galen-mcandrew
That's great, the first progress will all make our community better, each in their own way.

[Kevin-FF-USA]

Keeping this thread updated as this issue is worked. Current steps in progress to reduce the refresh time.

1. Meta Alloctor and Smart Contracts
   Will be coming from FIDL

2. RKH
   Adding additional RKH for processing

3. Templates
   Capture more relevant information up front

4. Auditor (Foundation)
   Dedicated role to triaging requests