Transfer request

Created on 17 January 2025, 3 months ago

I used the drupal.org contact form for @nashkrammer to request this namespace

📌 Task
Status

Active

Component

Miscellaneous

Created by

🇺🇸United States fathershawn New York

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

Comments & Activities

  • Issue created by @fathershawn
  • 🇺🇸United States fathershawn New York

    The `dynamic_yield` project consists of a one line README file created 4 years ago.

    My employer is sponsoring the creation on a module to integrate the Dynamic Yield personalization service with Drupal which we intend to contribute.

    I used the drupal.org contact form to contact the project owner over 2 weeks ago and have had no reply. It appears that this project is abandoned and I am requesting ownership so that we can use it for our contribution.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    I am moving back the issue to the project queue, since these requests need to stay in the project issue queue with the right title, for 14 days.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    These are the messages I sent.

    Hello Avinash,

    I am contacting you because Shawn ( https://www.drupal.org/u/fathershawn ) created an issue to take over Dynamic yield ( https://www.drupal.org/project/dynamic_yield ), a project you created for which you are project owner and maintainer, to create a different project which uses the same namespace.

    May you post a comment on https://www.drupal.org/project/dynamic_yield/issues/3500546 📌 Transfer request 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, Shawn will be probably made the new project owner and be able to commit the new project.

    Project moderators will not change the existing maintainers/co-maintainers.
    The purpose of requests to take over a namespace is to commit code for a different project, not creating a Drupal 9/10/11 release of an existing project; the new project could even have a totally different purpose.

    Best regards,
    Alberto Paderno
    -- Drupal.org project moderator
    -- Drupal.org site moderator

    Hello Nikunj,

    I am contacting you because Shawn ( https://www.drupal.org/u/fathershawn ) created an issue to take over Dynamic yield ( https://www.drupal.org/project/dynamic_yield ), a project for which you are maintainer, to create a different project which uses the same namespace.

    May you post a comment on https://www.drupal.org/project/dynamic_yield/issues/3500546 📌 Transfer request Active about accepting or declining the offer? The decision to accept the taking over is for the project owner, but the project owner could need to know if other maintainers have any plan for the existing project. A comment from you about that is well appreciated.

    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, Shawn will be probably made the new project owner and be able to commit the new project.

    Project moderators will not change the existing maintainers/co-maintainers.
    The purpose of requests to take over a namespace is to commit code for a different project, not creating a Drupal 9/10/11 release of an existing project; the new project could even have a totally different purpose.

    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 and move this issue to the Drupal.org project ownership queue, 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.

  • 🇺🇸United States fathershawn New York

    Thank you @avpaderno. I sent a similar message on Jan. 17 when I created this issue and attempted to follow the guidelines. Thank you for correcting our process. We will monitor for a response.

  • 🇮🇳India nikunjkotecha India, Gujarat, Rajkot

    Not sure why I didn’t get message from contact form before, I will check that separately.

    Please go ahead and transfer the namespace, I will make them project maintainers and later if they want can remove us.

  • 🇮🇳India nikunjkotecha India, Gujarat, Rajkot

    Maintainer added

    https://www.drupal.org/node/3108446/maintainers

    Thanks for reaching out and contributing to Drupal.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    This is not a request to be added as maintainer, but to take over the namespace used by this project, to create a completely different project. It means fathershawn is asking to be the new project owner, not a maintainer.

    Furthermore, as I explained in the message I sent, this is a decision only nashkrammer can take.

    The decision to accept the taking over is for the project owner, but the project owner could need to know if other maintainers have any plan for the existing project. A comment from you about that is well appreciated.

    I reverted the changes done.

  • 🇮🇳India nikunjkotecha India, Gujarat, Rajkot

    Hi Alberto,

    Apologies for quick reaction (not an excuse but it was early morning and I was just happy to let someone contribute).

    This was created by Avinash on my request, we both were working together at the time on the project. I am happy to try and connect with him to respond but I am sure he will have no problems as we both are no longer associated to the project and going to work on this.

    About taking over the namespace - is there something I or Avinash will have to do or that will be taken care of by you / moderator team?

  • 🇺🇸United States fathershawn New York

    Thanks @nikunjkotecha for the endorsement! The message I sent was to Avinash because of the policy @avpaderno stated in his comments.

    If the process is inflexible we can wait @avpaderno but I'd like to point out that I did attempt to follow the policy by contacting Avinash and by posting an issue that sat silently for more than the two weeks expected and that we are not truly proposing to "create a different project" as what exists is a placeholder: https://git.drupalcode.org/project/dynamic_yield.

    I appreciate your care in maintaining drupal.org and in protecting drupal sites against supply chain poisoning!

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    @nikunjkotecha If you are sure nashkrammer will not object about giving the namespace to somebody else, we can proceed.

    Only site moderators or project moderators can change the owner of a node, which is what is necessary in this case. Since neither of you are site moderators, there is nothing you can do in this case.

  • 🇮🇳India nikunjkotecha India, Gujarat, Rajkot

    I am sure he won't mind, as I said before it was me only who asked him as he was the developer for the module in the project.

    We didn't manage to push anything as our requirements were highly custom and we were not able to find a way to make something contributable.

    I don't have his number handy and I don't see him Drupal slack. I sent message to him in LinkedIn. IMO he has not responded since past 14+ days already so we are good to move forward.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    Perfect! 👍🏻

    I changed ownership as per this request.

  • 🇺🇸United States fathershawn New York

    Thank you very much, both of you :)

  • 🇮🇳India nashkrammer

    All ok for me. Thank you.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024