Add templates for issues in releng

Signed-off-by: Samyak Jain <samyak.jn11@gmail.com>

.forgejo/ISSUE_TEMPLATE/stalled-epel-ticket.md

@@ -0,0 +1,40 @@
+---
+name: Stalled EPEL package
+about: Report or follow up on a stalled EPEL package request
+title: "Stalled EPEL package: <package-name>"
+labels: ["ops", "points/01", "Priority/Low"]
+---
+
+## Describe the issue
+
+<!-- Provide a description of the stalled EPEL branch request. 
+     Include the package name and what the request is about.
+     If there is a related Bugzilla entry, link it here. -->
+
+
+## When do you need this? (YYYY/MM/DD)
+
+<!-- Provide the date by which this request should be completed.
+     If no specific date, write "ASAP" or "N/A" -->
+
+
+## When is this no longer needed or useful? (YYYY/MM/DD)
+
+<!-- Provide a sunset date after which this request becomes obsolete or is no longer needed.
+     If not applicable, write "N/A" -->
+
+
+## If we cannot complete your request, what is the impact?
+
+<!-- Describe the consequences or impact if this request cannot be fulfilled.
+     What is at risk or what would be affected? -->
+
+
+---
+
+## Checklist
+
+- [ ] I have checked existing issues for duplicates
+- [ ] I have filled out all the fields above
+- [ ] I have provided relevant Bugzilla or reference links (if applicable)
+

.forgejo/ISSUE_TEMPLATE/unretire-package.md

@@ -0,0 +1,40 @@
+---
+name: Unretire a package
+about: Request to unretire a package and assign a new maintainer
+title: "[UNRETIRE] <package-name>"
+labels: ["ops", "points/01", "Priority/Low"]
+---
+
+## Name of the package?
+
+<!-- Enter the exact name of the package you want to unretire -->
+
+
+## FAS username of the new maintainer?
+
+<!-- Provide the Fedora Account System (FAS) username of the person who will become the new maintainer -->
+
+
+## Branches that you need it to be unretired for?
+
+<!-- List the branches (e.g., f40, f41, rawhide, epel-9, etc.) -->
+
+
+## Package re-review BZ URL?
+
+<!-- If applicable, provide the link to the Bugzilla re-review request. If not applicable, write "N/A" -->
+
+
+## Any extra information?
+
+<!-- Add any additional context, justification for unretirement, or other relevant details -->
+
+
+---
+
+## Checklist
+
+- [ ] I have checked existing issues for duplicates
+- [ ] I have filled out all the fields above
+- [ ] The new maintainer is available and aware of this request
+

README.md

@@ -147,18 +147,23 @@ Check our [Contributing Guide](https://forge.fedoraproject.org/releng/tooling/sr
 ## ❓ Frequently Asked Questions
 
 **Q: How do I request a package unretirement?**
+
 A: File an issue here with the package name and justification for unretirement.
 
 **Q: My package build failed in Koji, what do I do?**
+
 A: If it's a package-specific issue, contact the maintainer. If it's a broader infrastructure issue affecting multiple packages, file an issue here.
 
 **Q: How do I request a buildroot override?**
+
 A: Use the [Bodhi web interface](https://bodhi.fedoraproject.org/) for override requests.
 
 **Q: When is the next release?**
+
 A: Check the [Fedora Release Schedule](https://fedoraproject.org/wiki/Releases/Schedule).
 
 **Q: How do I become a Release Engineer?**
+
 A: Start by contributing to RelEng tasks, attending meetings, and getting involved in the community. Contact the team through our communication channels.
 
 ## 📅 Release Schedule
@@ -178,14 +183,11 @@ Current and upcoming schedules: https://fedoraproject.org/wiki/Releases/Schedule
 
 For urgent, release-blocking issues:
 1. **File a high-priority issue** here with `[URGENT]` in the title
-2. **Notify on IRC/Matrix** in #fedora-releng
+2. **Notify on IRC/Matrix** in #releng:fedoraproject.org
 3. **Email the mailing list** if immediate response needed
 
 ---
 
 **Thank you for helping make Fedora releases better!**
 
-The Fedora Release Engineering Team
-
-*Last Updated: $(date +%Y-%m-%d)*
-
+The Fedora Release Engineering Team