Now I am not getting how to make it full project.
Your starting point is https://www.drupal.org/project/projectapplications You'll need to create an issue according to the instructions on this page. People will review (automated and manually) to check if this module is good for contrib.
To promote your sandbox project to full project, you will have to apply for permission to create a full project as described here in drupal docs: https://www.drupal.org/node/1011698 .
After getting permission you will be able to promote your sandbox to a full project.
Here are complete screenshots: https://www.drupal.org/node/1068952.
As of 2017/03/07, users do not need to go through the Project Application Review process to promote a project. With this change, people without the git-vetted status can promote one sandbox project to full project status. See also the change record:
Strong signals about security advisory coverage are available on project pages on Drupal.org, and in the updates.xml that is served by Drupal.org for core to consume. There is also now a field for project maintainers to opt into security advisory coverage.
This means that we're now able to open the gates, to allow any user who has accepted the Git repository usage policy to promote their sandbox projects to full projects with releases.
At the same time as we make this change, we'll be repurposing the 'git-vetted' user role as a 'may opt-into security coverage' role. The existing project application process move from a gate on promoting full projects to the gate for opting in to security advisory coverage. That process will be further refined by various stakeholders in follow ups.
We'll be updating the documentation to reflect this change in process as well.
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:
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):
- Contact the module owner via the contact form of that owner on Drupal.org, asking for the ownership to be transferred.
- 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.
- 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).
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".