Thank you for your contribution and for your patience with the review process!
I am going to update your account so you can opt into security advisory coverage any project you create, including the projects you already created.
These are some recommended readings to help you with maintainership:
- Dries → ' post on Responsible maintainers
- Maintainership →
- Git version control system →
- Issue procedures and etiquette →
- Maintaining and responding to issues for a project →
- Release naming conventions → .
You can find more contributors chatting on
Slack →
or
IRC →
in #drupal-contribute. So, come hang out and
stay involved →
!
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 also all the reviewers for helping with these applications.
Thank you for your contribution and for your patience with the review process!
I am going to update your account so you can opt into security advisory coverage any project you create, including the projects you already created.
These are some recommended readings to help you with maintainership:
- Dries → ' post on Responsible maintainers
- Maintainership →
- Git version control system →
- Issue procedures and etiquette →
- Maintaining and responding to issues for a project →
- Release naming conventions → .
You can find more contributors chatting on
Slack →
or
IRC →
in #drupal-contribute. So, come hang out and
stay involved →
!
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 also all the reviewers for helping with these applications.
Thank you for your contribution and for your patience with the review process!
I am going to update your account so you can opt into security advisory coverage any project you create, including the projects you already created.
These are some recommended readings to help you with maintainership:
- Dries → ' post on Responsible maintainers
- Maintainership →
- Git version control system →
- Issue procedures and etiquette →
- Maintaining and responding to issues for a project →
- Release naming conventions → .
You can find more contributors chatting on
Slack →
or
IRC →
in #drupal-contribute. So, come hang out and
stay involved →
!
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 also all the reviewers for helping with these applications.
Thank you for your contribution and for your patience with the review process!
I am going to update your account so you can opt into security advisory coverage any project you create, including the projects you already created.
These are some recommended readings to help you with maintainership:
- Dries → ' post on Responsible maintainers
- Maintainership →
- Git version control system →
- Issue procedures and etiquette →
- Maintaining and responding to issues for a project →
- Release naming conventions → .
You can find more contributors chatting on
Slack →
or
IRC →
in #drupal-contribute. So, come hang out and
stay involved →
!
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 also all the reviewers for helping with these applications.
The status is Postponed 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 that a project moderators' action is required.
This is the message I sent.
Hello #maintainer,
I am contacting you because Joseph ( https://www.drupal.org/u/josepholstad → ) offered to become maintainer for Youtube Gallery ( https://www.drupal.org/project/youtube_gallery → ), a project you created for which you are project owner and sole maintainer.
May you post a comment on https://www.drupal.org/project/projectownership/issues/3546332 💬 Offering to maintain Youtube Gallery 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, Joseph 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.
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/3546332 💬 Offering to maintain Youtube Gallery 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
I will handle this later this afternoon. The project owner logged in at least once in the past three months.
The status is Postponed 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 that a project moderators' action is required.
This is the message I sent.
Hello Rich,
I am contacting you because Sven ( https://www.drupal.org/u/svendecabooter → ) offered to become co-maintainer for Webform Composite Tools ( https://www.drupal.org/project/webform_composite → ), a project you created for which you are project owner and sole maintainer.
May you post a comment on https://www.drupal.org/project/projectownership/issues/3545958 📌 Offering to co-maintain webform_composite 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, Sven will be probably made co-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.
As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3545958 📌 Offering to co-maintain webform_composite 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 project link is https://www.drupal.org/project/webform_composite → .
I confirmed the account, since creating an organization node requires a confirmed account.
What I reported in my previous comment still holds true. Taking out boiler-plate code, this is the only PHP code to review.
public function settingsForm(array $form, FormStateInterface $form_state) {
$form['replace_empty_token'] = [
'#type' => 'checkbox',
'#title' => $this->t('Replace empty tokens'),
'#description' => $this->t('Remove tokens from text if they cannot be replaced with a value'),
'#default_value' => $this->settings['replace_empty_token'],
];
return $form;
}
public function process($text, $langcode) {
$node = $this->routeMatch->getParameter('node');
if (!empty($node)) {
$token_data = ['node' => $node];
}
else {
if ($this->moduleHandler->moduleExists('group')) {
$group = $this->routeMatch->getParameter('group');
if (!empty($group)) {
$token_data = ['group' => $group];
}
}
}
if (!empty($token_data)) {
$token_options = ['clear' => $this->settings['replace_empty_token']];
$text = $this->token->replace($text, $token_data, $token_options);
}
return new FilterProcessResult($text);
}
- The following points are just a start and don't necessarily encompass all of the changes that may be necessary
- A specific point may just be an example and may apply in other places
- A review is about code that does not follow the coding standards, contains possible security issue, or does not correctly use the Drupal API
- The single review points are not ordered, not even by importance
src/Controller/MetricsController.php
$summary = [
'#type' => 'container',
'#attributes' => ['class' => ['drupal-metrics-summary']],
'db_size' => [
'#markup' => '<strong>Total Database Size:</strong> ' . $this->formatBytes($totalSize),
],
Every string shown in the user interface should be translatable.
Starting with Drupal 10, there is the ByteSizeMarkup class, which can be used instead of $this->formatBytes().
drupal_metrics.info.yml
core_version_requirement: ^9 || ^10 || ^11
Now that Drupal 8 and Drupal 9 are no longer supported, new projects should no longer be compatible with those Drupal versions.
In the merge request I created, GitLab no longer reports PHP_CodeSniffer errors/warnings.
Now that patches are no longer tested, a merge request should be provided.
src/Controller/TagsOverviewController.php
$instance->stringTranslation = $container->get('string_translation');
The code should call StringTranslationTrait::setStringTranslation()
src/Form/TagsOverviewTermMergeForm.php
The class uses only a method from the parent class, and it duplicates properties already defined from the parent class, which also exposes methods to access those properties. Either the class does not extend FormBase, or it does not duplicate the parent class's properties.
// Validação: se não houver operações, informar o usuário e interromper.
if (empty($operations)) {
$this->messenger()->addMessage($this->t(
'No operation was created: no fields were found for merging or no terms were marked for removal after the merge.'
), 'warning');
return;
}
// Merge dos dois valores no parâmetro term_ids.
$termIdsParam = implode(',', [$removeTerms, $targetTid]);
// Monta a URL de redirecionamento.
$url = $this->urlGenerator->generateFromRoute('taxonomy_overview.group_similar.merge_form', [
'taxonomy_vocabulary' => $vocabulary,
'term_ids' => $termIdsParam,
]);
// Redireciona o usuário.
$response = new RedirectResponse($url);
$response->send();
Comments need to be in English.
composer.json
There is no need to duplicate the core requirements already given in the .info.yaml file: The drupal.org Composer façade will automatically add in the composer.json file the Drupal core requirements found in the .info.yaml file.
taxonomy_overview.info.yml
core_version_requirement: ^9 || ^10 || ^11
Now that Drupal 8 and Drupal 9 are no longer supported, new projects should no longer be compatible with those Drupal versions.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a project owner, maintainer, or co-maintainer → .
How to become project owner, maintainer, or co-maintainer → describes what to do in the case maintainers do not reply, or they do post a comment, but they do not further comment to decline or accept the offer.
The question asked on April 17, 2024 was answered on April 24, 2024. Since then, almost a year and a half passed.
If this issue is not moved to the Drupal.org project ownership queue, the issue is waiting for an action from the maintainers of this project.
Since this project is covered from the security advisory policy, project moderators will not add as maintainers/co-maintainers (nor project owners) people who cannot opt projects into security advisory coverage.
If this issue were moved to the Drupal.org project ownership queue, it will be moved back in this project queue.
check_plain() should be sufficient to avoid any issue.
Given that a development version has been updated April 29, 2025, I would say the project is still maintained.
(I am interested in this as maintainer of the Seven theme, now removed from Drupal core, and maintained as contributed project.)
The issue summary says:
When file-link used by image_widget, file_size should always be displayed, but there are other uses for this template such as by the file_table formatter, which displays file size in a separate column.
It does not seem a matter of checking the value of file_size in the template file, but rather to know which formatter is using that template file, or use two different template files.
The full text is the following one, and it is given in the Interfaces within non-experimental, non-test modules not tagged with either @api or @internal point.
Where there is a 1-1 relationship between a class and an interface, inherit from the class. Where a base class or trait is provided, use those. This way your class should inherit new methods from the class or trait when they're added.
It does not say the base class must be used; it certainly does not say to duplicate code and properties the parent class has, which is what prompted what I said in comment #3.
The example I made does not cause any harm. Using different HTML tags, it could be possible to make the profile page render not correctly, at the point that parts of the page would not be usable.
Is it expected that the entered value can contains HTML markup?
If I enter </code>avpaderno_<code>avpaderno_</code> with the current code, which calls l(), I get the following.
With the changed code, I guess I would get avpaderno_avpaderno_.
I published ✨ API upgrading and default thumbail when adding content Active and confirmed the account.
The project does not have maintainers, and its issue queue has been disabled. I made krystalcode the new project owner.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a project owner, maintainer, or co-maintainer → .
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.
Furthermore, since this project is covered from the security advisory policy, project moderators will not add as maintainers/co-maintainers (nor project owners) people who cannot opt projects into security advisory coverage.
If this issue were moved to the Drupal.org project ownership queue, it will be moved back in this project queue.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a project owner, maintainer, or co-maintainer → .
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.
I am closing this issue, since it has been created about three years ago, and no maintainer has been successfully added using this issue.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a 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.
The purpose of the automatically-created issues tagged Project available for adoption was to make easier to adopt a project which needed to be ported to Drupal 8, and accelerate the porting to Drupal 8, avoiding the project would become unsupported. Now that Drupal 8 is no longer supported, and projects without a release (or a development version) for supported Drupal versions are already marked unsupported, porting a project to Drupal 8 or higher versions is not a sufficient priority to appoint maintainers using an adaptation of the existing process for appointing new maintainers.
People who want to be appointed maintainers need to follow the usual procedure described in Offering to become a project owner, maintainer, or co-maintainer → .