psxjoy opened a new issue, #483: URL: https://github.com/apache/ozhera/issues/483
To maintain the code quality and overall maintainability of the Ozhera project, we need to establish clear guidelines for code contributions. A solid coding style and consistent formatting checks are vital for any open-source initiative. I suggest we create the following documentation to assist new contributors: 1. A thorough coding style and formatting specification, including codestyle and checkstyle; 2. A clear and accurate process for code updates and submitting PRs; 3. A detailed procedure for reporting vulnerabilities and bugs; 4. Comprehensive guidelines for unit testing; 5. Issues should feature tags like `good first issue` to foster greater engagement. Moreover, I believe we should work on enhancing community activity. Thus, we should also consider developing a set of rules for incentivizing contributor transitions (from contributor to committer, ultimately to PPMC member) in line with ASF standards. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
