As a Top Contributor, I have seen and reported quite a few “questionable” posts in the Community Resources section, including but not limited to:
Low-quality posts
Posting external articles without elaborating on the article
Posts that encourage “bad” programming habits
I have tried to bring restricting the ability for creating threads up internally, but it doesn’t seem like it has gotten any attention. The intention of this change would make new members require posting in #bulletin-board and messaging the Post_Approval group to move it, like bug reports and feature requests currently do. This would also allow for better tracking of posts by new members in the subforum, and potentially them being full members.
Feature Requests/Bug Reports is restricted to ensure a higher than average quality control. Community Resources should likewise be expected to have better quality posts than a support thread.
Speaking as a new member accepted through the application process:
With the recent influx of new members, I feel that much more of the forum needs to be restricted, making them use the post approval process and thus stopping the majority of low quality posts in more ‘professional’ categories.
They should make New Members can only post on categories that will help them to show Lead Top Contributors they are fully mature, knowledgeable and ready to help people out. About Inception Forum, they can post on it but, they are at least to focus on Development Support category. This is just on my opinion.
What you said is true. But, they are not ready to do so (includes me). Who knows, the next guy who will become full-Member in Devforum might contribute in Community Resources. As Nexus stated:
We don’t know this New Member if he is actually good at giving out Tutorials.
That’s why New Member should follow this path to become Full-Member.
Calling it an application is a stretch, but yes–rule 15.1
15.1 You are not allowed to create new Bug Reports or Feature Requests for other people. This includes non-Developer Forum members and those in the New Member role set. Instead, please re-direct them to group-PM the @Post_Approval group privately so their topic can be manually created.
The message title should be “Request: Posting Bug Report or Feature Request”. New Members should post their thread in Bulletin Board and link that in the PM.
As a new member I was here before this new way of being accepted started I see this as something that needs to become a top priority. I have noticed a lot of the newer member that have just been promoted are not making very good posts and it is lowing the quality of the Dev Forum. I think this should be addressed soon.
Perhaps a secondary trial rank for new users off this system that only give access to bulletin or inception, and then contacting the contributor group to move it, then to gain new member access. I’ve been new member for roughly a year because I just don’t have much to say in categories I already barely have access too. I wouldn’t want that taken away because of this new setup.
to be fair I think your right with the whole new member thing. but loads of new member’s like me aren’t posting low-quality post. and this would affect us if the staff members don’t make us member. I think they just have to go back to the manual system so they can do a quality check before they are accepted into the forrum.
I understand that the applications were backed up but I don’t think that this system is the right one. I am fine with allowing people to be accepted for their activity but there needs to be some sort of trial or tier rank that people must go through.
I agree completely. The number of low-quality community resource threads has been unfortunately high as of late. While we could very well just flag poorly made posts, that is more of a band-aid fix as it does not solve the underlying issue of New Members not planning out what they post very much.
I’m starting to get concerned about how many low quality or just downright unfinished resources are being posted in this category recently. There needs to be a post approval process for New Members in Community Resources.
Feature Requests/Bug Reports is restricted to ensure a higher than average quality control. Community Resources should likewise be expected to have better quality posts than a support thread.