#6172: Grant admin permission on staging Koji to mizdebsk

[Fedora Release Engineering]

#6172: Grant admin permission on staging Koji to mizdebsk
------------------------------+-----------------------
  Reporter:  mizdebsk         |      Owner:  rel-eng@…
      Type:  task             |     Status:  new
 Milestone:  Fedora 22 Final  |  Component:  koji
Resolution:                   |   Keywords:
Blocked By:                   |   Blocking:
------------------------------+-----------------------

Comment (by ausil):

 Replying to [comment:2 mizdebsk]:
 > Replying to [comment:1 kevin]:
 > > I really don't like the idea of importing srpms. We should be able to
 do builds like production.
 > Sure, I can run builds from SCM (pkgs.stg), but I would prefer to avoid
 using names conflicting with real Fedora packages so I'll at least need
 some package names added to tag listing, for example koschei-test-pkg1
 through 100:
 > {{{
 > stgkoji add-pkg --owner mizdebsk f23 $(for i in $(seq 100); do echo
 koschei-test-pkg$i; done)
 > }}}

 That should all be done from staging pkgdb. testing the full process for
 adding new packages. I guess by whitelisting in the initial request you
 mean adding the package to koji. I do not see that you need admin perms
 for any of that. it is things that should all happen as part of the normal
 workflows. add or retire a package in staging pkgdb should add and block
 in koji. any time a package is added or blocked koji will generate new
 repos. or if you do builds. I do not see a need to grant permission just
 to make newRepos and builds should all be from staging pkgs. there are
 times in production that a newRepo needs generated for epel, without
 giving admin permissions, I would be okay with working out a way to enable
 people to request a newrepo for a limited set of targets, developing it in
 stage makes sense.

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6172#comment:3>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project