[Community Request]: Consensus of descriptions and responsibility for armbian-config #523
Description
Which feature would you like to have?
[Community Request]: Consensus on Descriptions and Responsibilities for armbian-config
Background
It appears that bug reports are often used as the default action for various requests. Given the diverse communities involved with Armbian—such as the build community, homelab community, and manufacturers communities—it's important to establish clear guidelines on how different types of issues should be reported and addressed.
Proposal
In the spirit of transparency and efficiency, I propose that we standardize the way bug reports and feature requests are handled with armbian-config.
IMO as a technician. A bug should be clearly defined as a failure that can be deduced to a specific solution. On the other hand, a feature request is a suggestion for new functionality that needs to be considered and developed.
Rationale
- Clarity: Clear definitions will help contributors and maintainers quickly understand the nature of the issue and prioritize accordingly.
- Efficiency: Proper categorization can save time and resources, allowing for more effective problem-solving and feature development.
- Community Engagement: A standardized approach will help set the correct tone and attract the appropriate attention from the community, making it easier for everyone to contribute meaningfully.
Conclusion
By setting these guidelines, we can improve the overall workflow and ensure that issues are dealt with more effectively. This will not only benefit the technical team but also enhance the experience for all community members.
Thank you to the build community for your continued support of this project. Your contributions are invaluable and greatly appreciated.
Thank you for considering this proposal.