Topic on Talk:Gerrit/Tutorial/Archive 2

The Gerrit setup process seems to be the main blocker inhibiting newcomers to help with development (once they managed to actively reach this page).

Are there any ongoing projects or issues or debate about either simplifying the process or replacing it?

For example by just using Visual Studio Code and git without Gerrit and/or a GUI that takes the user through a simple step-by-step process to download, install and configure everything that's needed? Using that GUI would not require technical expertise or much time and it would automatically solve/prevent any problems. It (e.g. a Qt one) could also get developed further to also set up other things needed for various WP development projects like the MediaWiki docker container etc. (note that it needs to internally do things like comparing hashsums which it could display)

I think the Gerrit requirements are the or one of the major technical(!) bottlenecks that cause the lack of developers (even though the technical aspects are not even half of the problem). If this hasn't been discussed so far which would be the best places to propose this?

Gerrit is maybe not the "main blocker" but data shows it is one obstacle. See GitLab consultation for ongoing work to replace it.

Thanks, yes it only seems to be the main blocker to me. Other obstacles once they managed to actively reach this page(!) are probably further down so less inhibitive because by then they already got started developing. GitLab would make things much easier (a GUI could be still be useful for the same reasons once GitLab is being used).

There should also be (shorter?) tutorial for people that don't want to install anything (want to edit by web, if it's possible).

And alternative way to request for smaller changes (why do I need to create an account to propose a change that has only few lines?).

There is Gerrit/Tutorial/tl;dr for "short". There is Gerrit/Tutorial#Editing via the web-interface for "web".

Why to create an account? Because of authorship (accountability) and licenses, basically. Size of a patch is unrelated.