Hi all, Apache Fesod has now entered the Incubator. Before this, the project was not always very well-structured, which led to situations such as:
* Some contributors, out of passion, submitted a very large amount of code without much prior discussion; * Some new modules were added without going through community review. This has made code review quite heavy, and also limited effective communication within the community. I would like to propose the following guideline: For major changes, such as introducing a **new module**, contributors should not only open an Issue on GitHub, but also start a discussion on the **dev mailing list**. The discussion should: * Last at least **72 hours**; * Receive at least **+3 votes** before moving forward. I want to emphasize that this is **not meant to restrict contributions**, but to ensure that significant changes are discussed openly and thoroughly, so that all community members have the opportunity to share their views. This will help improve the project’s health and sustainability. Looking forward to your feedback and thoughts. Best, Shuxin Pan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
