Allow members respond to Feature requests in Platform feedback

I can no longer use the Post Approval because it is out of date. This leaves me and many other members without a voice on feature requests. I feel attacked by it. I feel inferior. From what I’ve read, Developer Relations is supposed to make an alternative to Post Approval, but that wasn’t added in this forum.

We can respond to bug reports, but why can’t we respond to feature requests? I would like to request a few things, but there was already a topic and I cannot bump it with additional use cases and more information in general.

(I used translator, sorry for mistake)

8 Likes

Well, I have no idea why it is like that, but people already just say “Yeah I’m having this bug too, plz fix”, and that will be the same for feature requests (“Yeah I think this should be a feature plz add it”). There will only be 1% (Which should be 100%, but sadly can’t) that actually help the topic giving more information so sorry, but no. We could if more people didn’t just reply with “Yeah me too”

3 Likes

Do you see? That’s the problem. Regulars are so against members for no reason. In the time I’ve been browsing bug reports, I can’t say I’ve seen members write bad responses like “Yeah I’m having this bug too, plz fix”.

And you absolutely have no authority to say

This is a request for Developer Relations, not you. If all you want to do is be toxic just because I’m a member asking us for more freedom, don’t answer.

6 Likes

Okay. Let me get this straight. I don’t hate members for no reason at all. I (WE) just want them to be better at posting. If this is a request for Developer Relations, make it private. Sometimes WE just want to give our feedback as well.

3 Likes

We don’t hate or are against members, we just know what some do and some don’t in matters of the #platform-feedback topic(s) and how they behave and post in there. I’ve seen this happen for the past year in the bug section of the forum and I don’t want it to happen in Features.

Also, if you’ve seen other topics in #platform-feedback:engine-bugs, #platform-feedback:studio-bugs there are members or regulars who say the same thing that don’t contirbute to the topic or help engineers solve a problem. He has the authority of saying that as he is a witness of this for the past months or years of members/regulars saying the same thing or spam replies.

Being a user on the forums who LIVES for the #platform-feedback topic as that’s my favorite place to post, I don’t wan it to become useless and become like #development-discussion with usless topics and crappy questions/quality posts.


In the original post, I don’t see this being affordable as I’ll see more and more useless topics that members might mistaken with such as broken scripts, low-quality topic and replies, and such. You and others have to wait this out until DET finds a replacement if I recall.

3 Likes

Currently,

  • Member -> Regular promotions are on hold and,
  • Post Approval is in the works of being improved.

The Developer Relations/Engagement team is working on a new system for these 2 concerns. There’s not much information about it, but you may ask the Developer Engagement Team regarding the matter.

Side Note:
When features like these are added to our forum, Roblox engineers develop the “plugins” needed with their own manpower, so please be patient.

My topic was requesting members the right to respond to feature requests. If we can be trusted with bug reports, we can be trusted with feature requests.

I wholeheartedly believe that members should be given the same rights as regulars. This barrier between members and regulars is almost reminiscent of systemic racism, and I don’t like it one bit. In all honesty, we should even be able to create topics in platform feedback entirely without any approval system.

If you go here you will find that six-hundred members have gotten their posts approved. This proves even more that we can create topics there.

If anyone else can say otherwise, please show direct evidence.

Edit: I also hear that regulars get an exclusive lounge category that has a sub-category for general Roblox conversations and even an off-topic category! What! You get a place to talk about non-development topics in this Roblox talk category, or just let yourself relax completely in the off-topic category by talking about absolutely everything, even topics that are not related to Roblox! This is a serious prejudice to members’ freedom of expression.

1 Like

I understood your request and I’m not saying that members should be barred from platform feedback. I was just providing some of the current situations the Developer Engagement Team is trying to resolve.

The concerned teams are working to make the thought of elitism and the barrier between member and regular much seemless or remove it completely. Please note that forum trust levels (Member/Regular/Leader) is just a representation of your proficiency in using the forum and does not represent you as a developer.

The Community Sage group has suggested to make off-topic Roblox Discussions open to Members. It’s just a matter of consideration from DET.

1 Like

