Gentoo Archives: gentoo-dev

From: Alexis Ballier <aballier@g.o>
To: gentoo-dev@l.g.o
Subject: Re: Discussing defaults (Was: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in virtual/ffmpeg: ffmpeg-9.ebuild ChangeLog ffmpeg-0.10.2-r1.ebuild)
Date: Mon, 11 Feb 2013 18:39:52
Message-Id: 20130211153934.107b3037@gentoo.org
In Reply to: Re: Discussing defaults (Was: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in virtual/ffmpeg: ffmpeg-9.ebuild ChangeLog ffmpeg-0.10.2-r1.ebuild) by Peter Stuge
1 On Mon, 11 Feb 2013 17:22:16 +0100
2 Peter Stuge <peter@×××××.se> wrote:
3
4 > Alexis,
5 >
6 > Alexis Ballier wrote:
7 > > All of this because ~10 people cannot work together, well, really,
8 > > thank you :)
9 >
10 > Do you have experience from being in a similar situation? You are
11 > being quite judgemental.
12 >
13 > There are absolutely situations where people so different that
14 > cooperation simply can't work. It's pretty lame, but unless you
15 > yourself participate at least on the same level as everyone else
16 > (on both sides) you really don't get much of a say.
17
18 Yes, sorry, I now realize what I wrote is understood differently from
19 what I meant. I was not criticizing the people, but rather the current
20 situation. Luca is the one to ask if you want to know more about this,
21 certainly not me. I am simply a consumer annoyed of having to write
22 more and more complicated code to support both sides.
23
24 I am aware that the split did not come out of nothing, and considering
25 the vast majority of core FFmpeg developers by that time are now
26 involved in libav, libav is likely to be the side of 'those who are
27 right'. However, as I said, maybe with an incorrect tone, I do not
28 think libav ignoring what happens in ffmpeg to be a pragmatic attitude
29 and believe it is mainly hurting applications trying to do their
30 best in supporting both, and users wanting the extra bugfixes or featues
31 from ffmpeg or the better review process from libav. The critic was
32 directed towards this, which I believe should be orthogonal to the
33 reasons of the split.
34
35 Finally, I would really love to see some will in reopening the
36 discussions, be it to merge back (I think that's very unlikely, but
37 let's not lose hope) or to decide that there is nothing more to be done
38 and find a sane way out of this lose-lose situation (soname change, or
39 anything better).
40
41 > It's easy to tell people to "stop fighting, just get along" - but
42 > I believ that intentional fighting is quite rare. It's more likely
43 > about trying to make one's point.
44 >
45 > That requires communication, but communication is not always
46 > possible. (I don't mean transmissions back and forth, I mean
47 > desire to understand the transmissions.)
48 >
49 > For a long time I idealized open source as being an ideal community,
50 > where communication always worked because everyone wanted it to. But
51 > that's unfortunately not at all the case.
52
53 Yep, thanks for shaking me on this, it seems I should reread twice
54 before hitting send on an email since I fell in the same trap. Again,
55 apologies if what I wrote has been taken personally, esp. to those that
56 tried their best to avoid the split.
57
58 [...]
59 > > I consider FFmpeg superior, but can understand there are different
60 > > opinions, however, if this is to lower the tree quality
61 >
62 > Quality is not a very helpful metric, because it means completely
63 > different things for different people. Some people value code
64 > readability, maintainability, and correctness very high, other people
65 > value having a new idea halfway implemented and released even if it
66 > only kindasorta works and is not at all reliable and not on par with
67 > previous parts of the code.
68 >
69 > I see a tendency in myself and in others to not care about what
70 > happens on the inside when thinking merely as a user. I see many many
71 > people complain about the insides when they are not happy with how it
72 > performs. I very rarely see people actually dig in to help fix up the
73 > insides. The same pattern exists in pretty much all projects that I
74 > know of, and it is quite natural - there are more users than
75 > developers.
76
77 Quality here is: Everything that works with FFmpeg works with libav,
78 and vice-versa. Once that is true, then the default can be what is
79 deemed better. In this precise case it is controversial, so once
80 everyone has expressed his arguments and reasons then default should be
81 what the majority prefers (and here, it seems the majority goes with
82 libav).
83
84 [...]
85 > > libav should realize they are the actual fork (this is now pretty
86 > > clear since the takeover failed and ffmpeg didn't collapse...) and
87 > > also rename their libraries so that the internal libav/ffmpeg
88 > > fights would not affect their users anymore and projects could use
89 > > what they think best...
90 >
91 > Unless libav considers the API too broken to still be functional I
92 > don't see the point of differentiation. A little bit of competition
93 > can be good overall even though it is more stressful for both sides.
94 > The most important thing is what I asked for already -
95 >
96 > That users inform themselves, and make informed decisions.
97
98 For distributors it does matter: if we start to have libav-only or
99 ffmpeg-only packages then users get the choice on what package to use,
100 not the implementation. If there is a differentiation, then upstream
101 decides what they think is best and that's about it. It would not kill
102 competition, rather the contrary I believe.
103
104 Alexis.

Replies