Stemming from #2453587: [policy, no patch] Changes to the project application review process, work out ways to further simplify and improve both the project application review process and maintaining the quality of an existing project. Part of the desire to improve both of these is the perception, warranted or not, that people who have been around for a few years have their projects held to a different standard than newcomers. Anyone today attempting to have their sandbox promoted to a full project for the first time has a detailed and length process by which their module is very heavily analyzed for code quality and bugs, something that most members of the community since before ~2010 (not sure exact date of the new policy) did not have to go through.

The suggestion is to add automated coder-based reviewing part of the testing process, then mandate that all releases must past their tests & coder review. Because this would be applied across the board there could no longer be any claims of preferential treatment. Furthermore, having this testing in place would allow some of the project application requirements to be dropped, thus lowering the barrier to contributing.

Sub-tasks:

Comments

damienmckenna’s picture

Title: [policy, no patch] Simplify, automate project application & release processes » [policy, no patch] Simplify, automate parts of the project application & release processes
jthorson’s picture

gisle’s picture

+1 for closing as a duplicate.

jthorson’s picture

Status: Needs review » Closed (duplicate)

Really, anyone can do that. ;)

Not sure how I missed this one earlier!