I would be accepting the crowd

[NtemKenyor]

For open source contributors:

We wanted an approach to filter out some code from pull requests in order to get the best set of PRs and individuals who pay great attention to detail. However, we believe that accepting every project and module design may help us check for possible human error in the future.

In other words:

We want to make sure that the code we accept into our project is of the highest quality. We are considering filtering out some code from pull requests, but we also want to make sure that we are not accidentally introducing new errors. We believe that accepting every project and module design may help us to catch these errors, but it will also make it more difficult to review and approve pull requests.

We are still working on the best way to balance these competing needs. We appreciate your patience and understanding as we work through this process.

Here are some possible solutions that we are considering:

Code reviews: We could require two code reviews for all pull requests, including a review from a maintainer or senior developer. This would help to ensure that all code is thoroughly reviewed before it is merged.
Automated testing: We could implement automated testing for all of our code. This would help to catch any errors that might be introduced in new code.
Branching strategy: We could use a branching strategy that allows us to isolate new code from existing code until it has been thoroughly reviewed and tested. This would reduce the risk of introducing new errors into our project.

We are open to suggestions from our community. Please let us know what you think of the possible solutions above, and if you have any other ideas.

Thank you for your contributions to our open source project!

[NtemKenyor]

But please be careful because immediately we detect that your project is dangerous, we would not only mark it as spam, we would block you. Thank you.