Proposal to make all core maintainers git vetted users

Events happening in the community are now at Drupal community events on www.drupal.org.
Posted by mpdonadio on November 13, 2014 at 7:10pm

Part of the project application review process is to ensure that users have a good grasp of Drupal concepts before we allow them to promote sandbox projects to full projects.

There are handful of core maintainers that are not git vetted users.

I propose the following:

We audit the MAINTAINERS.txt file for Drupal 7 and Drupal 8 and promote everyone who is a

  • Branch maintainer
  • Component maintainer
  • Module maintainer
  • Theme maintainer
  • Core mentoring lead
  • Initiative owner
  • Topic coordinator

That covers everyone listed in those two files. We trust these people enough to maintain Drupal itself, we should trust them enough to publish a Drupal module.

If we have enough consensus on this and no strong objections, and that we think all of these groups should be included, I will audit these two lists the weekend of 2014年11月21日 and promote everyone who needs it.

Comments

Yes, +1.

Posted by klausi on November 13, 2014 at 7:13pm

Yes, +1.

+1

Posted by jibran on November 13, 2014 at 7:30pm

Isn't this yet another

Posted by kreynen on November 13, 2014 at 7:55pm

Isn't this yet another example of large shops/Drupal's inner circle ignoring or bypassing the process they want to force other developers to follow?

Another way to look at this is if you are competent enough to contribute to core, creating a module and subjecting yourself to the review process should be trivial. It won't be, but it should be.

I've already posted about the method many large shops are using to avoid subjecting new developers to the review process.

Unless more people with experience contributing to other projects and communities are subjected to this process, I doubt it will ever improve.

The current waiting period for projects that don't review other projects for a "bonus" is > 8 months.

Is this trying to fix a

Posted by davidhernandez on November 13, 2014 at 11:21pm

Is this trying to fix a problem that doesn't exist? Did someone request this be done? I assume anyone listed in MAINTAINERS.txt already has whatever permissions they need to work. Otherwise, I agree with kreynen that everyone should be treated equally and should go through the same process. Part of the reason why the problems with the review process have existed so long is that community veterans didn't have to experience it.

Fabianx has applied recently:

Posted by klausi on November 13, 2014 at 11:42pm

Fabianx has applied recently: https://www.drupal.org/node/2355021
Looking at his code makes me smile because everything is written so well and I can hardly find anything to complain about.

IMO there are 2 reasons we should approve them immediately:

  • They already earned our trust and are our most valuable contributors. We put them in MAINTAINERS.txt because they know what they are doing and their work is exceptionally good and approved by the community.

  • They waste my time when I review applications. I could instead look at project applications of people that are new contributors and not well established yet.

Agreed!

Posted by pushpinderchauhan on November 14, 2014 at 4:28am

Pushpinder Rana

Should this be a codified

Posted by davidhernandez on March 20, 2016 at 5:30pm

Should this be a codified policy? Marc Drummond has also opened a project application and he certainly qualifies under the same standard as one of the Drupal 8 core component maintainers.

https://www.drupal.org/node/2682837

Code review for security advisory coverage applications

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

AltStyle によって変換されたページ (->オリジナル) /