-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Execute the documentation strategy #158
Comments
I made some changes in the order of Releases 7 and subsequent compared with the order available in https://github.com/orgs/json-schema-org/discussions/386. We have: The reason is to better adjust to the recent discussions to enable implementers with more resources. |
Release 1 completed. Excellent work @mjgutermuth and @aku1310. |
Hello! 👋 This issue has been automatically marked as stale due to inactivity 😴 It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details. There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest. Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack Thank you for your patience ❤️ |
Purpose
The purpose of this issue is to execute the Documentation strategy defined in issue #245 .
Scope
See issue #245 .
Objectives
See issue #245 .
Repository
All the changes will be implemented in the new website repo: https://github.com/json-schema-org/website
Plan
🏁 Release 1
🏁 Release 2
🏁 Release 3
🏁 Release TBD
🏁 Release 4
🏁 Release 5
Rebuild the Reference docs
🏁 Release 6
🏁 Release 7
🏁 Release 8
🏁 Release 9
🏁 Release 10
Success Metrics
See issue #245 .
Risks
See issue #245 .
Governance
We'll use milestones to group releases.
This is the group of people working in this project:
The text was updated successfully, but these errors were encountered: