-4

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

2 Answers 2

Reset to default
1

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.

1
  • Thanks for the quoted part of the WP SE rules. This proved that the moderator was wrong. I know that pointing to the other proposal was a little bit harsh, but I found myself many times "fight" with moderators in theory and only with specific examples, they are convinced.
    – Tasos
    Commented May 26, 2017 at 7:59
1

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.

6
  • 1
    On a personal note, I do agree with you. I too think WPSE should allow Q&A specific to third party WP products, much like wp.org. Kind of like "what's good for superman is good for me" :) AFAIK, that was the case at the beginning. What I can see from WPSE meta is that there was a huge debate about it at one point. Then they decided against it (I joined the community only this year). Who knows, that decision may change in the future even. Of course, at that point we'll have a new kind of conflict.
    – Fayaz
    Commented May 26, 2017 at 17:16
  • 1
    While I'm not going to count the users of WP.SE I think that their 'reason' for excluding 3rd party issues seems valid while discounting the knowledge of their user base. They seem, also, to miss the goal of SE in general. Granted there are a lot of 3rd party products for WP, yet among their users it's likely someone has knowledge sufficient to answer questions about most of them. By excluding those they reduce their user base and likely fall short of the site's true potential to become the "Go To" site for WP-based issues. They seem to have optimized for black pearls only.
    – Gypsy Spellweaver
    Commented May 28, 2017 at 4:32
  • @Robert so you decided to delete the proposal instead?
    – Tasos
    Commented May 29, 2017 at 6:16
  • @Tasos Deleted by the system automatically; there wasn't enough interest to get it started -- See the Minimum activity requirements for Area 51
    – Robert Cartaino
    Commented May 29, 2017 at 14:39
  • @RobertCartaino So you kept it closed for 2 days without a reason and then left it open for 1 day to reach the 3 days total limit? Ok. I understand. No comment.
    – Tasos
    Commented May 29, 2017 at 15:12
  • @Tasos No. The proposal was submitted May 23rd. After I reopened it, the proposal remained open for 3+ days before was closed by the system because the proposal did not have enough interest to continue.
    – Robert Cartaino
    Commented May 29, 2017 at 15:45

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .