[linux-dvb] [v4l-dvb-maintainer] [Wanted] dvb-ttpci maintainer
mrechberger at gmail.com
Fri Sep 26 21:26:10 CEST 2008
On Fri, Sep 26, 2008 at 8:43 PM, hermann pitton <hermann-pitton at arcor.de> wrote:
> Am Freitag, den 26.09.2008, 17:14 +0200 schrieb Oliver Endriss:
>> hermann pitton wrote:
>> > Except of course a majority of plumbers at the same place at the same
>> > time can create/propose some facts.
>> IMO decisions must be made where the community is, i.e. on the mailing
>> list. Not at a conference, no matter whether it is at one end of the
>> world or on the dark side of the moon. ;-(
>> To make it absolutely clear:
>> I did not leave _because_ S2API was selected.
>> I left because it was done _this_way_.
>> Good for those, who are fine with these methods. I am not.
> What the others should have done previously?
> They could only wait.
> What should Mauro have done better?
> Say, after Manu's pull request suddenly appeared, thanks, I merge it now
> over night and forget about all efforts others did.
>> > If you attack people such hard as Manu did, also behind the visible
>> > lines sometimes, Marcel had a copy from me concerning Mauro and did say
>> > nothing, you must not wonder about people starting to defend themselves.
>> I consider flame wars ridiculous. I did not participate, and I will not
>> participate in the future.
>> I believe that I know very well what is going on. (During more than 30
>> years in software development I have seen all kinds of problems. I know
>> how people react and why things happen.)
>> > For sure the dirt was not started from v4l people.
>> > Think it over.
>> Unlikely. I made this decision after sleeping over it for a few days.
>> Now I feel much better.
> You are the most trusted guy on linux-dvb for me.
> Markus should have accept your help instead giving Mauro an ultimatum to
> merge his stuff within the next 24 hours and we would have one problem
I really have to write that it was a good decision to stay away from
my code previously.
Not because I didn't follow some suggestions which seemed to be
ridiculous to me (and due
general lack of knowledge others and I had), it's because the code was
not manufacturer supported
at that time.
The supported code which redesigned alot parts of the old driver are
improved alot and those
changes were also influenced by business customers who back then
thought "we could use that work
since it states out it supports xyz". Those business customers did in
depth testing of their scenarios
and requirements and submitted valuable bugreports and or even patches
(eg VBI support, signal strength
improvements due wrong firmwares -or even wrong register settings,
mode switchover testing etc.)
I am not at all angry at anyone denying to merge the code around a
year ago since the whole situation
changed, overall the bad communication back then which definitely was
not driven by any community
rather than personalities just resulted in that overall bad
atmosphere. I think all that is far away now
and many things changed to a positive result for endusers in terms of
code quality now.
There are still some outstanding points on the list, in order to not
break other devices it requires alot
testing. It's being worked on I can write. Looking at the work which
has been done at Xceive even their
supplied code changed due the firmware upgrades and we supported them
in order to fix some smaller
Due the whole development I also have to write that I have alot
respect of what the Empia
windows developer is and was doing in order to support all those
possible device configurations it's a
very complicated task, and he's also on it fulltime for some good reason.
> Put at least a sticker on such guys like Uwe/Derek and Manu should do it
> as well.
> I'm open for everything fair to find a solution.
> v4l-dvb-maintainer mailing list
> v4l-dvb-maintainer at linuxtv.org
More information about the linux-dvb