avpaderno → changed the visibility of the branch 8.x-1.x to hidden.
Is this still an issue for supported releases?
Since patches are no longer testes, a merge request must be provided.
Since patches are no longer tested, a merge request needs to be provided.
No PHP_CodeSniffer error/warning has been reported by GitLab CI before doing any change.
avpaderno → changed the visibility of the branch 3358998-gitlab-ci-reports to hidden.
avpaderno → changed the visibility of the branch 3358998-dev to hidden.
avpaderno → changed the visibility of the branch 3349221-gitlab-ci-reports to hidden.
The merge request fixes all the PHP_CodeSniffer errors/warnings reported by GitLab CI.
Since patches are no longer tested, a merge request needs to be provided.
avpaderno → changed the visibility of the branch 3370016-fix-issues-by-phpcs to hidden.
avpaderno → changed the visibility of the branch 3370016-gitlab-ci-reports to hidden.
avpaderno → changed the visibility of the branch multi_region-3370016-3370016-fix-issues-by-phpcs to hidden.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue because there has not been any follow-up action as described in How to become project owner, maintainer, or co-maintainer → .
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
I am closing this issue because there has not been any follow-up action as described in How to become project owner, maintainer, or co-maintainer → from the person who opened this offer.
Since patches are no longer tested, it is necessary to provide a mere request.
This is the message I sent.
Hello Nikhil,
I am contacting you because Pablo ( https://www.drupal.org/u/plopesc → ), who is already co-maintainer for Feature toggle ( https://www.drupal.org/project/feature_toggle → ), a project you created for which you are project owner and maintainer, offered to become maintainer.
May you post a comment on https://www.drupal.org/project/projectownership/issues/3520275 💬 Offering to co-maintain Feature toggle with Edit permission Active about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Pablo will be probably made maintainer.Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.
I am contacting all the people who can administer co-maintainers/maintainers for the project.
As last note: This offer is about being maintainer, which is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3520275 💬 Offering to co-maintain Feature toggle with Edit permission Active . We need this to know it was intentional and not a misunderstanding on what the offer required.Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator
The status has been changed because we are waiting for a reply.
Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.
TechNikh logged in at least once in the past year. I am going to contact him.
The project link is https://www.drupal.org/project/feature_toggle → .
This thread has been idle, in the Needs work state with no activity for more than eight months; the application has been created more than 12 months ago. Therefore, I marked it as Closed (won't fix).
If this is incorrect, and you are still pursuing this application, please feel free to re-open it and set the issue status to Needs work or Needs review, depending on the current status of your code.
avpaderno → changed the visibility of the branch 3427513-gitlabci-reports to hidden.
The PHP_CodeSniffer errors/warnings have been already fixed, as GitLab CI does not report any PHP_CodeSniffer error/warning without doing any change.
avpaderno → changed the visibility of the branch 3427513-gitlab-ci-reports to hidden.
Since patches are no longer tested, a merge request needs to be provided.
Shared accounts cannot commit code on drupal.org repository. This means they cannot be used for these applications.
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, enable GitLab CI for the project, and fix what reported from the phpcs job. This help to fix most of what reviewers would report.
- For the time this application is open, only your commits are allowed. No other people, including other maintainers/co-maintainers can make commits.
- 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.
- Nobody else will get the permission to opt projects into security advisory policy. If there are other maintainers/co-maintainers who will to get that permission, they need to apply with a different module.
- 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. The configuration used for these tools needs to be the same configuration used by GitLab CI, stored in the GitLab Templates repository.
- 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 → .
Since patches are no longer tested, a merge request should be provided.
Nothing of what you describe changes moving the documentation pages in the repository, to which any project maintainer for the Drupal.org project ownership would have access, especially when they are project moderators or have a higher role.
That documentation page has been created time ago to describe what people who wanted to become co-maintainer/maintainer or project owner should do, such which title give to the issue, how long the issue must be kept in the project issue queue before moving it, who can move the issue, what can be changed in the issue after it was created and from who can be changed. It does not say that a project moderator, finding an issue for an offer to become maintainer created the day before, cannot contact the project maintainers.
What the documentation page says does not change moving it to a repository, nor does the nature of that documentation page change because it is moved to a repository.
Currently the only documentation available regarding the process to adopt a module are located on D.O. in a location where anyone can edit them. This raises questions about the accuracy of the documents at any given moment.
Is there any edit which defaced the documentation page? For what I recall, that never happened.
It is not necessary to move the documentation to GitLab Pages. All the project moderators have the permissions to use the Full HTML format, which cannot be used from people without specific roles.
We do not look at the code posted as attachment. We need a project link for a project for which you made commits.
https://www.drupal.org/project/rankcrew →
does not contain enough PHP code, as a previous comment reported.
I published 🐛 Deprecation Warning for Nullable Parameters in PHP 8.4 Active , which was posted before this request, and confirmed the account.
Now that patches are no longer tested, a merge request is necessary.
I added krakenbite as co-maintainer.
I added krakenbite as co-maintainer.
Showing a link to a documentation page require code change in Drupal core.
We only review projects with commits from the person who created the application.
The Project available for adoption issues were not supposed to be keep open for more than 2 years.
Issues for becoming maintainers/co-maintainers need to be first open in the project issue queue and kept there for at least 14 days.
I am closing this automatic issue, which has been created four years ago. These issues were supposed to be closed after two years.
I published ✨ Add support for form-action directive Needs work and ✨ Add support for form-action directive Closed: duplicate and confirmed the account.
Now that patches are no longer tested, a merge request is necessary.
More importantly, is the account used to create this application shared?