12 | | * Authors of plugins hosted on GitHub should be invited to join the [github:trac-hacks] organization. |
13 | | * A stub page should be created for a plugin hosted on GitHub, if the stub page doesn't already exist. |
14 | | * The `[[Maintainer]]` macro can be used on project wiki pages (e.g. TagsPlugin@78). |
15 | | * It isn't necessary to specify the owner in the //new ticket// query string. It makes maintenance easier if the owner is removed (e.g. TagsPlugin@79). |
16 | | * Deprecated plugins should have a notice at the top of the page using the `box` WikiProcessor (e.g. TracTagsXmlrpcPlugin@6). The deprecated tag should be added to the page. |
| 12 | * Authors of plugins hosted on GitHub should be invited to join the [github:trac-hacks] organization. The wiki page should be tagged with [tagged:github-hosted]. |
| 13 | * A stub page should be created for a plugin hosted on GitHub, if the stub page doesn't already exist. |
| 14 | * Plugins that are not only hosted on trac-hacks, but also PyPi, should be tagged with [tagged:pypi]. |
| 15 | * The `[[Maintainer]]` macro can be used on project wiki pages, for example TagsPlugin@78. |
| 16 | * It isn't necessary to specify the owner in the //new ticket// query string. It makes maintenance easier if the owner is removed, for example TagsPlugin@79). |
| 17 | * Deprecated plugins should have a notice at the top of the page using the `box` WikiProcessor, for example TracTagsXmlrpcPlugin@6. The deprecated tag should be added to the page. |