Hi all,

I'm proposing myself to be Drupal 7 maintainer. Now that I'm having more time to dedicate to Drupal again, I'm proposing my help.

The last projects I've been involved in are:

The last issue in Drupal 7 that I'm trying to fix: #2981726: Backport D8 html_tag element changes

I'm really motivated to push this forward and give a kind of "second life" to Drupal 7.

Thanks in advance :)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Pol created an issue. See original summary.

Manuel Garcia’s picture

Title: Drupal 7 maintainer proposal » Add Pol as Drupal 7 branch maintainer
Status: Active » Needs review
FileSize
464 bytes

+1, since David Rothstein is stepping down #2959509: Remove David Rothstein as Drupal 7 core maintainer

joseph.olstad’s picture

+1 yes!

ademarco’s picture

+1 for this!

donquixote’s picture

+1, if up to me.
From what I can tell, Pol cares about Drupal 7, and I expect that he will be a responsive and active maintainer.

For a "second life" of Drupal 7, there are some limits we currently accept, especially
- BC has top priority. Especially since we only have minor version vs patch version in D7.
- New features are introduced in D8 first, and are then backported to D7. Changes in D7 attempt to mimick D8 as far as possible.

We may negotiate the rigidity of these limits, but they won't ever fully go away I think.
I am curious where we are going with this.

Upchuk’s picture

+1!

joseph.olstad’s picture

patch #2 will have to be adjusted, Fabian is still an active maintainer. I suggest that we call private message Fabian and ask him if he's willing to share responsibilities with Pol . D7 still going to be around for at least another 10 years, in fact I'm currently building a partially new site based off of existing D7 components from another D7 site we have. While this organization does have a D8 site in the works, we've still got many D7 sites taking care of various parts of the business here at my new client. D8 and D7 will be side-by-side in my current clients business activities for years to come.

netlooker’s picture

I'm really lucky to work with Pol on a daily basis and what I can tell you is that Pol is a creativity volcano but for the most a soul mate really hard to find nowadays.
His way of approaching and solving problems is unique. He always put stress on the simplicity, creativity, scalability and following good practices. That explains why his projects are so successful and very well known across the Drupal Community. If you are searching for someone, who can lead/support the D7 core maintenance you can't find a better candidate.

You can also count on his fast feedback as he likes to share his knowledge, experience and passion for all of the things that he's involved in.

To recap, unique, reliable, old school, full-blown geek always open and ready for new challenges. A massively big +1 for this initiative.

hernani’s picture

I have knonw Pol for many years and I have been lucky to have him as a colleague in the last months. Pol is very interested in D7 and he cares tremendously about everything he gets involved in.
+1 definitely to have him as a maintainer.

David_Rothstein’s picture

Title: Add Pol as Drupal 7 branch maintainer » Add Pol as provisional Drupal 7 branch maintainer
Category: Bug report » Task
Status: Needs review » Reviewed & tested by the community
FileSize
478 bytes

This happened, according to https://groups.drupal.org/node/521072 -- congratulations!

But it looks like it's not in MAINTAINERS.txt yet, so here's an updated patch. Technically a "provisional" maintainer according to the above post, so I added the word "provisional" in front (based on how the Drupal 8 MAINTAINERS.txt does it).

Fabianx’s picture

Issue tags: +Pending Drupal 7 commit

Yep, let's commit that.

Pol’s picture

Fabianx’s picture

Status: Reviewed & tested by the community » Fixed
Issue tags: -Pending Drupal 7 commit

Pushed to 7.x

  • Fabianx committed bfefcae on 7.x
    Issue #2982027: Add Pol as provisional Drupal 7 branch maintainer
    

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.