Changes between Version 26 and Version 27 of AdoptingHacks

Timestamp:

May 23, 2015, 7:58:11 AM (9 years ago)

Author:

figaro

Comment:

Cosmetic changes

AdoptingHacks

@@ -5 +5 @@
 When owners of one of the hacks hosted on http://trac-hacks.org retire, 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. Allow for a two week grace period for the author of the hack to reply.
+ 1. Open a ticket for the hack in question and add the tag `adoption-request` in the ''Keywords'' field. Ask about its 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
@@ -20 +20 @@
  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.])]].
- 1. Edit the following line on the hack's wiki page to remove the `&owner=oldmaintainer` portion of the query string (the ticket is automatically assigned to the new maintainer so it is no longer necessary to explicitly set this parameter)[[FootNote(After completing this step you may want to select the '''new ticket''' link and verify that a ticket opened from the plugin's wiki page is assigned to you. You may also want to open a ticket using the '''New Ticket''' link in the main navigation bar and verify that the ticket is assigned to you in that case as well. The latter case depends on the trac-hacks admin assigning you as the hack's owner, so it is good to check that this was done correctly and follow-up with the admin if not.)]].
+ 1. Remove the `&owner=oldmaintainer` portion from the query string:[[FootNote(After completing this step you may want to select the '''new ticket''' link and verify that a ticket opened from the plugin's wiki page is assigned to you. You may also want to open a ticket using the '''New Ticket''' link in the main navigation bar and verify that the ticket is assigned to you in that case as well. The latter case depends on the trac-hacks admin assigning you as the hack's owner, so it is good to check that this was done correctly and follow-up with the admin if not.)]].
  {{{
 If you have any issues, create a 
-[/newticket?component=UserStatsMacro&owner=oldmaintainer new ticket].
+[/newticket?component=UserStatsMacro'''&owner=oldmaintainer''' new ticket].
 }}}
+ The ticket is automatically assigned to the new maintainer, so it is no longer necessary to explicitly set this parameter.
 
 == Available for Adoption