But see, it is my belief that we should be limited so that we can learn how to make quality posts. Post Approval is supposed to assist in that by having the members of post approval give the feedback required to make it adhere to standards.
This is likely not feasible in terms of workload for the post approval team. I think we would prefer that they focus their time on improving requests for the Platform Feedback category instead, that’s also a lot more interesting and constructive work over correcting Recruitment topics.
Do you have any other suggestions for improving the quality of posts in this category?
5 Likes
Ok I can understand that but again this is a Lego game we are not doing this for a grade people just want to fun with making games and just be limited to something because, it’s not a good post.
1 Like
Three solutions in that regard:
-
expand the post approval team. Not a popular idea, even with me. But it is a solution.
-
limit new members ability to post in recruitment category entirely. Again, not popular.
-
expand the tutorial to cover an extensive course on writing topics for particular categories so that its there, and prohibit anyone from becoming new members until they have completed that segment of the course.
I did mention in my OP that I did not know if it would be a larger burden on PA, and now that I know it will be, I think we need to consider more drastic solutions to a very real problem.
I have mixed opinions on this. Although it would definitely improve quality, new members needing to quickly hire someone would be turned off.
Dunno how this would work with Discourse limitations, but community approval. If a few people rate it as quality, then it would be automatically approved.
Edit: changed to community approval for added clarity
1 Like
Private recruitment exists. It’s just used sparringly and when there isn’t a good reason for a wide audience.
Do post approval not give feedback to posts that do not meet the quality bar? 
@CaptLincoln - Your post was a great read and yes - there are some very low quality posts in Recruitment, however I do not agree that we should make it subject to the post approval process. If you see a post that you think breaks forum or category rules, you should flag it.
You can (and should!) message users if you have any feedback about their post.
People should be able to collaborate without a barrier to entry, as long as you can accept and understand the basic rules of the forum.
The Discobot tutorial is very helpful to new users, but I suspect how many actually compete it as (iirc) you need to be a new member [at minimum] to fully complete the tutorial (and the tutorial starts… when you join the forum)
You could also argue that there are technical difficulties with modifying the tutorial, but I can’t speak on those.
The flag system acts as a community moderation system. Hiding bad posts and locking topics that are getting a bit too heated.
How would this function with bad posts? For people to rate it as ‘of quality’ and for it to be approved, people need to see it.
When most people suggest community moderation, they mean downvotes - not community approval.
relatively off-topic, but no it’s not. roblox isn’t even a game. don’t call it that. you don’t make large companies off a ‘lego game’ unless you’re the publisher.
1 Like
I don’t understand what is roblox then a job? a lifestyle?? It is a game the reason why I said that because,
1 Like
Roblox is a platform, not a game. Platforms might contain games. Which Roblox’s does
2 Likes
I realise so, but if public recruitment becomes member+, what will happen to the private one now.
1 Like
Wait, you mean to tell me you don’t sell your stuff for just under 2 pennies? Will 3 be enough?
5 Likes
I was being sarcastic. It’s blatantly obvious that you don’t sell your services for that low
5 Likes
Public recruitment should not become Member+. The name is literally ‘Public Recruitment’.
If you dislike public recruitment and only want to hire good forum users (not necessarily top devs), Private Recruitment is here for you.
yes - this post was a minor rant. there are a few good reasons for posting in private recruitment, however, collaboration should stay as is for the sake of the community.
my entire post was arguing in favour of keeping collaboration as is.
2 Likes
Here’s the problem, though: member no longer means quality— it means activity.
It would reduce the number of small bids but would devastate the community and create unnecessary work for the approval team. I say “no”
3 Likes
Pretty sure the problem with that would be budget constraints. As it’s already been noted here before, certain departments in the company have higher budgets than others, and I would think that the DevForum team would be allocated a smaller amount of money as it’s essentially a private sector of the Roblox site unless you search it out.
I can almost guarantee that people would zip right through these guidelines like they do the terms and conditions of a software install. This would do very little to stop inexperienced users from posting unprofessional requests in the long run.
It should also be noted that a private collaboration subcategory already exists for more experienced members. Once new members advance to the rank of a normal member of the forum, they can choose to mute the public recruitment category and only deal with private recruitments if they so please.
All in all, I believe restricting the category entirely would be deemed elitist towards new members, and cause strain on the DevForum team. My suggestion would be that more users should be educated with Discourses built in functions to mute categories as a user pleases, that way every user can choose which topics they want to read rather than rumaging through low quality posts in categories they don’t care about.
I myself had to be taught how to mute subcategories not too long ago, so I can imagine that new users might not even know this feature exists at all.
4 Likes
I really don’t have too much to add on top of what others have already said - this is mostly a case of not enough staff members on post approval to make locking down more forum categories under approval for newer members viable.
At the same time, while I understand the concern of new members skirting past rules (myself included on several occasions), simply being new to the developer forums does not necessarily equate to producing low-quality posts.
I wasn’t even aware of a private collaboration subcategory, but that sounds like the solution to your problems at the moment.
1 Like
Personally, I believe that adding post approval is the only feasible solution. The other idea I had is to create a starred post system for members and higher. Essentially, full members(or select members of the community, whichever is preferred) would have the ability to publicly recognize job listings that they choose. In theory this would allow for the “higher quality” posts to stand out more amongst the sea of poor quality threads. However, as mentioned above, it does create an elitist society.
Ultimately there is no perfect solution. I am glad that this topic has gained this much attention, because it means we care. Im glad we keep this civil because it means we’re mature enough to discuss this. Thank you, everyone, for helping so far, and I hope to see more soon!
EDIT: If people are skirting past the tutorial, I would suggest removing the “skip” function from the thread tutorial, or create a separate tutorial based solely on content without the skip function that is required to achieve new member.
Just to be overly clear: post approval people are volunteers from the community, they are not Roblox staff and they are not paid. They just do the work they do because they care a lot about the developer forum.
9 Likes
Ah, I wasn’t aware of that. Thanks for the clarification!
Although in that case, if Roblox were to suddenly start promoting members at a faster rate to be able to approve posts, I would also be concerned about potential bias or abuse of the role (though I personally haven’t run into that yet).
1 Like
I agree that quickly promoting community members is a bad idea. What I would suggest is if we were to add post approval, have the team get together and choose who else they would want to add to their team in a slowly expanding fashion. Again, I don’t know everything and will not presume I can answer every issue, but personally, I would take the hit of expanding the post approval team to add this feature. That is a personal opinion, not a fact of best course of action.
This whole thread seems to be a hate letter to new members. Several of you seem to be obsessed with having massive amounts of restrictions in place just to punish (or as some of you like to call it “help”) people who are new.
Do you know what happens when people are overly regulated on a forum? They leave. So if we add all these insane regulations you all are wanting then the growth of the devforums (and Roblox Dev community) would slow.
3 Likes