| 7 | | 1. Open a ticket for the plugin in question and add the tag `adoption-request` in the ''Keywords'' field. Ask about its maintainership status on the [http://lists.trac-hacks.org th-users mailing list] (quoting the ticket you've just opened) and tell the audience that you are willing to take over maintainership. Allow for a two week grace period for the author of the plugin to reply. |
| 8 | | 1. If the author replies, he/she decides how to proceed. He/she could deny |
| 9 | | your request, ask us to give you read/write permission for the plugin in |
| 10 | | the repository, or even pass (maintainer|owner)ship to you. |
| 11 | | 1. If the author does not reply, reply to your original post on the [http://lists.trac-hacks.org th-users mailing list]. |
| 12 | | The trac-hacks admins then grant write permission to the repository. |
| | 9 | 1. Open a ticket for the plugin in question and add the tag `adoption-request` in the ''Keywords'' field. Ask about its maintainership status on the [https://groups.google.com/forum/#!forum/trac-hacks th-users mailing list] and quoting the ticket you've just opened, and tell the audience that you are willing to take over maintainership. Allow for a two week grace period for the author of the plugin to reply. |
| | 10 | 1. If the author replies, he/she decides how to proceed. He/she could deny your request, ask us to give you read/write permission for the plugin in the repository, or even pass (maintainer|owner)ship to you. |
| | 11 | 1. If the author does not reply, reply to your original post on the [https://groups.google.com/forum/#!forum/trac-hacks th-users mailing list]. The trac-hacks admins then grant write permission to the repository. |