I understand you, however we should just get our rights we deserve. Nobody wants approval system because it created this environment that is toxic to members. Any time a member requests access to a category that is locked away behind a regular wall, they will be immediately harassed. I want to stop seeing my colleagues being harassed because they want more freedom.

2 Likes

Users who are more experienced on the Devforums are granted privileges for their dedication to improving its quality and making Roblox a better place. I do not understand your political comparison there.

There are no categories locked away, almost all important ones have a post approval system. The ones that don’t are unnecessary and merely privileges, not rights.

There is not any kind of prejudice towards members at all. Remember that Discourse (the software this forum uses) has a concept of trust levels. "Visitor, “Member”, “Regular”, “Editor”, and “Leader” (as they are called here) are trust levels. Visitor is TL0, Member is TL1, Regular is TL2, Editor is TL3, and Leader is TL4. The higher trust level the more stuff you can do. Members have a lower trust level, so they are just not trusted with more access to the forum yet. An approval system was necessary; otherwise the newer ones making mistakes (as we all do; we’re humans therefore imperfect) would hurt the browsing experience for other readers, and most importantly, Roblox engineers, since they are the ones actively looking at #platform-feedback and taking feature requests into consideration and fixing bug reports that get reported.

If there wasn’t an approval system, the less knowledgeable members (which unfortunately is a lot, like, a lot) would just post garbage on that category. This has been seen in #development-discussion and #resources, but I guess that is expected. Or, they would post feature requests with only a proposed solution and no use cases, or post bug reports without repros which don’t help engineers at all with considering why a feature should be added or how to fix a certain bug when they don’t even know how to get it to happen for themselves.

3 Likes

Umm… no. We don’t want another influx of irrelevant and/or garbage replies flooding Platform feedback. Plus regulars are more trusted to file quality feature requests, that follow the correct instructions and ect. Therefore there’s really no need to reply to a feature request when the feature request itself has been provided.

As a disclaimer, I obviously don’t speak for DevRel or anyone but myself. But, I’m in constant communication with the Community Sages and was a member of the Community Post Approval team for most of its lifespan. As a result, I have a decent amount of insight into this discussion that nobody else has had so far.

I can get more into it if you want, but the gist is that the signal to noise ratio would be too high if members were given unrestricted reply access to feature requests. We found that members were very quick to grasp what was required in bug reports, but we also found that they often reported bugs that weren’t real. As a compromise, members were given permission to post replies on bug reports with no restriction, but not allowed to make topics to prevent not-bugs from being posted. The same wasn’t true of feature requests, so that compromise couldn’t be made.

In case you were wondering, we were getting over a thousand posts into Post Approval a month by the end of the program. The fact that the badge was only awarded to 600 people across the entire program’s existence should hopefully be informative.

This is a relic from back when the forum was effectively a private club – Lounge should probably be deleted, and it would never have come into existence under the current forum’s leadership.

7 Likes

If a person is experienced aren’t they supposed to get more stuff???

1 Like

While I do agree that replies to feature requests should be unlocked (at least until new system comes in place, I’m not THAT patient to wait for over a month), I don’t think that making new topics in PF and opening Lounge to members is a good idea. A lot of people would post bugs in their code to engine bugs, and there’s kind of a special atmosphere in Lounge that I don’t want to be ruined.
Since even discussion was fully unlocked to members, I see no point in feature requests’ replies to be locked.

1 Like

You used to never be allowed to post into those categories as a new member. I was a new member for nearly a year.

I was paitent and got promoted because I had proven I could be trusted to contribute.

Maybe if you were paitent, you’d be promoted too?

I said that I’m not patient enough to wait for a new PA replacement, not the original PA queque length.

Roblox engineering creates and manages plugins, not Sages anymore. Just happened to be that sages were contracted to make a couple of them before.

3 Likes

Forum Feedback is for feature requests and bug reports for the Developer Forum so these address Developer Relations. This part of your response here is not desirable – let people give their opinion.

4 Likes

I don’t see what was wrong with the post approval system? I mean, Roblox makes a point to say that to become a regular; you must prove that you’re capable of creating well-made, constructive topics and discussion. How are we supposed to prove we’re capable of doing that if Members can barely post on the forum at all?

2 Likes