Koji can now build EPEL packages but we need bodhi changes in order to be able to push the packages to the servers. here's the run down on stuff todo:

• New signing box for epel. This just keeps the fedora and epel keys separate and lets the two groups of signers control of their keys better.
• About a day with lmacken and some epel-signers to tweak stuff togther. lmacken doesn't have access to the signing keys. The initial work to add the EPEL targets should be easy but there's places that will have hardcoded "fedora" that will need to be found and updated. So a few iterations of tweak, test, tweak will be needed.
• Probably deploy after change freeze since tweaks will likely be widespread in the code... so could impact the ability to get fedora beta ready.

We also discussed:
* Separate mash box for bodhi.
* This could have two benefits:
* Deploy during change freeze since tweaks would occur here and not impact the Fedora bodhi
* Spread the load of mashing
* Also has some cons:
* Requires teaching the front ends to talk to multiple backends -- complexity
* NFS is our bottleneck, adding new masher boxes probably won't help

• Do the pushes manually. This would entail:
  1. they'd have to run the signing scripts
  2. move all of the builds to the appropriate koji tags
  3. run mash.
• Cons: this leaves out updateinfo.xml.gz, email notices, bugzilla interaction, repo sanity checking, build tag/status sanity checking
• the current push scripts might be adapted to send email but we wouldn't have bugzilla and repo sanity checks and build checks would have to be recoded