Hi @DavidLen,
Thank you for promptly updating the proposal based on the previous feedback. The added details on deliverables and acceptance criteria are generally clear and verifiable, and we appreciate your responsiveness and professionalism.
The committee has completed the formal review and is currently setting the project status to Pending. This is not a rejection, but an invitation for you to optimize the project with a more targeted approach.
The committee’s core opinion is: the project should take a more pragmatic direction, with clearer use cases and a reduced budget. The specific recommendations are as follows:
- Use case description
Please further clarify the use case for this widget within Nervos Talk:
According to the design and implementation of DAO 1.1, community members no longer need to navigate to other websites to quickly determine whether a proposal is still in the voting period, how active the voting is, or whether it is nearing its deadline, and thus decide whether to participate in the discussion immediately or go to vote. Therefore, the committee believes the practical use case for this project within Nervos Talk is more akin to a real-time billboard aimed at community members.
- Optimization of data retrieval methods
Your data source has been updated to use the API of https://docs.ccfdao.org. Although the documentation mentions many key APIs, the documentation itself was not designed as an API. Therefore, following the recommendation to “adjust project direction,” the committee further recommends that the real-time data required by the project be pulled directly from the API endpoints on https://www.ccfdao.dev using front-end developer tools (DevTools) (no need to reverse-engineer the RPC Cell structure), in order to further reduce the uncertainty and development risk of Week 1 research.
- Budget adjustments due to functional differences
The current https://www.ccfdao.dev/ platform already provides a complete display of proposal statuses, so the committee suggests that the Discourse widget focus on three core functions: “fetch + display + redirect.”
- Fetch: client-side JS calls the API
- Display: card UI (e.g., status badges, countdowns, voting bars, progress bars, etc.)
- Redirect: CTA button links to ccfdao.dev
Since the underlying data is already fully presented by the official platform, the widget is more of a “lightweight mirror + embedded notifier” rather than a complex system built from scratch.
The committee recommends reducing the budget accordingly to better match the actual scope of work.
After updating, directly @xingtianchunyan and reply here. Thank you for your enthusiasm—looking forward to seeing the revised version!
Best,
Xingtian
On behalf of the Spark Program Committee
Hi @DavidLen，
感谢你们根据之前的反馈及时更新了提案，新增的交付物细节和验收标准的内容都基本满足清晰且可验证的要求，我们很认可你们的响应速度和专业性。
委员会已经完成了正式评审，目前将本项目的状态设为 Pending，这不是拒绝，而是邀请你们对本项目进行更具针对性的优化。
委员会的核心意见是：项目整体方向应更加务实，需要进一步明确使用场景并缩减预算。具体建议如下：
-
使用场景说明
请进一步明确这个挂件在 Nervos Talk 中的使用场景：
根据DAO 1.1 的设计和实现，社区成员已经无需再跳转到其它网站，即可快速判断提案是否仍在投票期、投票热度如何、是否接近截止，从而决定是否立即参与讨论或跳转投票。因此，委员会认为本项目在 Nervos Talk 中的实际使用场景更偏向于面向社区成员的实时的广告牌。
-
数据获取方式优化
你们的数据来源已更新为使用 https://docs.ccfdao.org 的 API。尽管在文档中提到了诸多关键的API，但文档本身没有设计API ，因此根据“项目方向调整“的建议，委员会进一步建议项目所需的实时数据直接通过前端开发者工具（DevTools）从 https://www.ccfdao.dev 直接抓取API接口，（无需自行逆向 RPC Cell 结构），以进一步降低 Week 1 调研的不确定性与开发风险。
-
功能差异导致的预算调整
当前 https://www.ccfdao.dev/ 平台已提供完整的提案状态展示，因此委员会建议 Discourse 挂件专注于“抓取 + 展示 + 跳转”三个核心功能：
- 抓取：客户端 JS 调用 API
- 展示：卡片 UI（比如：状态徽章、倒计时、投票条、进度条等）
- 跳转：CTA 按钮链接到 ccfdao.dev
由于底层数据已由官方平台完整呈现，挂件更多是“轻量镜像 + 嵌入式提醒”性质，而非从零构建复杂逻辑。
委员会建议据此缩减预算到适当范围，以更好地匹配实际工作量。
更新后直接 @xingtianchunyan 并在此回复，感谢你们投入的热情，期待看到更新后的版本！
祝好，
行天
代表星火计划委员会