David, please create a release for the new driver branch, 1.0.x. I will send you a message through your Drupal.org profile as well.

CommentFileSizeAuthor
#9 Screenshot.20200515.1112.png24.8 KBavpaderno

Comments

Beakerboy created an issue. See original summary.

beakerboy’s picture

beakerboy
Primary language English
Location Kentucky
commented
Project: Drupal driver for SQL Server and SQL Azure » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Ownership transfer
Assigned: david_garcia » Unassigned
Category: Task » Support request

The sqlsrv project has been basically abandoned for some time. The result from a previous ownership transfer request #3056186: Offering to maintain Drupal driver for SQL Server and SQL Azure was write access to the git repository, but no ability to manage the project page. This means I am unable to add information to the page or create releases.

I have again contacted the primary contact for this project and have again received no response. Could I be given the ability to manage the project page, so I can create a release for this project that is compatible with the Drupal 8 -> Drupal 9 transition and beyond?

beakerboy’s picture

beakerboy
Primary language English
Location Kentucky
commented
Title: Create a release for the new semantic version branch, 1.0.x » Offer to maintain Drupal driver for SQL Server and SQL Azure
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: Ownership transfer » Maintaining offer
Assigned: Unassigned » avpaderno
Category: Support request » Task
Status: Active » Postponed

I sent a message to the current project owner.

Hi Garcia,

I am writing you because the latest co-maintainer added, Beakerboy (https://www.drupal.org/u/beakerboy), asked to get more permissions on the "Drupal driver for SQL Server and SQL Azure" module (https://www.drupal.org/project/sqlsrv), such as the permission to edit the project page and create new releases.
May you post a comment on https://www.drupal.org/project/projectownership/issues/3131421 which explicitly states if you accept to give him more permissions or you decline it? We need a publicly visible comment in that issue. Other way to reply, such as replying back to this email, won't be considered.

Without a comment in the next 14 days, Beakerboy will get more permissions as requested by him.

Best regards,
kiamlaluno
-- Drupal.org webmaster
-- Drupal.org Git administrator

I am post-poning this issue for the time we wait for a reply.

david_garcia’s picture

david_garcia commented

I gave @beakerboy full permissions for the project. Thanks for your effort.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed » Fixed

Thank you for your quick reply!

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented

For the record, he has not "full permissions": https://www.drupal.org/project/sqlsrv/maintainers.json

He still cannot "administer maintainers". I.e. he is still just a co-maintainer, not a maintainer. See the introduction here for definitions: https://www.drupal.org/node/251466#intro

This is a "maintaining offer" and IMHO, the correct status is not yet "Fixed".

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I should have checked it was done as the comment said.
I fixed that, since the project owner accepted to give Beakerboy full permissions, which by our terms means all the permissions we can assign for a project.

Thank you for noticing this.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
StatusFileSize
new Screenshot.20200515.1112.png24.8 KB

(To document Beakerboy is now maintainer of the project, this is the screenshot I took after giving him full permissions on the project.)

screenshot

beakerboy’s picture

beakerboy
Primary language English
Location Kentucky
commented

Thanks for your help everyone. I’m looking forward to getting everything ready for Drupal 9!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.