How *could* we make it more easy to deliver late-breaking deliverables?

[Paul W. Frields]

On Fri, Apr 24, 2015 at 12:04:46PM -0400, Matthew Miller wrote:
> On Fri, Apr 24, 2015 at 10:50:02AM -0500, Adam Miller wrote:
> > >> release engineering. I think in an ideal world, that would be very
> > >> nice, and not just release engineering. Once the changes are accepted
> > >> by FESCo, everyone would look at them and say "okay, I see this needs
> > >> to be done, and that's in my area, so I'll make sure that goes on my
> > >> worklist".
> > > Everyone look at them every time they change? There are days I barely
> > > get time to read my email! Sorry I don't believe that to be scalable.
> > I actually agree with this, I don't think it's realistic. We had an
> 
> To be clear, I *also* don't think it's realistic. (That context got
> lost in the quoting.)
> 
> > I recently sent an RFC/Proposal email to the Rel-Eng list about using
> > a kanban-style approach to projects[0] and using a task board with
> > cards. I was curious if this is something that maybe would be useful
> > for FESCo also to plan/track Releases on? Then Rel-Eng could be tagged
> > on cards in the board that need attention, then that could trigger the
> > discussion about what's needed. This would kind of centralize the
> > discussion in one place and might help, thoughts?
> 
> I'm definitely in favor; also, I'm thinking it might be an area where
> the Fedora Program Manager could provide some administrative
> assistance, so tracking this "metawork" doesn't become an _extra_
> burden on rel-eng.

Also, in case it wasn't clear, Matthew and I are reaching out to
program management folk to try and get support for expanding into
areas like this.

-- 
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