Changes between Version 24 and Version 25 of AdoptingHacks

Timestamp:

May 2, 2015, 12:13:24 PM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes

AdoptingHacks

@@ -5 +5 @@
 When owners of one of the hacks hosted on http://trac-hacks.org retires, the hack may be adopted by interested parties to maintain and further the hack for the Trac community. The standard procedure is:
  
- 1. Open a ticket for the hack in question and add the tag `adoption-request` in the ''Keywords'' field. Ask about it's maintainership status on [http://lists.trac-hacks.org th-users mailing list] (quoting the ticket you've just opened) and tell the audience that you'd be willing to take over maintainership. Then sit back and wait for at least two weeks, to see if the author of the hack replies.
+ 1. Open a ticket for the hack in question and add the tag `adoption-request` in the ''Keywords'' field. Ask about it's maintainership status on [http://lists.trac-hacks.org th-users mailing list] (quoting the ticket you've just opened) and tell the audience that you'd be willing to take over maintainership. Allow for a two week grace period for the author of the hack to reply.
  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 hack in
@@ -17 +17 @@
 
  1. Change the '''Owner''' of open tickets from the previous maintainer to the new maintainer.
- 1. ~~Add your username to the '''Maintainer''' field on the hack's wiki page.~~ Replace the username in the **Maintainer** field with `[[Maintainer]]`, if the change has not already been made (#10249).
+ 1. Replace the username in the **Maintainer** field with `[[Maintainer]]`, if the change has not already been made (#10249).
  1. Add your username to the list of '''Tags''' on the hack's wiki page. Remove the [/tags/'needsadoption' needsadoption] tag, if present.
  1. If the plugin has a `setup.py` file, you can add your name and email address to the `maintainer` and `maintainer_email` fields, respectively[[FootNote(This step will also allow you to verify that you have write access to the repository.)]] [[FootNote(To see an example, take a look at [/browser/doxygenplugin/0.11/setup.py?rev=6328&marks=42-43#L1 this file.])]].
@@ -30 +30 @@
 See the [tag:needsadoption list of hacks] available for adoption. If you have a plugin which you no longer wish to maintain, please add the [/tags/'needsadoption' needsadoption] tag to the plugin's wiki page.
 
-
 == Administrator Actions
 
-The following steps should be taken by an administrator when changing the maintainer of a hack.
+The following steps should be taken by an administrator when changing the maintainer of a hack:
 
 1. Change the //Component// owner of the hack to the new maintainer (Admin > Ticket System > Components). Put the old Component owner in the description field.
-1. Grant r/w access to new maintainer for the hack's repository path. [[FootNote(Currently the SvnAuthzAdminPlugin is not functional, so this must be done by editing the permissions file)]]. Generally we do not revoke r/w access for any previous maintainers.
+1. Grant r/w access to new maintainer for the hack's repository path. [[FootNote(Currently the SvnAuthzAdminPlugin is not functional, so this must be done by editing the permissions file.)]]. Generally we do not revoke r/w access for any previous maintainers.
 
 [[FootNote]]