-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Clément,
On 13/06/15 20:17, Clément Bœsch wrote:
>
> Ah, if you're interested in testing... http://coverage.ffmpeg.org/
> will give you an idea about how much or test suite covers the code
> base. You can see that it's not bad but there are many
On Wed, Jun 10, 2015 at 04:26:49PM +0100, George Boyle wrote:
> Hello,
>
> I was wondering what is the best way to begin getting involved in
> contributing to ffmpeg/libav*? I've been a big fan of the project for
> years. I've been an observer on the mailing list, and have closely read
> the guide
Hi George,
On Thu, Jun 11, 2015 at 1:57 PM, George Boyle wrote:
> Hi Ronald,
>
> On 11/06/15 17:01, Ronald S. Bultje wrote:
> >
> > It would also be helpful if you could identify what you would like to be
> > doing, i.e. do you have any particular aspect that you find particularly
> > exciting o
Hi Ronald,
On 11/06/15 17:01, Ronald S. Bultje wrote:
>
> It would also be helpful if you could identify what you would like to be
> doing, i.e. do you have any particular aspect that you find particularly
> exciting or intriguing and would like to learn more about? E.g. you might
> like one of v
Hi George,
On Wed, Jun 10, 2015 at 11:26 AM, George Boyle wrote:
> Hello,
>
> I was wondering what is the best way to begin getting involved in
> contributing to ffmpeg/libav*? I've been a big fan of the project for
> years. I've been an observer on the mailing list, and have closely read
> the
Great! Thank you both (Carl and Michael) for the suggestions. I'll begin
by having a look at the coverity one and see how I get on.
Best wishes,
George
On 10/06/15 17:03, Michael Niedermayer wrote:
> On Wed, Jun 10, 2015 at 04:26:49PM +0100, George Boyle wrote:
>> Hello,
>>
>> I was wondering wh
On Wed, Jun 10, 2015 at 04:26:49PM +0100, George Boyle wrote:
> Hello,
>
> I was wondering what is the best way to begin getting involved in
> contributing to ffmpeg/libav*? I've been a big fan of the project for
> years. I've been an observer on the mailing list, and have closely read
> the guide
George Boyle thebuds.net> writes:
> I was wondering what is the best way to begin getting
> involved in contributing to ffmpeg/libav*?
You could find a bug and fix it, or choose one from
trac.ffmpeg.org.
You could add documentation for a muxer, demuxer,
decoder or whatever you find that is mi
Hello,
I was wondering what is the best way to begin getting involved in
contributing to ffmpeg/libav*? I've been a big fan of the project for
years. I've been an observer on the mailing list, and have closely read
the guidelines on the website, so I have a fair idea of how the
development/review
