Registry Administrator duties

The Registry Administrator is responsible for maintaining the quality of registry data in Launchpad. It acts as a steward for unmaintained projects and teams. The Launchpad engineering team are the leaders of the Registry Administrator team and the Launchpad maintenance squads take on the daily and monthly duties.

Daily duties

• Review the moderation queue for the ~registry mailing list.
  Approve legitimate email to go to the list. Discard other emails.

• Review the recent emails to the mailing list (or archive)
  Respond to user requests: reply to the email if you are subscribed, or send an email to the user and CC the list.

• Answer open questions.
  ~registry does not get many questions (since users are directed to ask questions at /launchpad), but some users assign the team questions.

• Decline invitations to join teams.
  ~registry is root-team used as a last resort for ownership. It does not participate in any community. It should not be a member of any team to gain permission or to receive email.
  

• Remove superteams
  These have appeared because of merge-delete team defects.

   from launchpadlib.launchpad import Launchpad
   lp = Launchpad.login_with(
       'retract-team', service_root='https://api.launchpad.net',
       version='devel')
   my_team = lp.people['registry']
   other = lp.people['<team-lp-id>']
   comment = 'The Registry admins should not be a member of any team.'
   my_team.retractTeamMembership(team=other, comment=comment)

  ^ Replace <team-lp-id> with the name of the team ~registry is in.

• Remove owned teams
  ~registry does not delegate responsibilities to other teams; it does not use other teams to manage the projects it stewards. Therefore it should not own any teams. Launchpad does not provide a way to know what teams a person or team owns, but you can examine your admined teams using a random project's +subscribe page and investigate those you do not understand.

  • Delete the team
  • Or make an admin the owner of the team and remove ~registry.
  • Note that some teams in the +subscribe list may be from ~rosetta-admins, which also should not own any teams.

• Clean up objects wrongly linked to ~registry by team merge-delete

  • Remove direct bug subscriptions

  • Remove structural bug subscriptions

  • Remove bug assignments

  • Remove blueprint assignments, drafter, approver

  • Remove blueprint subscriptions (not possible)

Monthly duties

• Deactivate abandoned projects
  Visit Search projects and search for terms that users add to display names and descriptions to indicate that they have given up the project: delete, dead, remove, obsolete, abandoned. The listing often includes 10-20 projects where you can see the user is asking for the project to be removed. See bug 413585

• Delete abandoned teams
  Visit Search people and search for terms that users add to display names and descriptions to indicate that they have given up the team: delete, dead, remove, obsolete, abandoned.

• Review licensing of active projects owned by ~registry
  Review the listings for projects owned by Registry Admins: Projects without a license and "I Don't Know" projects You can either update the license information or deactivate the project.