Why this proposal closed and this is still open and even on the phase of commitment? Either both should stay or both should closed.
Proposal: Divi Builder
I cannot answer definitively as I'm not a moderator. However, as per WordPress StackExchange policies, this site proposal about Divi shouldn't be a conflict of interest with the WordPress site.
Specifically in this help center topic, it's clearly mentioned that third party Plugins & Themes are off topic in WordPress StackExchange site:
Note that we do not handle questions:
questions concerning third party plugins and themes. As these required detailed knowledge of the workings of those plugins and themes, support is difficult and with thousands of plugins and themes available such knowledge is very specialized. Please consult the appropriate support forum for the plugin or theme in question
For this reason, if any third party Plugin or Theme has enough traction, proposal from that Plugin or Theme should be allowed. As I'm an active member of WordPress StackExchange site, I know first hand that we vote to close questions as off topic in WPSE that are specifically about third party Plugins or Themes. I'd request the moderators to reconsider (even if it requires some changes in the proposal definition).
Note to OP: it's not desirable to point finger towards another proposal. You could've made your point even without that negativity.
Yeah, Beaver Builder — hardcore WordPress experts. That proposal is a textbook-ideal example of an energetic community enthusiastically embracing the Stack Exchange model for support.
Unfortunately the WordPress community doesn't want them.
Regarding WordPress' non-support of plugins:
That is easily one of the most short-sighted, myopic decisions I have ever seen by a community (okay, top 5). Wordpress.org owes its success in no small part to its massive adoption of 3rd-party products and support. When we agreed to split WordPress SE from Stack Overflow, the argument was a vast ecosystem of questions outside of the development site. So when we agreed to create a site for "WordPress Users", it seems disingenuous now to say, "yeah, we just want to be a developer site."
Stack Exchange scales really well for usage and technical support issues; nobody's asking them to take over another company's customer service. This is all about peer-to-peer support.
I get a lot of emails from project teams asking how we can support their communities on Stack Exchange. A lot. Tool and product support is a huge growth area for many sites. Most of these projects teams have extensive communities of their own, so if someone is searching for help with the tools they use ever day, it sure would be nice to find that support on the WordPress site.
I think WordPress SE confused poor-question development with the issues of a comprehensive scope, nevertheless…
I reopened the proposal to see if there is any interest.