Final thoughts/votes on Kubuntu Policy

[Scott Kitterman]

On Tuesday, August 05, 2014 21:36:24 Harald Sitter wrote:
> On Tue, Aug 5, 2014 at 8:40 PM, Scott Kitterman <ubuntu at kitterman.com> 
wrote:
> > On Tuesday, August 05, 2014 19:55:07 Harald Sitter wrote:
> >> On Tue, Aug 5, 2014 at 7:45 PM, Scott Kitterman <ubuntu at kitterman.com>
> > 
> > wrote:
> >> > I, for one,
> >> > think the notion that we won't apply known fixes because upstream is
> >> > non-
> >> > responsive is silly.  I don't intend to be bound by it.
> >> 
> >> Where does the fix come from then?
> > 
> > Could be defective Python code I figured out by myself (for reference,
> > this
> > exact scenario is why we had an even sort of working displayconfig in
> > hardy - if this policy had been in effect, it would have had to be
> > removed and not replaced since there was no replacement available).
> 
> so why did you not pick up maintainership?

Because it would have needed a full rewrite to work with the then brand new X 
stack reliably.  We were going to have a new tool for Intrepid anyway, so 
beating it into sort of working was enough for Kubuntu and I'm certainly not 
qualified to take on upstream development for all of KDE.

Scott K