Optimizing Contributor Communication

[thewh1teagle]

When creating packages for mingw/msys2, it is recommended to inform the contributor upfront about the likelihood of merging. In my own experience, there have been instances where I was asked to fix things in two different pull requests, and only later was it communicated that the changes would not be merged. To improve the process, it is advised to first communicate the potential for merging based on technical reviews. If issues are identified that need fixing, guide the contributor to address them. This approach ensures that contributors are aware of the potential outcome before investing additional effort in the process, avoiding unnecessary work in cases where merging may not be possible.