Create a high-level ROADMAP.md outlining the next 12 months #740
Description
Motivation
OpenSSF’s documentation_roadmap criterion expects a public roadmap describing where the project is headed over the coming year. A concise, high-level roadmap will guide contributors and users without locking us into granular dates.
⸻
Proposed structure for ROADMAP.md
Key theme Planned direction (12-month horizon)
Quality & reliability Increase test coverage, reduce flaky acceptance tests, and formalize a predictable release cadence.
Security hardening Strengthen binary-signing and SBOM practices, integrate stricter static/dynamic analysis, and address any newly reported CVEs promptly.
AI & Copilot Studio support Expand resources and data sources that simplify building AI-powered solutions on Power Platform, with examples and documentation.
Community-driven improvements Prioritize fixes for issues raised by users, improve error messages, and host periodic discussions to gather feedback.
The roadmap will also include a brief “Out of scope for this period” section to clarify what the project will not tackle right now.
⸻
Tasks
• Draft ROADMAP.md using the table above.
• Review with all maintainers and the product owner.
• Link the roadmap from README.md and pin a corresponding Discussion.
⸻
Publishing this high-level roadmap will satisfy the OpenSSF requirement and give the community clear visibility into our intended direction.