• Logo
    Ubuntu project
  • documentation.ubuntu.com
  • More resources
    • Discourse
    • Matrix
    • GitHub
Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Ubuntu project documentation
Ubuntu project documentation
  • How Ubuntu is made
    • Governance
      • Ethos
        • Ubuntu Code of Conduct
        • Diversity policy
        • Our Mission
      • Peers
    • Key concepts and definitions
      • About components
      • About freezes
      • About pockets
      • About seeds
      • About series
      • Glossary
      • Package lifecycle
    • Process overviews
      • Main Inclusion Review (MIR)
      • MIR roles and steps
      • The merge process
      • The SRU process overview
      • The sync process
      • How transitions work
  • Contributors
    • Getting started
      • git-ubuntu
      • How to run package tests
      • Test environment
      • Tooling for development
    • Contribute to documentation
    • Fix a bug
      • How to bug-fix a package
      • Bug fixing checklist
      • How to debug an apport bug
      • Report a bug
    • Patching
      • How to dual-maintain with Salsa and git-ubuntu
      • Find a sponsor for your upload
      • How to use deb patches
      • Version string format
    • New packages
      • How to create a new package
      • Request an SRU
    • Advanced Contributor tasks
      • Manage seeds
      • +1 Maintenance
      • Request a package removal
      • MIR bug request template
      • How to use MIR templates
  • Maintainers
    • Uploader tasks
      • Sponsoring
      • How to update seeds
      • How to work with the upload queue
    • MIR tasks
      • MIR reviewer's template
    • SRU tasks
      • How to review an SRU
    • Archive Admin tasks
      • How to adjust Launchpad ACLs
      • Auto-builders
      • Client side tools
      • How to manage chroots
      • How to manage component mismatches
      • How to manage package sets
      • NBS packages
      • How to remove packages
      • How to sync packages
      • Team rotations
      • How to update i386 allowlists
  • Who makes Ubuntu
    • Councils and Boards
      • Community Council
      • Conflict resolution
      • Delegation
      • Membership Board
      • Technical Board
    • Roles and responsibilities
      • About the uploaders role
        • Uploaders service level agreement
      • About the MIR role
        • MIR Service Level Objectives
        • MIR team weekly status meeting
      • About the MIR processes
        • Process states
        • MIR exception - font packages
        • MIR exception - OEM packages
        • MIR - re-reviews
        • MIR - Rust code in main
      • About the SRU role
        • SRU service level agreement
      • About the Archive Admin role
        • AA service level agreement
    • Joining a role
      • Contributor Journeys
      • How to run a core-dev interview
      • How to run a membership interview
      • Membership perks
      • Package set membership
  • Staging/preview area
    • Germinate
    • Mirror scripts
    • Mirrors
    • New packages
    • The Package Archive
    • Phased updates
    • Push mirroring
    • Seed management
    • Sponsorship process
    • Archive Administration
      • NEW review
      • NEW processing (wiki)
      • Package removal
      • Removals (wiki)
      • Package overrides
      • Component mismatches and changing overrides (wiki)
      • AA team’s less common tasks
      • Archive-related services
      • Content that doesn’t belong to AA
      • Archive Admin museum
    • Packaging guide move
      • Guides for contributors
        • Getting set up
          • Get the source of a package
          • Getting set up
          • Use schroots
        • Bug fixing
          • Build packages
          • Download a new upstream version
          • Extract packages
          • Fix a bug
          • Install built packages
          • Propose changes
          • Run tests
        • Patching
          • Making changes to a package
          • Patch management
        • New packages
          • Create a new package
          • Upload packages to a PPA
      • How Ubuntu is made
        • Concepts
          • Supported architectures
          • Ubuntu package archive
          • Basic overview of the debian/ directory
          • Debian policy
          • Filesystem hierarchy standard
          • Launchpad
          • Package model
          • Package version format
          • Patches
          • DEP 3 - patch file headers
          • Ubuntu releases
          • Upstream and downstream
        • Process overviews
          • Backports
          • Importing changes from Debian (merges & syncs)
          • Ubuntu development process
          • Main Inclusion Review (MIR)
          • Merge a package from Debian
          • Proposed migrations
          • Request a freeze exception
          • Sponsorship
          • Transitions
Back to top
Contribute to this page

About the MIR role¶

Should split between the role/responsibilities, and info about the team processes.

MIR team responsibilities¶

  • MIR Service Level Objectives
  • MIR team weekly status meeting
Copyright © 2025 CC-BY-SA, Canonical Ltd.
Last updated on Jun 23, 2025
Contents
  • About the MIR role
    • MIR team responsibilities