14 | | 3. If the author does not reply, post the request to the [http://lists.trac-hacks.org th-users mailing list]. This makes the whole process public, allowing other users to |
15 | | comment on it if, for example, they have information on the whereabout of |
16 | | the original author. |
17 | | |
18 | | 4. If the author does not reply within the given time frame and the mailing list discussion hasn't panned out, contact one |
19 | | of the admins ''(link?)''. They will check the status quo, probably try again to get |
20 | | in contact with the author, and eventually decide on your request. In |
21 | | most cases you would be granted (maintainer|owner)ship of the hack in |
22 | | question if its development seems stalled and if neither the original |
23 | | author nor any contributor can be contacted in a reasonable timeframe. |
| 14 | 3. If the author does not reply, post the request to the [http://lists.trac-hacks.org th-users mailing list]. |
| 15 | The trac-hacks admins then grant commit-right to the repository. |