I am interested in using this namespace for a new annotation-based project. Since the project is currently seeking a new maintainer and has minimal usage, I would like to take over as the owner and start a fresh codebase for Drupal 11.

Comments

niklp created an issue. See original summary.

niklp’s picture

Forgot to add, I have attempted to contact the project owner via:
- contact form
- slack
- linkedin

All attempts were made days in advance of originally opening this issue.

Link to existing project: http://drupal.org/project/annotations

I have an existing repo that I have developed, waiting to go into this namespace at https://github.com/NikLP/annotations

niklp’s picture

Title: Project maintainer request » Offering to maintain Entity Annotations
Project: Annotations » Drupal.org project ownership
avpaderno’s picture

Version: 8.x-1.x-dev »
Component: Miscellaneous » Maintaining offer
Category: Support request » Task
avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Active » Fixed

kkumaren has last logged in more than a year ago. I added niklp as maintainer.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

niklp’s picture

Status: Fixed » Active

Hi, sorry if I made an error of judgement here - I was hoping to have the ownership transferred completely as the project seems like abandonware. Is this possible? As much for security as anything else.

avpaderno’s picture

Title: Offering to maintain Entity Annotations » Taking over the Entity Annotations namespace
Project: Drupal.org project ownership » Annotations
Version: » 8.x-1.x-dev
Component: Maintaining offer » Miscellaneous
Assigned: avpaderno » Unassigned
Category: Task » Support request

I apologize: Since this issue is about taking over a namespace, I have to revert the changes and move the issue back to the project issue queue.

A request for taking over a namespace is different from a request to be added as maintainer, since in the first case the existing project is replaced by a different project, while in the latter case the existing project is preserved, and (possibly) ported to a new Drupal release.

This request can be moved back here after 14 days.

niklp’s picture

Not wishing to disrupt the process, but I followed it to the letter.

The request was always for ownership, but the docs here state (under "Offering to be the new project owner"), "For the title, use Offering to maintain [PROJECT_NAME]." which I did, if - unexpectedly - erroneously. The OP specifically states " I would like to take over as the owner and start a fresh codebase".

I was told the process was stringent and I've followed it exactly, so the two weeks extra wait unfortunately seems punitive, in honesty. The wait is hampering development as I wish to break this module [suite] into submodules, which doesn't make sense until the core stuff has a home.

Not expecting special treatment but something seems broken in the mechanism here :(

hestenet’s picture

Hm. Chiming in here. As far as I can tell this issue properly followed the process outlined in:
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...

And the issue description does specifically mention the new codebase.

If we're going to be strict about having a different title for full namespace requests vs being added as a co-maintainer we need to update the docs, but I don't think we should penalize the requester.

One 14 day period is enough whether their intent was to co-maintain or completely replace - as long as that intent is stated in the issue description.

(However, thank you for being especially careful @avpaderno)

Proceeding with the full changeover, including removal of prior maintainer.

hestenet’s picture

Title: Taking over the Entity Annotations namespace » Request to take over the Entity Annotations namespace
Project: Annotations » Drupal.org project ownership
Version: 8.x-1.x-dev »
Component: Miscellaneous » Maintaining offer
Assigned: Unassigned » hestenet
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

avpaderno’s picture

Taking over an obsolete project's namespace describes what to do in this case. The issue title for this case is Taking over the [PROJECT_NAME] namespace, where [PROJECT_NAME] is the project name, which makes clear that the intent is not being added as maintainer, to continue developing the existing project, which could also mean porting the project to a supported Drupal version, but being added as project owner to create a new project which just share the namespace with the existing project.

That is an important difference which needs to be made explicit in the issue title.

hestenet’s picture

Ahhhh. It is in the docs.

Okay, I'm going to update the documentation to make that more clear/easier to find.

I think this issue can stand and remain closed. If the original maintainer reappears, I'm happy to talk to them.

niklp’s picture

Thanks both, sorry for the confusion.

avpaderno’s picture

Component: Maintaining offer » Ownership transfer
niklp’s picture

Not sure if this is the place to ask, but, additionally I would like to change the name of this project to "Annotations" but this project (defunct) is blocking: https://www.drupal.org/sandbox/alfonso_ma/2101417

Is there a way to achieve my goal or should I just chalk it down to hubris and move on? :)

avpaderno’s picture

Category: Support request » Task

That sandbox project has not been developed since 2013. It cannot be changed to a full project, since its namespace would conflict with the Entity Annotations project namespace.

I can rename that sandbox project.

avpaderno’s picture

I renamed the sandbox project Node Annotations.

niklp’s picture

Beautiful, thank you very much :)

Status: Fixed » Closed (fixed)

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