I would like to became a co-maintainer of Tailwind CSS Starter Kit
I found this project sightly outdated ~2 months ago and that time posted this issue - Is this project still actively maintained?, which initially reborn the project - its original maintainer opdavies answered, which also bough attention of another maintainer - ravi-kant.
My contributions so far
As a result i proposed the development plan for the project, which was followed by a code - multiple merge requests from my side were accepted and merged into the main branch by ravi-kant, which also did some refactoring work at that period of time.
Current situation
However, after that promising initial initiative it seems that there is no more sufficient interest from its current contributors. It took out that after its last messages contact with project owner was lost and its current co-maintainer is not paying the attention about the community aspects of the project. I have to claim for my credits in any closed issue that i fixed and no single new version was released since that time.
My co-maintenance requests hangs for one month with no answer from anybody.
I request to add me as a co-maintainer, so i can continue the modernisation of a starterkit - keep the code updates going, assign contribution credits, accept the merge requests after they are tested, Maintain issues, Administer releases, and ideally also Administer maintainers, as current contributors are not responding for requests and the original owner is out of reach.
Comments
Comment #2
avpadernoThese offers need to be created in the project issue queue, even when the person asking for more permissions is already co-maintainer or maintainer. As per Offering to become a project owner, maintainer, or co-maintainer, they can be moved in the Drupal.org project ownership queue, 14 days after the offer was posted/moved in the project queue, if the offer has not been declined by maintainers (including the project owner).
Remember to give the project link, when the issue is moved.
As a side note, only the person who made the offer can move the issue.
Comment #3
avpadernoAs a side note, project moderators will not add as co-maintainer / maintainer / project owner a person who is not able to opt projects into security advisory coverage. Moving this offer to the Drupal.org project ownership queue will only have the effect to make it moved back to this queue.
Comment #4
avpadernoI am closing this issue because there has not been any follow-up action as described in How to become project owner, maintainer, or co-maintainer from the person who opened this offer.
Comment #6
firflant@avpaderno Please let me know if I am wrong, he follow-up action is currently not on my side. Here is a clarification:
My security advisory coverage, which is a must-have criteria according to How to become project owner, maintainer, or co-maintainer, is pending. After initial review of my contrib module, I added the required improvements and now it awaits review for two months.
Here is a link to the issue that blocks my account from becoming a fully trustable Drupal user:
https://www.drupal.org/project/projectapplications/issues/3577951
I hope that it can be closed soon and then we can proceed with the contribution offer?
Comment #7
avpaderno@firflant Since the offer is yours, you need to move this offer to the Drupal.org project ownership queue by changing the Project value to Drupal.org project ownership. Anyway, since you cannot yet opt projects into security advisory coverage, moving this issue in that queue would just have the effect of getting it back to this issue queue.
If you want to be appointed co-maintainer for a project, and maintainers do not reply to your offer, you need to wait to be able to opt projects into security advisory coverage.
Comment #8
firflant@avpaderno then let me wait. I will go back to the Drupal.org project ownership issue after the process is hopefully finished.