- Issue created by @abhi_khandelwal
- 🇺🇸United States dww
Hi,
Thanks for your interest in this module. However, I've never seen an issue from you, a patch or MR from you, or even a comment in this issue queue that you're using this module and helping to test / fix anything. I have no idea who you are, if you know how to write secure code, if you know how to write good tests, if you know how to manage releases, database schema updates, etc. There's no way I could possibly grant you access to push commits to this project, much less "co-maintain" it since you've never contributed anything to it and I have no information about you, your experience, abilities, or anything.
Also, if you have a "strong team" that is "managing" this module, I'd love to see some evidence of that in the issue queue before you request for your "team" to take over. Note that drupal.org works with human accounts, not teams. If you have a team, and they're all helping, we need to see activity from each member of that team who will would potentially become a maintainer. Sharing accounts or credentials among a team is disallowed by drupal.org policy.
In the future, if you and your strong team want to contribute to the modules hosted here, I strongly encourage you to start by actually contributing to the module in any/all of the following ways:
- Triage the issue queue (look for duplicates, make sure bugs can be reproduced, that issue summaries are clear and accurate, etc).
- Help review and test existing merge requests.
- Write test coverage for MRs that are lacking tests.
- Write new merge requests for issues that do not yet have code but need it.
- ...
If you perform any (ideally, many) of these tasks, you will begin to earn some respect and trust from existing maintainers. Only after a period of building respect and trust would any responsible maintainer seriously consider granting anyone else access.
Cheers,
-Derek