A core part of our Strategic work is the evaluation of how proposed work serves the Web. In the "Evaluation" phase at the end of the funnel, we make the case whether work is ready to proceed to Chartering of a Recommendation-track deliverable. At that point, we need to identify:
-
Will this work help to lead the web to its full potential?
-
Is the work Rec-track ready?
- Rec Track Readiness (AB)
- Intent to Migrate (WICG)
-
Do we have the ecosystem of participants needed to make the work successful?
- users, developers, implementers; industry sectors
- from that we can dig into
- who specifically is involved? interested, opposed?
- what tools and frameworks do they use?
digging deeper:
Will it add value?
- something good for web users. what are the alternatives?
- have "horizontal" (a11y, i18n, security, privacy) issues been considered and identified?
- what's its importance/opportunity cost?
Will we be able to make it succeed?
- right participants interested. What does the ecosystem look like?
- implementation likely
- manageably sized problem
- achievable timeline
- minimum viable product
- does it raise architectural issues that need to be addressed before it can succeed?
Special considerations?
- risk factors
- incentives
- openness, decentralization
Once we're past the transitional phase, We should plan evaluation reports that compile our review of the area and recommend for/against chartering work at this time. This report will help us to tell the story to our members and prospects when we move to chartering and beyond.
- Advance notice to AC when team feel a WG charter is likely to be developed, we send "advance notice" to the AC and public-new-work.
- Horizontal review: in this phase, team should request review of charter-in-development from a11y, i18n, arctec, privsec.