Return to Answer

An alternative approach to "create a full project on drupal.org", is to investigate the existing (+17K) contributed modules, and narrow them down to projects with status like:

• Seeking new maintainer (675 hits).
• Unsupported (1.514 hits).

From the search results that you get, verify if there is anything that has a "namespace" (= the machine name of your module) that might fit (or is close enough) to what your (new) module is about.

Then request the module's ownership to be treansfered, using these steps (in specified order):

1. contact the module owner via the contact form of that owner on Drupal.org, asking for the ownership to be transferred.
2. If current owner indicates to agree with a transfer, or if after 2 weeks you have not received any response to step 1, then file an issue on Drupal.org, to request the "ownership to be transfered" (include relevant communication from step 1 to motivate your request). Issue # 2367923 is an example of such issue.
3. The people handling the request from step 2 will then also try to contact the current owner (if you didn't get a reply to step 1.). And after a grace period of (about) 2 weeks, the project's ownership will be changed to you (unless there was some type of feedback from the current owner to not do so).
4. Do whatever you want to do with the module for which you became the new owner, without any review process involved. But make sure to:

• give credit to the previous owner somehow.
• NOT destroy any (GIT) history of the old version of the module.

The above period works fine, though it takes a little time (a few weeks at max) to complete all the steps ... And it has the advantage (I think) that you contribute a very little bit to reduce the amount of abonded-looking contributed modules.

PS: There are occasions where the current maintainer responds/reacts with something like "Hm, somebody interested in contributing to a 2nd live to a module I started ... how about I only grant co-maintainer status instead of transferring module ownership?". If that happens, then "you" have to decide if you yes/no are willing to accept that. A possible compromise in that case could be "how about we turn the table: I become owner, and make you (current owner) a co-maintainer".

An alternative approach to "create a full project on drupal.org", is to investigate the existing (+17K) contributed modules, and narrow them down to projects with status like:

• Seeking new maintainer (685 hits).
• Unsupported (1.524 hits).

From the search results that you get, verify if there is anything that has a "namespace" (= the machine name of your module) that might fit (or is close enough) to what your (new) module is about.

Then request the module's ownership to be treansfered, using these steps (in specified order):

1. Contact the module owner via the contact form of that owner on Drupal.org, asking for the ownership to be transferred.
2. If current owner indicates to agree with a transfer, or if after 2 weeks you have not received any response to step 1, then file an issue in the Drupal.org project ownership project (component = Ownership transfer), to request the "ownership to be transferred" (include relevant communication from step 1 to motivate your request). Issue # 2367923 is an example of such issue.
3. The people handling the request from step 2 will then also try to contact the current owner (if you didn't get a reply to step 1.). And after a grace period of (about) 2 weeks, the project's ownership will be changed to you (unless there was some type of feedback from the current owner to not do so).
4. Do whatever you want to do with the module for which you became the new owner, without any review process involved. But make sure to:

• give credit to the previous owner somehow.
• NOT destroy any (GIT) history of the old version of the module.

The above period works fine, though it takes a little time (a few weeks at max) to complete all the steps ... And it has the advantage (I think) that you contribute a very little bit to reduce the amount of abonded-looking contributed modules.

PS: There are occasions where the current maintainer responds/reacts with something like "Hm, somebody interested in contributing to a 2nd live to a module I started ... how about I only grant co-maintainer status instead of transferring module ownership?". If that happens, then "you" have to decide if you yes/no are willing to accept that. A possible compromise in that case could be "how about we turn the table: I become owner, and make you (current owner) a co-maintainer".

An alternative approach to "create a full project in drupal.org", is to investigate the existing (+17K) contributed modules, and narrow them down to projects with status like:

• Seeking new maintainer (675 hits).
• Unsupported (1.514 hits).

From the search results that you get, verify if there is anything that has a "namespace" (= the machine name of your module) that might fit (or is close enough) to what your (new) module is about.

Then request the module's ownership to be treansfered, using these steps (in specified order):

1. contact the module owner via the contact form of that owner on Drupal.org, asking for the ownership to be transferred.
2. If current owner indicates to agree with a transfer, or if after 2 weeks you have not received any response to step 1, then file an issue on Drupal.org, to request the "ownership to be transfered" (include relevant communication from step 1 to motivate your request). Issue # 2367923 is an example of such issue.
3. The people handling the request from step 2 will then also try to contact the current owner (if you didn't get a reply to step 1.). And after a grace period of (about) 2 weeks, the project's ownership will be changed to you (unless there was some type of feedback from the current owner to not do so).
4. Do whatever you want to do with the module for which you became the new owner, without any review process involved. But make sure to:

• give credit to the previous owner somehow.
• NOT destroy any (GIT) history of the old version of the module.

The above period works fine, though it takes a little time (a few weeks at max) to complete all the steps ... And it has the advantage (I think) that you contribute a very little bit to reduce the amount of abonded-looking contributed modules.

PS: There are occasions where the current maintainer responds/reacts with something like "Hm, somebody interested in contributing to a 2nd live to a module I started ... how about I only grant co-maintainer status instead of transferring module ownership?". If that happens, then "you" have to decide if you yes/no are willing to accept that. A possible compromise in that case could be "how about we turn the table: I become owner, and make you (current owner) a co-maintainer".

An alternative approach to "create a full project on drupal.org", is to investigate the existing (+17K) contributed modules, and narrow them down to projects with status like:

• Seeking new maintainer (675 hits).
• Unsupported (1.514 hits).

From the search results that you get, verify if there is anything that has a "namespace" (= the machine name of your module) that might fit (or is close enough) to what your (new) module is about.

Then request the module's ownership to be treansfered, using these steps (in specified order):

1. contact the module owner via the contact form of that owner on Drupal.org, asking for the ownership to be transferred.
2. If current owner indicates to agree with a transfer, or if after 2 weeks you have not received any response to step 1, then file an issue on Drupal.org, to request the "ownership to be transfered" (include relevant communication from step 1 to motivate your request). Issue # 2367923 is an example of such issue.
3. The people handling the request from step 2 will then also try to contact the current owner (if you didn't get a reply to step 1.). And after a grace period of (about) 2 weeks, the project's ownership will be changed to you (unless there was some type of feedback from the current owner to not do so).
4. Do whatever you want to do with the module for which you became the new owner, without any review process involved. But make sure to:

• give credit to the previous owner somehow.
• NOT destroy any (GIT) history of the old version of the module.

The above period works fine, though it takes a little time (a few weeks at max) to complete all the steps ... And it has the advantage (I think) that you contribute a very little bit to reduce the amount of abonded-looking contributed modules.

PS: There are occasions where the current maintainer responds/reacts with something like "Hm, somebody interested in contributing to a 2nd live to a module I started ... how about I only grant co-maintainer status instead of transferring module ownership?". If that happens, then "you" have to decide if you yes/no are willing to accept that. A possible compromise in that case could be "how about we turn the table: I become owner, and make you (current owner) a co-maintainer".

An alternative approach to "create a full project in drupal.org", is to investigate the existing (+17K) contributed modules, and narrow them down to projects with status like "looking for a new maintainer", or "obsolete" (and probably a few other variations). Just use existing query facilities on drupal.org.

From the list that pops up, verify if there is anything that has a "namespace" (= the machine name of your module) that might fit (or is close enough) to what your (new) module is about.

Then request the module's ownership to be treansfered, using these steps (in specified order):

1. contact the module owner via the contact form of that owner on Drupal.org, asking for the ownership to be transferred.
2. If current owner indicates to agree with a transfer, or if after 2 weeks you have not received any response to step 1, then file an issue on Drupal.org, to request the "ownership to be transfered" (include relevant communication from step 1 to motivate your request). Issue # 2367923 is an example of such issue.
3. The people handling the request from step 2 will then also try to contact the current owner (if you didn't get a reply to step 1.). And after a grace period of (about) 2 weeks, the project's ownership will be changed to you (unless there was some type of feedback from the current owner to not do so).
4. Do whatever you want to do with the module for which you became the new owner, without any review process involved. But make sure to:

• give credit to the previous owner somehow.
• NOT destroy any (GIT) history of the old version of the module.

The above period works fine, though it takes a little time (a few weeks at max) to complete all the steps ... And it has the advantage (I think) that you contribute a very little bit to reduce the amount of abonded-looking contributed modules.

PS: There are occasions where the current maintainer responds/reacts with something like "Hm, somebody interested in contributing to a 2nd live to a module I started ... how about I only grant co-maintainer status instead of transferring module ownership?". If that happens, then "you" have to decide if you yes/no are willing to accept that. A possible compromise in that case could be "how about we turn the table: I become owner, and make you (current owner) a co-maintainer".

An alternative approach to "create a full project in drupal.org", is to investigate the existing (+17K) contributed modules, and narrow them down to projects with status like:

• Seeking new maintainer (675 hits).
• Unsupported (1.514 hits).

From the search results that you get, verify if there is anything that has a "namespace" (= the machine name of your module) that might fit (or is close enough) to what your (new) module is about.

Then request the module's ownership to be treansfered, using these steps (in specified order):

1. contact the module owner via the contact form of that owner on Drupal.org, asking for the ownership to be transferred.
2. If current owner indicates to agree with a transfer, or if after 2 weeks you have not received any response to step 1, then file an issue on Drupal.org, to request the "ownership to be transfered" (include relevant communication from step 1 to motivate your request). Issue # 2367923 is an example of such issue.
3. The people handling the request from step 2 will then also try to contact the current owner (if you didn't get a reply to step 1.). And after a grace period of (about) 2 weeks, the project's ownership will be changed to you (unless there was some type of feedback from the current owner to not do so).
4. Do whatever you want to do with the module for which you became the new owner, without any review process involved. But make sure to:

• give credit to the previous owner somehow.
• NOT destroy any (GIT) history of the old version of the module.

The above period works fine, though it takes a little time (a few weeks at max) to complete all the steps ... And it has the advantage (I think) that you contribute a very little bit to reduce the amount of abonded-looking contributed modules.

PS: There are occasions where the current maintainer responds/reacts with something like "Hm, somebody interested in contributing to a 2nd live to a module I started ... how about I only grant co-maintainer status instead of transferring module ownership?". If that happens, then "you" have to decide if you yes/no are willing to accept that. A possible compromise in that case could be "how about we turn the table: I become owner, and make you (current owner) a co-maintainer".