Back to Ideas
32
Like
Follow Idea
Forge components approval
2338Views
17Comments
Implemented
Forge

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.

23 Jun 2016
Copy link to comment
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.
23 Jun 2016
Copy link to comment
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.
24 Jun 2016
Copy link to comment
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. 
24 Jun 2016
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP
I agree.

we need some better mechanisms to create a better forge.

24 Jun 2016
Copy link to comment
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,

Remco
24 Jun 2016
Copy link to comment
+1

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.
01 Jul 2016
Copy link to comment
See thi srecent example ..someone uploaded a test componenet which says nothing about it.

https://www.outsystems.com/forge/component/1411/TEST/


Regards
-PJ-
01 Jul 2016
Copy link to comment
Related idea: Include a reporting system.

https://www.outsystems.com/ideas/2520/report-inappropriate-threads-posts-projects-and-user-profiles
03 Jul 2016
Copy link to comment
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.
04 Jul 2016
Copy link to comment
2018-09-19 17-53-01
Alexandra (Brower) Bowen

What do you think is more effective and better? 1. A reporting tool, or 2. an approval process?


Perhaps there could be a "report" dropdown where the community can identify the urgency and type/reason for the report. 


To also broaden this a bit, (tip of the hat to @J.) - what other mechanisms do you think we need to create a better Forge?


Open to any ideas, and feedback!

-Alexandra

OutSystems Community Manager

04 Jan 2017
Copy link to comment

Hi Alex,

The report option would be cool for inappropriate or incomplete. 

Next to this there should be an option to mark as personal or private (available for a select group of people) because there are also items on the forge that are specifically created for a company or just to remove the IPP in order to move from personal license to enterprise license. 

Kind regards,

Remco

05 Jan 2017
Copy link to comment

Hi Remco,

"there are also items on the forge that are specifically created for a company"

If they are specific for a company then why share it in the Forge?


"or just to remove the IPP in order to move from personal license to enterprise license."

OutSystems support can do that for you.

08 Jan 2017
Copy link to comment

Hi Carlos,

I only wrote down what I see other people posting in the forge. I would like this to be fixed by Outsystems. There is too much stuff in the forge that is not useful for others. With approval before publishing or the possibility to report components that don't belong in the forgeto a moderator this can be solved. 

Kind regards, Remco

08 Jan 2017
Copy link to comment

In addition to this, make sure developers credit the work of the original developer (there are multiple developers that simply take another developer's code, and pass it off as their own!)

15 Jan 2017
Copy link to comment
Changed the status to
Working on it
expected delivery in Q3 2018

Hi Carlos and Followers, 

During this and next quarter, we will work hard to grow the forge into a marketplace of high-quality components.

We will:

  • Review supported components based on usage and criticality
  • Provide an additional trusted level, for open-source components curated by OutSystems
  • Clean low-quality components from the forge, either improving or dropping

So I have set the status to “Working on it”. We expect it to be ready during Q3. I’ll post an update once it’s done!

Cheers 

Ana Sequeira

02 May 2018
Copy link to comment

Great news.

02 May 2018
Copy link to comment
Changed the status to
Implemented
on 28 Nov 2018

we did it :)

03 Dec 2018
Copy link to comment