User:Toshio/Who picks up the pieces

Toshio

At bat

• python-fedora
  • Release management (laxathom)
  • Everything else: team: (puiterwijk, pingou, threebean, lmacken, relrod)
  • Code review and PR approval.
  • Coding/bugfixing
    • AuthN, authZ integration with client

• python-kitchen (threebean) ;; abompard to migrate to github (done)
  • Release management
  • Coding bug fixing
  • Porting to python3

• FAS
  • (laxathom) is already officially the head maintainer. You'll mostly miss me for quick analysis and hotfixes (see hotfixes section)

• Pkgdb/elections/etc (pingou)
  • Mostly picked up by pingou already :-)

• Packages I maintain
  • https://admin.fedoraproject.org/pkgdb/packager/toshio/
  • A few assigned to nirik (things we deploy for hosted), threebean or lmacken (already comaint). Others given to group::infra-sig and threebean given approveacls. Who is responsible for updating which package to be worked out by the team.
  • Packages not maintained by the team:
    • bzr, bzrtools => hno (comaint), orphan on epel5
    • loggerhead => hno, kevin as backup (used in infra)
    • qbzr, bzr-explorer => orphan
    • bzr-gtk (on el5) => orphan
    • trac-bazaar-plugin => kevin (used in infra)
    • supervisor(el5,6,7) => kevin
    • python-cjson (el5) => orphan
    • gprof2dot => orphan
    • python-migrate => orphan(el5), pbrady(other epel branches)
    • python-paver => orphan
    • python-decorator => threebean
    • python-decorator3 (el5) => lmacken
    • python-sqlalchemy => nphilip (infra-sig as comaint)
    • pygpgme => (mitr)
    • python-rope => (mcepl)
    • python-elixir => (orphan)
    • rpmdevtools (asked scop if he would like kevin to help out)
    • python-q => toshio
    • python-cpio => toshio

• Provenpackager
  • analysis and bugfixes to packaging, bug fixes, etc
  • Getting fixes into packages where maintainers are unresponsive and doing general distro cleanups.
  • pingou, abompard, nirik, lmacken, relrod already in provenpackager
  • pingou and abompard to do this for the python stack which we depend on...
  • rest of the distro, nirik can work on but he's already stretched so there's going to be less coverage :-(

• Postgres (pingou, relrod)
  • ad hoc queries to FAS mostly

• one-off quick sysadmin scripts (pingou, threebean, abompard, lmacken, puiterwijk, relrod)
  • People just aware that nirik will need various scripts and I won't be there to do them

• Fireman: The "It's Friday afternoon and $RANDOM thing is broken, can you fix it?" (threebean, relrod and pingou)
  • hotfixes
  • and the whole team might have to take on more scripts that intersect their areas of knowledge. rely on nirik to coordinate (letting people know that there is a need that has to be satisfied)

• General knowledge of history - why code is the way it is, who to talk to about an issue in Fedora, etc.
  • I'll still be around IRC so some this you can still rely on me for. I just won't be nearly as active on creating new code.

• FPC
  • Going to look outside of our team (?)
  • python packaging guidelines -- python3, wheels? (?)
    • nirik, abompard, hopefully pingou, threebean, and lmacken
    • Since python is so important to infrastructure I think someone has to get involved in this.

• Knowledge that I'm the go to guy for
  • Packaging knowledge (?)
  • setuptools knowledge (lmacken, threebean, abompard)
  • unicode issues (abompard)
  • history of legal issues spot has resolved, etc. (Decided we just have to go back to spot)
  • I'll be around IRC but you may also have to make due without until someone gains the knowledge.

On deck

Things I've talked about working on with Paul or the infra team:

• Working on authN and authZ with puiterwijk and Xavier
  • (puiterwijk) since he's coming on board.

• Python3 porting (?)
  • Longer term problem but this is coming at us and it's large.
  • Need to review the python34 EPEL packages from orionp and get the packaging effort started.
  • Once that's done, just start plugging away at making library code run on both py2 and py3 and app code either run on both or run only on py3.
  • I think that threebean's interested in this. Question of how much time he has to work on it, though.
  • (puiterwijk) expressed interest in porting fedoauth to python3 as one of his tasks. This would get the python3-flask stack into epel7. Some libraries fedoauth uses will need upstream porting help

• mirrormanager port to flask (pingou)
  • pingou won't have much of my time or mdomsch's time for talking about architecture and as a sounding board for changes - suggest a FAD with mdomsch

• Port away from TG1
  • mirrormanager (pingou), bodhi (lmacken, FAD: post-F21 release), and fas (laxathom and pingou).
  • From toshio to pingou: Be careful not to burn out :-)

skvidal

• Copr
  • msuchy. But needs lots of help and more TZ coverage
  • Possible to get more mikem time to add these needs to koji?
  • Someone needs to catch up with mikem about what he and msuchy talked about at flock. Find out recommendations from him wrt using obs for signing copr and building copr vs adding to koji. Coordinate with management to get coding time to add features to koji for building and signing coprs if that's mikem's suggestion. (stickster + nirik for initial coordination?)
• cloud
  • Currently smooge and nirik have picked up this work
• Depsolving questions -
  • Currently no one is filling this void in infra

spot

• Packaging: maintaining lots of packages and pitching in to fix or take on new ones if there was a need in the distro
• Since he's Fedora Legal we had easy access to get questions answered. Harder now with all of his other projects.

...every time two fools collide