Lets add a way to track conflicts between modules, and then later set up drupal core to check and report on any conflicts found

I am thinking it would be a very nice feature for each project listed on Drupal.org to have the ability to add a list of other projects that the given project conflicts with. This is a new solution to the problem noted in:
https://www.drupal.org/node/92233

By maintaining this information on Drupal.org, rather than in .info files we can better track issues and allow Drupal Core to get the latest updates about problems and fixes to problems related to conflicts with another project/module. I know that there could be some themes that have conflicts with modules.

One way to do this would be to add another field on the issue tracker for the listing of a conflicting project. From here, details about what the bug is and whether its something that can be fixed, and a level of severity would be good to have. Another way to do it is to have an entirely new field for the project to add conflicting projects, and at that time also add any issues that have more details about the conflict. I'd suggest the former. If we do the former, I expect we will have some issued as won't fix.

It would be nice to get a quick report of conflicts with other projects, such that we might quickly identify other modules with similar functionality.

It would be nice to make an API to read this data from Drupal.org so that when someone enables two modules that conflict, a message can appear on the module page or elsewhere notifying the administrator and allowing them to quickly research the concern.

Thanks for your consideration, let me know how I can help with this.