[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Kaffeine bugreport complaint
From:       Daniel Nicoletti <dantti12 () gmail ! com>
Date:       2016-08-10 19:04:34
Message-ID: CACo8zOfPNDf1C0OgZUVLa5rnFb-aB7zFYZ70PxT7_-HftK2RQQ () mail ! gmail ! com
[Download RAW message or body]

2016-08-10 15:42 GMT-03:00 Markus Rechberger <mrechberger@gmail.com>:
> Some people are using that and the patch obviously is a FIX.
>
> It has been mentioned that it will take weeks until the proposed way
> would be available.
> Until then the code in question is uninitialized.

You are a company, help this get's finished sooner.

> There is absolutely no reason to not fix it.
> This code has been unmaintained for years but it is still getting
> picked up by distributions.
> It is worth nothing to point out that now all the distributions who
> pull this version have to fix it (while it worked with the version
> before Mauro has touched it).

It was, so you could have picked the maintainership. Now he stepped
up and is working on it and you show up complaining and what not.

> We manufacture devices and support not only Linux. I think everyone
> should be happy if manufacturers directly support linux (regardless of
> opensource or not - those who don't like it aren't forced to buy
> them).
> And those devices are available since 2008 as well.
> Kaffeine is the only project having problems at the moment, all other
> ones directly query /dev/dvb directly and they have no problem.

I really think you should pay him a beer ;)

> That said if this is the attitude of the KDE project in general please
> let me know it should also be a good lesson for other manufacturers to
> avoid digging into KDE projects and just support other projects.

It's called respect, and we respect his maintainership, if I were unhappy
I'd probably fork it. Manufacturers are making money out of our software
so either pay him or leave him alone.

> As mentioned the bugfix is 3 lines, any sane person would just add it
> everything else is absolute nonsense.
> The noise this has to generate is just unbelievable.

You are generating noise. There is no point in noise, nor will you get
attention here, if you were a bit smart you could have worked on another
kind of patch/approach.

>
> Best Regards,
> Markus Rechberger
>
>
> On Wed, Aug 10, 2016 at 8:23 PM, ChALkeR <chalkerx@gmail.com> wrote:
>> For reference, https://bugs.kde.org/show_bug.cgi?id=365083#c11 lists purely
>> technical issues with the proposed approach, and that serves as valid
>> (technical) reasons for not accepting the proposed patch.
>>
>> 2016-08-10 21:14 GMT+03:00 Daniel Nicoletti <dantti12@gmail.com>:
>>>
>>> Hi,
>>>
>>> I had the tedious reading of the bug report and IMHO it's a
>>> valid WONTFIX, if I were the maintainer I wouldn't fix.
>>>
>>> The maintainer is going to DROP that code to rely on the work
>>> of another library, so why fixing it?
>>>
>>> I might agree that the patch looks simple and doesn't looks like
>>> it's going to break things, but it's not my code.
>>>
>>> I'd say you can do 3 things.
>>> 1. Fork the thing
>>> 2. Make sure libdvd can detect you card (I'd go with this so others can
>>> benefit)
>>> 3. Ask your downstream distribution to keep the patch, this
>>> is the option that might be easier for you and downstream
>>> have to do this kind of stuff all the time...
>>>
>>> It worth nothing coming to this mailing list to complain about
>>> a maintainer, he does that for free and we won't fire him.
>>>
>>> Any KDE developer can push the fix but that's not polite, unless
>>> he is not an active maintainer we could do it.
>>>
>>>
>>> 2016-08-10 14:11 GMT-03:00 Markus Rechberger <mrechberger@gmail.com>:
>>> > Hi,
>>> >
>>> > there is a bug, and a fix available but the maintainer won't fix it
>>> > due personal issues
>>> > I have asked him kindly at least several times even before
>>> > participating in bugzilla to fix this issue, that's why I'm not
>>> > friendly at all to that guy anymore.
>>> >
>>> > The bug is even caused by him.
>>> >
>>> > The fix is a 3liner and available in the bugzilla
>>> > https://bugs.kde.org/show_bug.cgi?id=365083
>>> >
>>> > Can someone else commit this fix and resolve the issue?
>>> > Basically it was added in 2014 and he broke it a few weeks ago.
>>> >
>>> > I'd really appreciate if someone could just jump in and fix it. The
>>> > fix is so ridiculous small and is getting way more attention than it
>>> > should.
>>> >
>>> > Best Regards,
>>> > Markus
>>>
>>>
>>>
>>> --
>>> Daniel Nicoletti
>>>
>>> KDE Developer - http://dantti.wordpress.com
>>
>>



-- 
Daniel Nicoletti

KDE Developer - http://dantti.wordpress.com
[prev in list] [next in list] [prev in thread] [next in thread]