AdminContacts: Difference between revisions

From QEMU
m (Protected "AdminContacts" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
No edit summary
Line 6: Line 6:
*** stable branch: jforbes, afaerber, mdroth
*** stable branch: jforbes, afaerber, mdroth
*** website: paolo,jcody, pmaydell, mdroth
*** website: paolo,jcody, pmaydell, mdroth
*** sgabios: paolo
** CHANGES: via server root access
** CHANGES: via server root access
* QEMU server root access (sysadmin)
* QEMU server root access (sysadmin)
** WHO: jcody, (backup) stefanha, paolo
** WHO: jcody; backup: stefanha, paolo
** CHANGES: by anybody with root, I assume
** CHANGES: by anybody with root, I assume
* VM root access (runs patchew etc)
* VM root access (runs patchew etc)
Line 37: Line 38:
** each mailing list has its own list admin and (I think) password. If you have savannah project admin access you can request a password reset for any list.
** each mailing list has its own list admin and (I think) password. If you have savannah project admin access you can request a password reset for any list.
* github https://github.com/qemu
* github https://github.com/qemu
** WHO: afaerber, alex bennee, aliguori, paolo
** WHO: afaerber, aliguori, paolo, stsquad (Alex Bennée)
* QEMU Advent Calendar (http://www.qemu-advent-calendar.org/)
* QEMU Advent Calendar (http://www.qemu-advent-calendar.org/)
** WHO: (primary) Thomas Huth, Kashyap Chamarthy, jcody, stefanha
** WHO: (primary) Thomas Huth, Kashyap Chamarthy, jcody, stefanha

Revision as of 12:44, 27 April 2017

The QEMU project has a large number of different pieces of infrastructure, including servers and accounts on various web services. This page attempts to list them all and indicate who has the access rights on those systems and how they can be updated, so we can update things as necessary as people leave or join the project.

  • git server push access
    • WHO:
      • main repo: pmaydell, stefanha, mdroth
      • stable branch: jforbes, afaerber, mdroth
      • website: paolo,jcody, pmaydell, mdroth
      • sgabios: paolo
    • CHANGES: via server root access
  • QEMU server root access (sysadmin)
    • WHO: jcody; backup: stefanha, paolo
    • CHANGES: by anybody with root, I assume
  • VM root access (runs patchew etc)
    • WHO: Fam Zheng
    • CHANGES: anybody with access
  • wiki admin
  • Google+ page https://plus.google.com/101344524535025574253
    • WHO: stefanha, mdroth, aliguori
    • CHANGES: ?
  • Launchpad https://launchpad.net/qemu
    • WHO: everybody in the LP 'qemu' team: https://launchpad.net/~qemu -- currently pmaydell, Thomas Huth, Paolo, Dustin Kirkland
    • CHANGES: if you're in that group with admin status you can add others
  • IRC channel operator
    • WHO: pmaydell, stefanha, aliguori
    • CHANGES: anybody with 'MASTER' access can change this via ChanServ's "ACCESS" command
  • DNS
    • qemu-project.org is owned by Conservancy
    • qemu.org/qemu.net/qemu.com are owned by Olivier Guillaumin
    • all should be set up so we are the technical contact, admin via Gandi. jcody (anybody else?) has access here.
  • OSUOSL point-of-contact
    • stefanha, jcody (and at the OSUOSL end Lance Albertson)
  • our savannah project (https://savannah.nongnu.org/projects/qemu/)
    • WHO: pmaydell, stefanha, edgar
    • CHANGES: admin access lets you change list
  • savannah mailing lists
    • each mailing list has its own list admin and (I think) password. If you have savannah project admin access you can request a password reset for any list.
  • github https://github.com/qemu
    • WHO: afaerber, aliguori, paolo, stsquad (Alex Bennée)
  • QEMU Advent Calendar (http://www.qemu-advent-calendar.org/)
    • WHO: (primary) Thomas Huth, Kashyap Chamarthy, jcody, stefanha
    • CHANGES: Any of the above (all have root accounts)
  • Rackspace (https://rackspace.com): rights to obtain access and control / allocate / delete resources, and backups for qemu.org server, patchew new server and the QEMU Advent calendar
    • WHO: jcody, stefanha
    • CHANGES: SF Conservancy can add new admin accounts