Open Aniketkhote opened 10 months ago
As the GetX package continues to gain popularity, the number of issues, feature requests, and pull requests is growing. With this increasing demand, it becomes even more critical to have a robust team of maintainers who can efficiently manage the project and keep up with the community's needs.
I want to kindly request that we consider expanding the GetX maintainer team by welcoming new contributors who are passionate about GetX and its mission. By adding more maintainers to the team, we can ensure that the project's growth and development continue at a steady pace.
Here are some key reasons to consider increasing the number of maintainers:
Faster Response: With more maintainers, we can provide faster responses to issues and pull requests, which can lead to an improved developer experience for GetX users.
Diverse Expertise: New maintainers bring fresh ideas, perspectives, and expertise, which can lead to innovative features and improvements.
Community Involvement: Expanding the maintainer team can foster a stronger sense of community involvement and support, allowing more Flutter developers to contribute to and benefit from GetX.
@Aniketkhote hi, did you see #2889 thread? I don't think you will get an answer soon)
Dear GetX Maintainer,
I hope this message finds you well. I wanted to express my sincere appreciation for the fantastic work you and the GetX team have done with the library. GetX has undoubtedly been a game-changer for Flutter developers, simplifying state management and making our lives easier.
I would like to humbly request the release of GetX Version 5, and I'd like to highlight a couple of key areas where improvements and enhancements would greatly benefit the Flutter community:
New Features: It would be fantastic to see new features and enhancements added to GetX. This could include but is not limited to, more flexibility in state management, additional utility methods, or new widgets that can simplify common development tasks.
Fixing Routing Issues: Routing is a crucial aspect of app development, and there have been occasional issues with the GetX routing system. A more robust and bug-free routing system would be immensely valuable for the community.
Optional Build Context: Many developers have varying preferences when it comes to passing the
BuildContext
parameter in GetX methods. It would be a great addition if developers had the option to use or omit theBuildContext
parameter as needed, providing more flexibility and aligning with different coding styles.I understand that open-source development relies on the dedication and voluntary contributions of maintainers and contributors. Therefore, please consider these suggestions in line with your project's roadmap and the community's needs.
I'm more than willing to contribute to this effort in any way I can, be it through code contributions, testing, or documentation. Together, we can make GetX even more robust and valuable for the Flutter community.
Thank you for your attention to this request, and for your unwavering commitment to making GetX a remarkable library. Your work is highly appreciated, and we eagerly anticipate the future of GetX.
Best regards,