-
Notifications
You must be signed in to change notification settings - Fork 503
Description
🐞 Problem
Currently, there are outdated projects listed in the project suggestions, which may confuse contributors who are looking for active projects to contribute to. This issue aims to remove the outdated projects to ensure the list remains accurate and up-to-date.
🎯 Goal
The goal of this change is to improve the quality and relevancy of the project suggestions list by removing projects that are no longer actively maintained or haven't received significant updates. This will help contributors find projects that they can actively contribute to and avoid wasting time on outdated projects.
💡 Possible solutions
To address this issue, we need to establish criteria for determining the status of a project. Consider the following factors to identify outdated projects:
- Check if the project repo has been archived or deprecated by the maintainer/owner.
- Identify projects with no recent updates (e.g., no issues, pull requests, or commits) within the past 6 months.
- Look for unresolved critical issues or bugs that have been left unattended for a long time.
- Examine if the project's documentation has been updated recently. Outdated documentation might indicate an inactive project.
- Assess if the project is still compatible with the latest versions of its dependencies or the platform it's built for.
- Review if the maintainer or owner has publicly announced that they are no longer maintaining the project.
- Evaluate if there are active discussions in the issues, pull requests, or project forums, indicating community engagement.
📋 Steps to solve the problem
- Comment below to indicate that you are working on this issue.
- Review the
listOfProjects.js
file that contains the project suggestions. - Apply the established criteria to identify outdated projects.
- Remove the outdated projects from the project suggestions list in the
listOfProjects.js
file. - Make sure to update the file with the changes accordingly.
- Commit your changes with an appropriate commit message, clearly stating the purpose of your modifications.
- Push your changes to your forked repository.
- Submit a pull request to the original repository and include the following comment in the pull request description:
Addresses #<put issue number here>
. - Request a review in the comments section of the pull request to ensure the modifications are accurate and appropriate.
- Celebrate your contribution to this project once the changes are successfully merged!
Let's work together to ensure that the project suggestions list remains relevant and helpful to all contributors! 🎉