Changes between Version 27 and Version 28 of AdoptingHacks


Ignore:
Timestamp:
Sep 12, 2016, 7:48:55 PM (6 years ago)
Author:
figaro
Comment:

Propagate better plugin naming

Legend:

Unmodified
Added
Removed
Modified
  • AdoptingHacks

    v27 v28  
    1 = Adopting Hacks
     1= Adopting plugins
    22
    3 == How to Adopt Unmaintained Hacks
     3== How to adopt unmaintained plugins
    44
    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:
     5When owners of one of the plugins hosted on http://trac-hacks.org retire, the plugin may be adopted by interested parties to maintain and further the plugin for the Trac community. The standard procedure is:
    66 
    7  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.
     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.
    88 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 hack in
     9    your request, ask us to give you read/write permission for the plugin in
    1010    the repository, or even pass (maintainer|owner)ship to you.
    1111 1. If the author does not reply, reply to your original post on the [http://lists.trac-hacks.org th-users mailing list].
    1212    The trac-hacks admins then grant write permission to the repository.
    1313
    14 == After Adopting a Hack
     14== After adopting a plugin
    1515
    16 Make the following changes to the hack:
     16Make the following changes to the plugin:
    1717
    1818 1. Change the '''Owner''' of open tickets from the previous maintainer to the new maintainer.
    1919 1. Replace the username in the **Maintainer** field with `[[Maintainer]]`, if the change has not already been made (#10249).
    20  1. Add your username to the list of '''Tags''' on the hack's wiki page. Remove the [/tags/'needsadoption' needsadoption] tag, if present.
     20 1. Add your username to the list of '''Tags''' on the plugin's wiki page. Remove the [/tags/'needsadoption' needsadoption] tag, if present.
    2121 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.])]].
    2222 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.)]].
     
    2727 The ticket is automatically assigned to the new maintainer, so it is no longer necessary to explicitly set this parameter.
    2828
    29 == Available for Adoption
     29== Available for adoption
    3030
    31 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.
     31See the [tag:needsadoption list of plugins] 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.
    3232
    3333== Administrator Actions
    3434
    35 The following steps should be taken by an administrator when changing the maintainer of a hack:
     35The following steps should be taken by an administrator when changing the maintainer of a plugin:
    3636
    37 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.
    38 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.
     371. Change the //Component// owner of the plugin to the new maintainer: Admin > Ticket System > Components. Put the old Component owner in the description field.
     381. Grant read/write access to new maintainer for the plugin'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 read/write access for any previous maintainers.
    3939
    4040[[FootNote]]