kde-pim dev needed, for a sponsored open source effort, to remove akonadi

[Paul Vixie]

Peter Humphrey wrote:
> On Saturday, 17 March 2018 15:45:31 GMT Paul Vixie wrote:
>
>> A few years ago i spent a couple of hours trying to build kde-pim from
>> sources, so that i could [...] propose improvements in the form of code
>> changes. i failed.
>
> Have you thought of trying on a Gentoo system? Everything is compiled from
> sources - even the compilers - so all the code and logs are easily
> available.

i do not think that the choice of base system or the base system's 
attitude toward its own source code will change my experience of 
building kde-pim from sources. but if it will, i'll switch. vm's are 
cheap. my production env is freebsd and tumbleweed, but for dev, i've 
got just about everything else.

>> If putting akonadi into kde-pim with an obvious lack of broad testing and
>> acceptance was possible, then patches to improve its stability should also
>> be allowed in with the same absence of broad acceptance andtesting. we
>> should not have a higher acceptance criteria for fixing itthan we had for
>> breaking it.
>
> I don't understand your point here. How is the code to improve, if you still
> accept the same quality as what's gone before?

that question doesn't even come up if what's here today is pretty 
unusable. brownian motion, up to just below the point where the code no 
longer compiles, would not be worse.

therefore the operable question is, why make it harder to fix than it 
was to break?

-- 
P Vixie