True, but I do not think creating a separate topic on a very very similar discussion would please many people, so I am going to hijack the discussion here a bit.
Instead of discussing ways to remedy the issue, why can’t we talk about the root of the problem, the elephant in the room? We all know the problems began when Development Discussion became open for Members to use. The question is, why was this change made to begin with?
Let’s look at the two outcomes of opening or not opening Development Discussion:
First, the case of opening Development Discussion (which is what happened):
- Thousands upon thousands of completely unqualified individuals now have access to this category, along with a few dozen developers.
- These few dozen developers would not have had access to Development Discussion otherwise, because of the lack of any mechanism to upgrade a Member to a Regular. Now that Dev Discussion is open to Members, however, those qualified individuals can make posts there.
- BUT, since qualified developers are so outnumbered by unqualified individuals, in a 10-to-1 or higher ratio, Development Discussion ceases to be a useful resource for both the new qualified developers as well as the pre-existing qualified developers who were Regulars.
Now, the case where Development Discussion is not opened to Members:
- Those who are Regulars, who are qualified, have access to Development Discussion. No members are allowed in.
- The quality of discussion is great, since only qualified Regulars have access to the channel.
- There are a few dozen qualified developers who would have liked to have contributed to Development Discussion, but because they are not Regulars, they cannot do so.
If we compare the two situations, realize that in both cases, the qualified Member-status developer does not get what they wanted. They either don’t have access to the good Development Discussion, or they do have access to the absolutely awful, scum of the earth “Development” Discussion. No matter which option you pick, there is no happy ending where the qualified Member-status developer gets access to the high quality Development Discussion.
But, when you pick the opening option, what you do is completely ruin Development Discussion for the pre-existing developers. You gain nothing and lose A LOT. It is very obvious that the people behind this decision-making did not foresee what would occur, which is understandable, but what they should have done is reversed the decision a few weeks in, before the devforum community became irreparably shattered.
Take this from someone who has been a Member since 2015 and would consider himself more than qualified to be part of this community (applied once, was rejected, missed the chance to apply again before the apps were closed). Locking out Members from Development Discussion is clearly the better choice, once you fully weigh both options. It is a far better temporary solution while we wait for a proper fix, since that allows the devforum to be at least usable for some users, instead of being totally useless for everyone.