Add poker10 as a provisional D7 maintainer

+1 Juraj Nemec (poker10) is really great and I would be very happy to have him as provisional co-maintainer on board.

First of all I would like to thank @mcdruid and @Fabianx for this proposal and for the vote of confidence in me. It is an honor for me and I am excited about the opportunity to help Drupal 7 and the whole Drupal community in such a role.

What can I tell about myself? I have 10+ years of experience working with Drupal 5/6/7/8/9 on different scale projects, including custom modules/themes development, performance tuning, website deployment and so on. Here is a brief summary of my recent contributions to the Drupal 7 core:

• PostgreSQL tests in D7 core were broken for some time and it was causing problems, as all core patches were not tested against PostgreSQL. I helped here with several issues to fix the PostgreSQL tests. See: #710858: Meta issue: fix the remaining PostgreSQL bugs
• I helped to fix the long-lasting bug with the long PostgreSQL identifiers, which was also causing problems in some specific D7 environments (not only in the tests). See: #998898: Make sure that the identifiers are not more the 63 characters on PostgreSQL
• I was extensively testing multiple large-scale sites on PHP 8.1 trying to find any PHP 8/8.1 compatibility issues and helped to fix them. See: #3224299: [META] Make Drupal 7 core compatible with PHP 8.1
• I have contributed to fix/backport multiple PostgreSQL performance issues to get them ready to D7 core, which resulted in that Simpletest PostgreSQL tests run time decreased from approx. 24 minutes to 8 minutes. This reduced the load of D.O infrastructure and also waiting time for core contributors while testing patches on PostgreSQL. These fixes also had performance benefits for all D7 sites, though smaller. See: #3259739-4: [meta] Priorities for 2022-06-01 release of Drupal 7
• I have added tests to several issues / patches so that they can be included in one of the potential future releases

I plan to focus on stability and priority should be bug fixes and PHP / database issues. PHP 8.2 is coming - there will be a lot of work especially with this: #3275851: [META] Fix PHP 8.2 dynamic property deprecations and I am ready to help there, where possible. Obviously I am ready to consult any questions or complicated situations with @mcdruid / @Fabianx to secure the future stability of D7 and secure smooth operation of D7 for all sites. There are still more than 500k D7 sites running, so I understand that this role includes big responsibility to make the right decisions. I have also started to clean up the D7 issue queue a little bit (step by step).

So to the #4:

@poker10, Can you read over that governance doc when possible, and confirm here on the issue that you fit the description and are willing to have those responsibilities?

I confirm that I have read all governance documents, I understand them and fit the description described there. I am ready and willing to have those responsibilities and will do my best to make the Drupal community satisfied (as far as possible, of course :) ).

@poker10: thank you for offering to help maintain Drupal 7. I reviewed/discussed your application with a number of people, and we're happy to add you to the Drupal 7 Core Committer Team. 🎉 Thank you so much for helping with Drupal 7!

Thanks everyone!

@poker10 , congratulations and thanks!

Congratulations @poker10! Thanks for all the great improvements you added to Drupal 7 lately, it's really appreciated.

Yes, congratulations @poker10, well deserved recognition.