Offering to maintain Drupal Tech Talk

Created on 12 July 2024, about 2 months ago
Updated 31 July 2024, about 1 month ago

I propose we transfer project ownership from marcvangent to bbrala. We talked about this on Slack. The project is now managed by a new list of people, and Marc is no longer involved. This issue is for that transfer.

It seems Marc cannot do this on his own. This issue is to confirm the transfer officially.

📌 Task
Status

Fixed

Component

Ownership transfer

Created by

🇳🇱Netherlands bbrala Netherlands

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @bbrala
  • Status changed to RTBC about 2 months ago
  • 🇳🇱Netherlands marcvangend Amsterdam

    I agree with the transfer of ownership to bbrala.

    In good open source tradition, the ownership comes with the requirement that if the new owner stops being involved in the Drupal Tech Talk, they will again transfer the ownership to the then organizer(s), under these same conditions.

  • Issue was unassigned.
  • 🇳🇱Netherlands bbrala Netherlands

    All good, agreed :) Moving to proper queue.

  • Status changed to Postponed: needs info about 2 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    May you provide the project link?

  • Status changed to RTBC about 2 months ago
  • 🇳🇱Netherlands bbrala Netherlands

    Sorry, assumed the issue move was enough.

    drupaltechtalk

  • Status changed to Fixed about 2 months ago
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    The project link is necessary to find the project page.
    Issues do not have a link to the project for which the issue has been created; they only have a link to the project where they actually are. 😉

    I changed ownership as requested, since marcvangend commented in this issue.

  • 🇺🇸United States cmlara

    @apaderno:

    Just a note, while it is much easier if applicants provide a link, you can obtain the project (for applications that have properly gone through the queue) by clicking View History > Date of an entry that was before the project moved to ownership Queue (the first post in this case). The project link will be in the breadcrumb.

    I could argue this should always be done as it adds an extra check that the issue was indeed created in the correct repo and not a repo with a very similar name in attempt to avoid a maintainer seeing the request (D.O. does not allow exactly the same name to my knowledge however hidden/less visible characters like spaces might be able to impact that).

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    @cmlara. You are right: The link to the project is kept in the revision. Thank you for pointing that.
    I have never checked because I always thought the revisions for issues could not be "trusted." See the issue title shown in the breadcrumb for the first revision , for example: It is the title I set, not the original title. (I could check what happens when an issue is moved back and forth between one or more issue queues.)

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

Production build 0.71.5 2024