Repository navigation
Add a key management policy for TeachLink Mobile #1489
Description
Background
The Governance/ folder does not yet include a Governance/policies/KEY_MANAGEMENT.md document. This is a governance gap: contributors and maintainers lack a clear, versioned reference for this area of governance. Adding the document closes the gap and keeps the change self-contained within the Governance folder.
Implementation Plan
- Create
Governance/policies/KEY_MANAGEMENT.mdand document the key lifecycle. - Specify the storage and access rules.
- Define the rotation and revocation.
- Add regression tests where applicable
- Document the change
Acceptance Criteria
- Governance requirement is implemented successfully
- Scope is limited to a maximum of two files
- No changes are made outside the Governance folder
- No regression in existing functionality
- Tests pass and code follows project standards
- Change is documented
Activity
rupesh-kumar-sah commentedon Oct 13, 2026
Hi maintainers,
I reviewed "Add a key management policy for TeachLink Mobile" and have a structured approach ready for implementation:
Technical Implementation Outline:
Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!
thatslinx commentedon Oct 15, 2026
@thatslinx has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @thatslinx to this issue.
ayshadogo commentedon Oct 15, 2026
@ayshadogo has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayshadogo to this issue.
drips-wave commentedon Oct 15, 2026
Congratulations, @ayshadogo! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @ayshadogo: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
grantfox-oss commentedon Oct 15, 2026
🦊 GrantFox — @ayshadogo has been assigned to this issue!
Next steps:
Closes #1489)Good luck! Track your progress on GrantFox.
docs(governance): correct anchor reference in the key management policy
grantfox-oss commentedon Oct 17, 2026
🎉 This issue has been marked as completed on GrantFox!
@ayshadogo's PR #1549 was approved and merged by @RUKAYAT-CODER.
🏆 @ayshadogo: You earned 35 FoxPoints for this contribution! Your current tier: Builder (1,025 total points). Track your full progress on GrantFox.
👏 Great work, @ayshadogo! Keep contributing to rinafcode.
drips-wave commentedon Oct 17, 2026
This issue has been completed by @ayshadogo as part of the Stellar Wave Program's 10th Wave 🥳
😎 @ayshadogo: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
docs: add key, certificate, vulnerability SLA, and patch management p…