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

[Joe Brockmeier]

On 04/22/2015 03:31 PM, Matthew Miller wrote:
> And I've heard a few other good ideas, including FESCo liasons for
> Cloud/Server/Workstation working groups helping to track individual
> changes more closely throughout the process.

Sign me up.

> But, in general, I feel sad about the outcome here. This would have
> been very useful to Fedora users, and help us in a particular target
> area in which we need to grow. Rather than focusing on this particular
> thing, though, I want to go with the assumption that in the future, we
> _will_ have more new and changing deliverables.

This is discouraging and disappointing. Yes, I totally get that we need
to have processes and procedures that protect our already hard-working
folks from being overrun with last-minute requests, changing
deliverables, and all that. I do. I get it.

But this ... we did spell this out in the request. Maybe we didn't do it
properly, but it was in the change request. We had someone rush the
work. IT WORKS. There's no reason not to ship this other than to stand
on a principle of enforcing procedures.

This is a loss for the project and our users.

> I see where Dennis is coming from in frustration with people not
> following process. That can causes a lot of extra work for _other_
> people, and can result in lower-quality results which we might not be
> proud of as a project, and which can erode trust in Fedora overall.
> 
> However, there's another side too. Docker was the last big thing, but
> who knows what the next one will be? Increasing communication and
> long-term planning is one thing, but often with these emerging
> technologies we're _really_ making it up as we go along. When these
> things have little negative impact outside of their own space (they are
> effectively self-contained changes _except_ for releng needs), and have
> significant benefits for the user community and for Fedora's adoption
> and growth, I *want* the limits pushed further than they currently can
> be.

Not only is the project making it up as we go along, so are participants
and volunteers. I know I get it wrong occasionally, but I do *try* to
follow procedures. The thing is, we need to make it easier for people to
contribute, not raise barriers. How would someone who isn't paid to work
on open source feel about this? Would they come back to do this again?

Best,

jzb
-- 
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb at redhat.com | http://community.redhat.com/
Twitter: @jzb  | http://dissociatedpress.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/rel-eng/attachments/20150422/b082e043/attachment.sig>