[whatwg] Google's use of FFmpeg in Chromium and Chrome Was: Re: MPEG-1 subset proposal for HTML5 video codec

2009-06-01 Thread Chris DiBona
rk hard to ensure we are in compliance with these licenses Chris DiBona On Mon, Jun 1, 2009 at 11:21 AM, wrote: > > Thank you for a very informative reply.  Inline comments follow. > > --- On Sun, 5/31/09, Gregory Maxwell wrote: > >> From: Gregory Maxwell >> Subj

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome

2009-06-02 Thread Chris DiBona
Looping in Dannyb (who may not be on the list, so if necessary, I'll forward) as I'm in the midst of a conference and can't give this the attention it deserves. Chris On Tue, Jun 2, 2009 at 1:19 PM, Håkon Wium Lie wrote: > Also sprach Chris DiBona: > >  > To be clea

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome Was: Re: MPEG-1 subset proposal for HTML5 video codec

2009-06-02 Thread Chris DiBona
Looping in Danny (in transit) On Wed, Jun 3, 2009 at 1:38 AM, Geoffrey Sneddon wrote: > > On 2 Jun 2009, at 02:58, Chris DiBona wrote: > >> One participant quoted one of the examples from the LGPL 2.1, which >> says "For example, if a patent license wou

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome Was: Re: MPEG-1 subset proposal for HTML5 video codec

2009-06-03 Thread Chris DiBona
Yeah, this is really pretty difficult stuff. The lgpl is probably the least understood and most complicated free software licenses. Chris On Wed, Jun 3, 2009 at 2:49 PM, Silvia Pfeiffer wrote: > On Wed, Jun 3, 2009 at 3:28 PM, Daniel Berlin wrote: >> On Tue, Jun 2, 2009 at 11:51 PM, Gregory Max

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome Was: Re: MPEG-1 subset proposal for HTML5 video codec

2009-06-03 Thread Chris DiBona
I mostly wanted to explain our position on the use of the library and the LGPLs. Danny keeps it all straight for us. Happy hacking, everyone! Chris On Wed, Jun 3, 2009 at 3:40 PM, Anne van Kesteren wrote: > On Wed, 03 Jun 2009 09:34:08 +0200, Chris DiBona wrote: >> Yeah, this is real

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome

2009-06-06 Thread Chris DiBona
At this point I feel like we're giving open source advice to teams outside of Google, which is beyond our mission. We're comfortable with our compliance mission and feel it is accurate and correct. Other companies and people need to make their own decisions about compliance. Chris On Sun, Jun 7,

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome

2009-06-06 Thread Chris DiBona
> To me, it seems more like Google doesn't really want to take a position in > the matter regarding codecs and is taking the "weird" way out by using > ffmpeg. Given Google's dominance in search, which tends to bring people to > at least look at Google's products, anything Google does is examined w

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome

2009-06-07 Thread Chris DiBona
> The incredibly sucky outcome is that Chrome ships patent-encumbered > "open web" features, just like Apple. That is reprehensible. Reprehensible? Mozilla (and all the rest) supports those same "open web" features through its plugin architecture. Why don't you make a stand and shut down compatibi

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome

2009-06-07 Thread Chris DiBona
Jun 8, 2009 at 9:29 AM, Nils Dagsson Moskopp wrote: > Am Montag, den 08.06.2009, 09:24 +0900 schrieb Chris DiBona: >> > The incredibly sucky outcome is that Chrome ships patent-encumbered >> > "open web" features, just like Apple. That is reprehensible. >> &

Re: [whatwg] Google's use of FFmpeg in Chromium and Chrome

2009-06-07 Thread Chris DiBona
e spec in the end. Chris On Mon, Jun 8, 2009 at 10:10 AM, Robert O'Callahan wrote: > On Mon, Jun 8, 2009 at 12:42 PM, Chris DiBona wrote: >> >> I'm perfectly calm, what people need to realize is that this issue is >> actually not about submarined patents (more like airc

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
c encoding efficiency. . Chris On Fri, Jun 12, 2009 at 10:02 AM, Mike Shaver wrote: > Apologies for the poor threading, I wasn't subscribed when the message > here was sent. > > In http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-June/020237.html > Chris DiBona wrote:

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
> On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: >> Comparing Daily Motion to Youtube is disingenuous. > > Much less so than comparing "promotion of H.264-in- via > Google's sites and client" to "support for legacy proprietary content > via plugi

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
> We certainly believe so, but I'm certainly not qualified to evaluate > the different techniques. > > Would Theora inherently be any less able to than any other codec > system, though?  I hope you're not saying that it has to be H.264 > forever, given the spectre of the streaming license changes a

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
Let me ask David Sparks and see where it went, I remember we had it in the inital drops, or thought we did. On Sat, Jun 13, 2009 at 10:35 AM, Mike Shaver wrote: > On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: >> actually shipping with Theora (also on android, too) > > I wa

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
It'll take a little while, I'm travelling a bit this month (brazil , new york, etc..) Chris On Sat, Jun 13, 2009 at 10:55 AM, Håkon Wium Lie wrote: > Also sprach Chris DiBona: > >  > > I don't think the bandwidth delta is very much with recent (and >  > >

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-14 Thread Chris DiBona
2009 at 1:15 AM, Gregory Maxwell wrote: > On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: >> Comparing Daily Motion to Youtube is disingenuous. If yt were to >> switch to theora and maintain even a semblance of the current youtube >> quality it would take up most ava