[D7] MTCaptcha

Thank you for applying! I added the PAReview checklist link. Reviewers will check the project and post comments to list what should be changed.

If you haven't done it, yet, please check the PAReview report and fix what needs to be fixed. There could be some false positives; verify that what reported is correct, before making any change.

The branch name (7.x) is wrong. A correct branch name would be 7.x-1.x. You need to create the correct branch, make it the default one, and then delete the wrong branch.

Also, the module files should not be in the mtcaptcha/mtcaptcha directory, but directly in the repository root directory.

The license file needs to be removed, as Drupal modules, themes, installation profiles, and distributions hosted on drupal.org are licensed under the same license used from Drupal, which isn't Apache License version 2.
Agreeing to the Git access agreement, you agreed also to the following:

I will only commit code licensed as GPL-2.0+ and non-code assets licensed with GPL friendly licenses to Drupal project repositories.

A correct branch name is 7.x-1.x or 7.x-2.x, not 7.x-2.0, which is a tag name. The x in 7.x-1.x doesn't mean replace it with any number.

The default branch is set in https://www.drupal.org/node/3124085/edit/default-branch. Before a branch can be deleted, the correct branch must be created and made the default one; without changing the default branch, a branch cannot be deleted.

Here is the patch with the PHPCS fixes required for the PAReview & Coding standards issues.

One other issue is still pending. Here is the patch for the pending item.
https://pareview.sh/pareview/https-git.drupal.org-project-mtcaptcha.git-...

Note: Using the commit command from the ticket, so that you give credits to the author.

The task of reviewers is pointing out what needs to be changed, not providing patches.

Thank you for the contribution!

Review of the 7.x-1.x branch (commit 7c6b620): It looks good to me.

Thank you for your contribution! I am going to update your account.

These are some recommended readings to help with excellent maintainership:

• Dries' post on Responsible maintainers
• Best practices for creating and maintaining projects
• Maintaining a drupal.org project with Git
• Commit messages - providing history and credit
• Release naming conventions.
• Helping maintainers in the issue queues

You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

I thank all the dedicated reviewers as well.