Forge components approval

By Carlos Henriques on 23 Jun
To improve Forge quality, which in my opinion is decreasing day by day, OutSystems should moderate all the new components submissions.

Instead of being instantly available after submission, they should wait for someone from OutSystems to check them and approve.
This would avoid the submission of tests, spam, exploits, redundant components, etc.
I've been begging for this in other Ideas and Forum posts.  There is so much garbage out there, especially recently, it's really crazy no one has addressed this in the three years I've been using the platform.

Even the good components need more scrutiny.  Most have no documentation, no sample pages, etc.  If its just a matter of someones time, I'd be happy to contribute a few hours.
Agreed with curt ,forge components should be verified before they available publically for download and also if a component doing the same functionality is laready avilable in forge, the new component should grouped under the old verified component so that while searching the user can take decission which one to use.
Something else that may help to reduce clutter:

Have the ability to control/limit visibility of a newly posted forge item.  If a newly posted forge item is still in development and needs to be shared with a team, allow the uploader to limit visibility to self, team, or everyone.  Once the item goes to a production release, it can automatically be visible to everyone. 

Implement some data/content validation rules before an item can be made visible to everyone such as a mandatory description of what the item does, instructions on how to use (maybe optional), keyword tags to help categorize the item. 
J.24 Jun
I agree.

we need some better mechanisms to create a better forge.

I agree.

Verified before availability is a good solution or you add a button for the community to mark it as inappropriate or incomplete. The inappropriate button should redirect to QA of Outsystems to validate the added value of the forge component and they can decide to remove it and the incomplete should be sent to the developmentteam of the component to tell them what is missing.

Kind regards,


IMO, only new projects should be evaluated.
Once a project is approved into Forge, new versions submitted to the same project wouldn't need to be approved.
That surely would improve Forge quality whilst not having the need for the team to allocate too many resources for the reviewing process.
See thi srecent example ..someone uploaded a test componenet which says nothing about it.

Related idea: Include a reporting system.
Perhaps we should be less strict: add an approval system, and only show approved components by default, but still allow unapproved components. Of course we already have the rating system, which helps somewhat.