Repository navigation
Add an end-of-life policy for TeachLink Mobile #1493
Description
Background
The Governance/ folder does not yet include a Governance/policies/END_OF_LIFE.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/END_OF_LIFE.mdand document how EOL is decided and announced. - Specify the support reduction stages.
- Define the migration guidance.
- 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
ranjeet150 commentedon Oct 12, 2026
Hello,
I am interested in taking up "Add an end-of-life policy for TeachLink Mobile" and implementing a production-grade solution.
Technical Implementation Outline:
Please assign this issue to me. I will submit a clean, well-tested, and production-ready PR promptly!
Emelie-Dev commentedon Oct 15, 2026
@Emelie-Dev 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 @Emelie-Dev to this issue.
sadeeq6400 commentedon Oct 15, 2026
@sadeeq6400 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 @sadeeq6400 to this issue.
chikawobishie-sketch commentedon Oct 15, 2026
@chikawobishie-sketch 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 @chikawobishie-sketch to this issue.
drips-wave commentedon Oct 15, 2026
Congratulations, @sadeeq6400! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @sadeeq6400: 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 🌊
docs(governance): fix relative link to the lazy consensus process
grantfox-oss commentedon Oct 17, 2026
🎉 This issue has been marked as completed on GrantFox!
@sadeeq6400's PR #1550 was approved and merged by @RUKAYAT-CODER.
🏆 @sadeeq6400: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,628 total points). Track your full progress on GrantFox.
👏 Great work, @sadeeq6400! Keep contributing to rinafcode.
drips-wave commentedon Oct 17, 2026
This issue has been completed by @sadeeq6400 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @sadeeq6400: 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 end-of-life, support, compatibility, and data residency pol…