The future of FTBFS?

[Matt Domsch]

As my job and family responsibilities have shifted over time, I have
been giving less and less attention to the FTBFS (fails to
build from source) process that I started 5 years ago on a "see, it
_can_ be done" lark.  

I think FTBFS has been valuable.  Through the process, hundreds, maybe
even a couple thousand, bugs have been discovered and fixed before
they affected our users or downstream remixes and derivatives.  I find
the breakage, file bugs, and the package owners fix them.  Sure,
I get the occasional "why are you filling my mailbox with this"
message, but overall, the response has been very positive.

Question is, is it valuable enough to the Project as a whole, that
someone else should take it on now?

If so, should it become standard process of the Project, rather than a
personal project?  With resources (koji servers) owned and managed by
the project, instead of the servers I could scrounge?

FTBFS cuts across Packagers, BugZappers, QA, Developers, and Release
Engineering.  As such, I think it needs to be part of standard
processes for the Project.

Thanks,
Matt

-- 
Matt Domsch
Technology Strategist
Dell | Office of the CTO