[1.x] Drupal Open Source Dashboard

Thank you for applying!

Please read Review process for security advisory coverage: What to expect → for more details and Security advisory coverage application checklist → to understand what reviewers look for. Tips for ensuring a smooth review → gives some hints for a smoother review.

The important notes are the following.

• If you have not done it yet, you should run phpcs --standard=Drupal,DrupalPractice on the project, which alone fixes most of what reviewers would report.
• For the time this application is open, only your commits are allowed.
• The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status won't be changed by this application and no other user will be able to opt projects into security advisory policy.
• We only accept an application per user. If you change your mind about the project to use for this application, or it is necessary to use a different project for the application, please update the issue summary with the link to the correct project and the issue title with the project name and the branch to review.

To the reviewers

Please read How to review security advisory coverage applications → , Application workflow → , What to cover in an application review → , and Tools to use for reviews → .

The important notes are the following.

• It is preferable to wait for a Code Review Administrator before commenting on newly created applications. Code Review Administrators will do some preliminary checks that are necessary before any change on the project files is suggested.
• Reviewers should show the output of a CLI tool → only once per application.
• It may be best to have the applicant fix things before further review.

For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues → .

For these applications, we need a project where, in at least the branch used for the application, most of the commits (if not all the commits) have been done from the user who applies.
The purpose of these applications is reviewing a project to understand what the person who applies understands about writing secure code that follows the Drupal coding standards and correctly uses the Drupal API, not what all the project maintainers collectively understand about those points.

This application can only continue with a project (and a branch) where all the commits (or the majority of the commits) have been done by you.

Hi, thanks for the review and suggestions.

I'm not sure I understand the last one, related to only my commits.

I do not have any dedicated module/theme, where only I'm the owner - all my modules are written with co-maintainers.

Maybe the gitlab page with all my activities might work here? - https://git.drupalcode.org/driverok

Thanks!

On the branch used for this application there are:

• nine commits authored by SAVEL →
• seven commits authored by dmitry.korhov →
• eight commits authored by you

That means that most of the commits have been authour by SAVEL, who could eventually apply using that project.

Who is the project owner is not relevant for these applications. We just review a project's files to see what the person who applies understand about writing secure code that follows the Drupal coding standards and correctly uses the Drupal APIs. This is not possible when commits have been authored by other people.

Could the role be granted to the SAVEL → instead?

Should we create a new issue or it could be handled in the scope of this one?

Thanks!