RFC: rel-eng tooling development workflow

[Paul W. Frields]

On Fri, Apr 24, 2015 at 05:32:09PM -0500, Adam Miller wrote:
> Alright, this is 4 votes for pagure if I count my own. I'll open a
> ticket in trac to discuss this email thread during the rel-eng meeting
> next week and come to a final decision. From there I'll see where I
> can be helpful in making the transition happen (pending the results of
> the meeting).

The thread kind of moved on into a number of implementation areas, but
one thing to clarify in the workflow discussion is the need to have
plenty of empowered committers for the new tools.  With more people
empowered to do code reviews and approve pull requests we can make
more progrss.  (It also doesn't hurt to increase community involvement
and attractiveness over time!)

I recently organized a new small subteam in Fedora Engineering around
release infrastructure:

https://fedoraproject.org/wiki/Fedora_Engineering#Release_Infrastructure_Team

This doesn't mean everyone in that subteam is working 100% on the
project and release tooling issues, like Adam is.  But their
individual major projects are highly related (like Bodhi, cloud
images, etc.).  Having this subteam helps align our work a little
better, beyond just having more hands.  It's not just about this
subteam, though; the workflow should support committers across the
community.

-- 
Paul W. Frields                                http://paul.frields.org/
  gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233  5906 ACDB C937 BD11 3717
  http://redhat.com/   -  -  -  -   http://pfrields.fedorapeople.org/
    The open source story continues to grow: http://opensource.com