Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On Sun, Aug 07, 2016 at 07:47:19PM -0400, Ronald S. Bultje wrote: > Hi, > > On Fri, Aug 5, 2016 at 6:20 PM, Michael Niedermayer> wrote: > > > On Wed, Aug 03, 2016 at 07:48:36PM -0400, Ronald S. Bultje wrote: > > > Hi, > > > > > > On Wed, Aug 3, 2016 at 1:57 PM, Michael Niedermayer > > > > > wrote: > > > > > > > Hi all > > > > > > > > Sun, Jul 31, 2016 at 10:01:00PM +0200, Michael Niedermayer wrote: > > > > > Hi all > > > > > > > > > > you have a great idea for a Outreachy task or a GSoC task ? > > > > > Or something you always wanted to do but never had the time and > > > > > it would fit in the time for GSoC/Outreachy ? > > > > > Or some feature you always wanted which would fit as a task? > > > > > Also keep in mind Outreachy is more flexible and not limited to > > > > > coding tasks ! > > > > > reply and dump it here below: > > > > > > > > ping ? > > > > > > > > also cc-ing ffmpeg-user > > > > > > > > or are all feature requests on trac fake and noone has anything they > > > > think should be implemented ? > > > > > > > > we need ideas for Outreachy, the page is EMPTY: > > > > https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 > > > > > > > > > I have some ideas. Most are TODOs / extensions to stuff I wrote that I > > > never ended up doing myself. Some might be hard. > > > > > > vp9: > > > - avx2 loopfilter functions. Qualification task: explain to me without > > any > > > guidance why it's an issue for AVX2 (or SSE2) that the loopfilter in > > vp9.c > > > works on 8px blocks, and explain how I solved that to work on 16px blocks > > > to use SSE2 instructions, and likewise explain how you would extend that > > to > > > work on 32px blocks. > > > > the Qualification task sounds interresting, we required for applicants > > though always to submit a patch that then gets reveiwed and applied. > > Generally a small/tiny part of the whole project. > > So i would suggest to require the applicant to do that as well as your > > Qualification task > > > > Progress on cols-only C wrapper sounds like a good qual task. > > please add any projects you want to mentor to the page. > > > I noticed the deadline is Aug 22, I'll be on vacation until end of Aug so I > won't have time to either add things to wiki or to help students get > started. Should probably hold this off until the next round. If the dates for this round match last years then For this round participating organizations will be announced in september, applicants likely wont do much before september the internship period will likely be december to march the next round after that participating orgs would likely be announced in february and the internship would be may to end of august so if you have no time in august next year then you certainly cannot mentor in the next round, this years august has no impact on either round. also this round is in winter the next is in summer and will overlap with GSoC. The winter round allows people to participate who have no time in the northern summer (generally people living on the southern side of that blue ball i guess) So IMO it makes sense for us to participate in this round, in the next (if we are accepted to GSoC again) we would have to split resources between 2 "Sponsoring Programs" Also just to remind we need an admin for this round too! [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are best at talking, realize last or never when they are wrong. signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
Hi, On Fri, Aug 5, 2016 at 6:20 PM, Michael Niedermayerwrote: > On Wed, Aug 03, 2016 at 07:48:36PM -0400, Ronald S. Bultje wrote: > > Hi, > > > > On Wed, Aug 3, 2016 at 1:57 PM, Michael Niedermayer > > > wrote: > > > > > Hi all > > > > > > Sun, Jul 31, 2016 at 10:01:00PM +0200, Michael Niedermayer wrote: > > > > Hi all > > > > > > > > you have a great idea for a Outreachy task or a GSoC task ? > > > > Or something you always wanted to do but never had the time and > > > > it would fit in the time for GSoC/Outreachy ? > > > > Or some feature you always wanted which would fit as a task? > > > > Also keep in mind Outreachy is more flexible and not limited to > > > > coding tasks ! > > > > reply and dump it here below: > > > > > > ping ? > > > > > > also cc-ing ffmpeg-user > > > > > > or are all feature requests on trac fake and noone has anything they > > > think should be implemented ? > > > > > > we need ideas for Outreachy, the page is EMPTY: > > > https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 > > > > > > I have some ideas. Most are TODOs / extensions to stuff I wrote that I > > never ended up doing myself. Some might be hard. > > > > vp9: > > - avx2 loopfilter functions. Qualification task: explain to me without > any > > guidance why it's an issue for AVX2 (or SSE2) that the loopfilter in > vp9.c > > works on 8px blocks, and explain how I solved that to work on 16px blocks > > to use SSE2 instructions, and likewise explain how you would extend that > to > > work on 32px blocks. > > the Qualification task sounds interresting, we required for applicants > though always to submit a patch that then gets reveiwed and applied. > Generally a small/tiny part of the whole project. > So i would suggest to require the applicant to do that as well as your > Qualification task > Progress on cols-only C wrapper sounds like a good qual task. please add any projects you want to mentor to the page. I noticed the deadline is Aug 22, I'll be on vacation until end of Aug so I won't have time to either add things to wiki or to help students get started. Should probably hold this off until the next round. Ronald ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On Wed, Aug 03, 2016 at 07:48:36PM -0400, Ronald S. Bultje wrote: > Hi, > > On Wed, Aug 3, 2016 at 1:57 PM, Michael Niedermayer> wrote: > > > Hi all > > > > Sun, Jul 31, 2016 at 10:01:00PM +0200, Michael Niedermayer wrote: > > > Hi all > > > > > > you have a great idea for a Outreachy task or a GSoC task ? > > > Or something you always wanted to do but never had the time and > > > it would fit in the time for GSoC/Outreachy ? > > > Or some feature you always wanted which would fit as a task? > > > Also keep in mind Outreachy is more flexible and not limited to > > > coding tasks ! > > > reply and dump it here below: > > > > ping ? > > > > also cc-ing ffmpeg-user > > > > or are all feature requests on trac fake and noone has anything they > > think should be implemented ? > > > > we need ideas for Outreachy, the page is EMPTY: > > https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 > > > I have some ideas. Most are TODOs / extensions to stuff I wrote that I > never ended up doing myself. Some might be hard. > > vp9: > - avx2 loopfilter functions. Qualification task: explain to me without any > guidance why it's an issue for AVX2 (or SSE2) that the loopfilter in vp9.c > works on 8px blocks, and explain how I solved that to work on 16px blocks > to use SSE2 instructions, and likewise explain how you would extend that to > work on 32px blocks. the Qualification task sounds interresting, we required for applicants though always to submit a patch that then gets reveiwed and applied. Generally a small/tiny part of the whole project. So i would suggest to require the applicant to do that as well as your Qualification task > - coefficient reading optimizations or arithmetic symbol reading > optimizations. I think this is too hard but it would be an amazing speed > optimization in vp9 decoding, since this is where pretty much all runtime > is spent after other optimizations. > - tile threading. This may actually be a nice qual task for the next block > since this is quite easy. > > frame/slice-mt: > - implement a mode that allows combining those. Qual task could be to > implement vp9 tile threading or something like that. Final deliverable > would implement this for at least vpN codec and one h.26x codec. > > I'll think about others. I'm willing to mentor the above maybe. please add any projects you want to mentor to the page. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No great genius has ever existed without some touch of madness. -- Aristotle signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On Wed, Aug 03, 2016 at 11:24:16PM +0100, Kieran O Leary wrote: > Hi > > On 3 Aug 2016 6:58 p.m., "Michael Niedermayer"> wrote: > > > > Hi all > > > > > we need ideas for Outreachy, the page is EMPTY: > > https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 > > > > How about EBU-STL subtitle decoding? It's currently unsupported. It's a non > text based subtitle format that is used in a broadcast environment. I'm > not sure if that is too specific to be of interest. Feel free to add this to the page also do we have someone interrested in mentoring a student doing this project? thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The educated differ from the uneducated as much as the living from the dead. -- Aristotle signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
Hi, On Wed, Aug 3, 2016 at 7:48 PM, Ronald S. Bultjewrote: > Hi, > > On Wed, Aug 3, 2016 at 1:57 PM, Michael Niedermayer < > mich...@niedermayer.cc> wrote: > >> Hi all >> >> Sun, Jul 31, 2016 at 10:01:00PM +0200, Michael Niedermayer wrote: >> > Hi all >> > >> > you have a great idea for a Outreachy task or a GSoC task ? >> > Or something you always wanted to do but never had the time and >> > it would fit in the time for GSoC/Outreachy ? >> > Or some feature you always wanted which would fit as a task? >> > Also keep in mind Outreachy is more flexible and not limited to >> > coding tasks ! >> > reply and dump it here below: >> >> ping ? >> >> also cc-ing ffmpeg-user >> >> or are all feature requests on trac fake and noone has anything they >> think should be implemented ? >> >> we need ideas for Outreachy, the page is EMPTY: >> https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 > > > I have some ideas. Most are TODOs / extensions to stuff I wrote that I > never ended up doing myself. Some might be hard. > > vp9: > - avx2 loopfilter functions. Qualification task: explain to me without any > guidance why it's an issue for AVX2 (or SSE2) that the loopfilter in vp9.c > works on 8px blocks, and explain how I solved that to work on 16px blocks > to use SSE2 instructions, and likewise explain how you would extend that to > work on 32px blocks. > - coefficient reading optimizations or arithmetic symbol reading > optimizations. I think this is too hard but it would be an amazing speed > optimization in vp9 decoding, since this is where pretty much all runtime > is spent after other optimizations. > - tile threading. This may actually be a nice qual task for the next block > since this is quite easy. > > frame/slice-mt: > - implement a mode that allows combining those. Qual task could be to > implement vp9 tile threading or something like that. Final deliverable > would implement this for at least vpN codec and one h.26x codec. > > I'll think about others. I'm willing to mentor the above maybe. > Another one, also for vp8/9: - alpha plane support for native decoders. (Thanks to James for remembering about this, I had forgotten.) Ronald ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
Hi, On Wed, Aug 3, 2016 at 7:48 PM, Ronald S. Bultjewrote: > Hi, > > On Wed, Aug 3, 2016 at 1:57 PM, Michael Niedermayer < > mich...@niedermayer.cc> wrote: > >> Hi all >> >> Sun, Jul 31, 2016 at 10:01:00PM +0200, Michael Niedermayer wrote: >> > Hi all >> > >> > you have a great idea for a Outreachy task or a GSoC task ? >> > Or something you always wanted to do but never had the time and >> > it would fit in the time for GSoC/Outreachy ? >> > Or some feature you always wanted which would fit as a task? >> > Also keep in mind Outreachy is more flexible and not limited to >> > coding tasks ! >> > reply and dump it here below: >> >> ping ? >> >> also cc-ing ffmpeg-user >> >> or are all feature requests on trac fake and noone has anything they >> think should be implemented ? >> >> we need ideas for Outreachy, the page is EMPTY: >> https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 > > > I have some ideas. Most are TODOs / extensions to stuff I wrote that I > never ended up doing myself. Some might be hard. > > vp9: > - avx2 loopfilter functions. Qualification task: explain to me without any > guidance why it's an issue for AVX2 (or SSE2) that the loopfilter in vp9.c > works on 8px blocks, and explain how I solved that to work on 16px blocks > to use SSE2 instructions, and likewise explain how you would extend that to > work on 32px blocks. > - coefficient reading optimizations or arithmetic symbol reading > optimizations. I think this is too hard but it would be an amazing speed > optimization in vp9 decoding, since this is where pretty much all runtime > is spent after other optimizations. > - tile threading. This may actually be a nice qual task for the next block > since this is quite easy. > > frame/slice-mt: > - implement a mode that allows combining those. Qual task could be to > implement vp9 tile threading or something like that. Final deliverable > would implement this for at least vpN codec and one h.26x codec. > > I'll think about others. I'm willing to mentor the above maybe. > Thinking more about frame/slice-mt combination, I'd also like someone to implement WPP threading (in addition to tile/frame) for HEVC, and again a mode to combine WPP/tile + frame. The term "slice-mt" also becomes questionable and might need renaming to something broader. But then again, I also feel that for outreachy, these tasks might be hard and "vp9 tile" or "hevc wpp" might be a full outreachy task on their own, and "*-mt combining" might just be too hard for a "new" student. Comments? I also don't want to mentor everything myself so I'd probably want someone else to mentor hevc bits so I can remain more narrowly focussed on vp9 for now. Ronald ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
Hi, On Wed, Aug 3, 2016 at 1:57 PM, Michael Niedermayerwrote: > Hi all > > Sun, Jul 31, 2016 at 10:01:00PM +0200, Michael Niedermayer wrote: > > Hi all > > > > you have a great idea for a Outreachy task or a GSoC task ? > > Or something you always wanted to do but never had the time and > > it would fit in the time for GSoC/Outreachy ? > > Or some feature you always wanted which would fit as a task? > > Also keep in mind Outreachy is more flexible and not limited to > > coding tasks ! > > reply and dump it here below: > > ping ? > > also cc-ing ffmpeg-user > > or are all feature requests on trac fake and noone has anything they > think should be implemented ? > > we need ideas for Outreachy, the page is EMPTY: > https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 I have some ideas. Most are TODOs / extensions to stuff I wrote that I never ended up doing myself. Some might be hard. vp9: - avx2 loopfilter functions. Qualification task: explain to me without any guidance why it's an issue for AVX2 (or SSE2) that the loopfilter in vp9.c works on 8px blocks, and explain how I solved that to work on 16px blocks to use SSE2 instructions, and likewise explain how you would extend that to work on 32px blocks. - coefficient reading optimizations or arithmetic symbol reading optimizations. I think this is too hard but it would be an amazing speed optimization in vp9 decoding, since this is where pretty much all runtime is spent after other optimizations. - tile threading. This may actually be a nice qual task for the next block since this is quite easy. frame/slice-mt: - implement a mode that allows combining those. Qual task could be to implement vp9 tile threading or something like that. Final deliverable would implement this for at least vpN codec and one h.26x codec. I'll think about others. I'm willing to mentor the above maybe. Ronald ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On Wed, Aug 03, 2016 at 07:46:26PM +, Timothy Gu wrote: > On Wed, Aug 3, 2016 at 12:36 PM Michael Niedermayer> wrote: > > > what about writing guides/howtos about how to build/replace FFmpeg > > on all kinds of hw > > > > That's the responsibility of the HW vendor. > > > > i mean everything these days uses FFmpeg below one or more layers > > and users should have the right to replace their products FFmpeg > > maybe with one that has more features enabled or a newer version > > but in practice for how many products that contain FFmpeg can > > the user actually do this easily? ... > > > > Practically none, an amount easily matched by the number of users who are > interested in doing that. I am interrested in modifying stuff, and i think some developers i know are too, so is probably the hacking and "power user" community around whatever specific device one considers A sizeable portion of the whole user base that is not but an important portion. If you provide a guide that allows people to replace the installed FFmpeg binary on some hw, that hw might gain support for formats providing better quality per bitrate or are more free, or ones that where disabled due whatever marketing or legal reasons Having guides like this can get users interrested in hacking and modifying stuff, does it help us, no probably not but to me getting more people interrested in any kind of hacking, programming, science or engeneering sounds like a win. Most users dont even know what is used to decode multimedia Maybe this suggestion doesnt fit FFmpeg Outreachy, i dont know, it was just a suggestion ... [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Dictatorship naturally arises out of democracy, and the most aggravated form of tyranny and slavery out of the most extreme liberty. -- Plato signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
Hi On 3 Aug 2016 6:58 p.m., "Michael Niedermayer"wrote: > > Hi all > > we need ideas for Outreachy, the page is EMPTY: > https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 > How about EBU-STL subtitle decoding? It's currently unsupported. It's a non text based subtitle format that is used in a broadcast environment. I'm not sure if that is too specific to be of interest. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On Wed, Aug 3, 2016 at 11:57 AM James Almerwrote: > On 7/31/2016 5:01 PM, Michael Niedermayer wrote: > > Hi all > > > > you have a great idea for a Outreachy task or a GSoC task ? > > Or something you always wanted to do but never had the time and > > it would fit in the time for GSoC/Outreachy ? > > Or some feature you always wanted which would fit as a task? > > Also keep in mind Outreachy is more flexible and not limited to > > coding tasks ! > > reply and dump it here below: > > Writing new examples or porting decoding_encoding.c and > demuxing_decoding.c to use codecpar and send/receive packet/frame. > +1 Maye also adding or extending doxy on public and private header, > sort of like what Timothy did the last couple days, but as Paul > said, coding related there's probably not a whole lot left that > can be easily done by students. > +1 too. Also fixing up some parts of FATE I don't have time to fix, and adapting Doxygen output style to the website. Web development sounds like a buzzword these days. Timothy ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On Wed, Aug 3, 2016 at 12:36 PM Michael Niedermayerwrote: > what about writing guides/howtos about how to build/replace FFmpeg > on all kinds of hw > That's the responsibility of the HW vendor. > i mean everything these days uses FFmpeg below one or more layers > and users should have the right to replace their products FFmpeg > maybe with one that has more features enabled or a newer version > but in practice for how many products that contain FFmpeg can > the user actually do this easily? ... > Practically none, an amount easily matched by the number of users who are interested in doing that. Timothy ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On Wed, Aug 03, 2016 at 03:55:08PM -0300, James Almer wrote: > On 7/31/2016 5:01 PM, Michael Niedermayer wrote: > > Hi all > > > > you have a great idea for a Outreachy task or a GSoC task ? > > Or something you always wanted to do but never had the time and > > it would fit in the time for GSoC/Outreachy ? > > Or some feature you always wanted which would fit as a task? > > Also keep in mind Outreachy is more flexible and not limited to > > coding tasks ! > > reply and dump it here below: > > Writing new examples or porting decoding_encoding.c and > demuxing_decoding.c to use codecpar and send/receive packet/frame. > Writing documentation with steps to migrate applications using > old APIs to new ones like the above, so we don't have to deal > with tons of projects sticking to deprecated APIs two years from > now and blocking or complicating their scheduled removal. > > Maye also adding or extending doxy on public and private header, > sort of like what Timothy did the last couple days, but as Paul > said, coding related there's probably not a whole lot left that > can be easily done by students. what about writing guides/howtos about how to build/replace FFmpeg on all kinds of hw i mean everything these days uses FFmpeg below one or more layers and users should have the right to replace their products FFmpeg maybe with one that has more features enabled or a newer version but in practice for how many products that contain FFmpeg can the user actually do this easily? ... [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you fake or manipulate statistics in a paper in physics you will never get a job again. If you fake or manipulate statistics in a paper in medicin you will get a job for life at the pharma industry. signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On 7/31/2016 5:01 PM, Michael Niedermayer wrote: > Hi all > > you have a great idea for a Outreachy task or a GSoC task ? > Or something you always wanted to do but never had the time and > it would fit in the time for GSoC/Outreachy ? > Or some feature you always wanted which would fit as a task? > Also keep in mind Outreachy is more flexible and not limited to > coding tasks ! > reply and dump it here below: Writing new examples or porting decoding_encoding.c and demuxing_decoding.c to use codecpar and send/receive packet/frame. Writing documentation with steps to migrate applications using old APIs to new ones like the above, so we don't have to deal with tons of projects sticking to deprecated APIs two years from now and blocking or complicating their scheduled removal. Maye also adding or extending doxy on public and private header, sort of like what Timothy did the last couple days, but as Paul said, coding related there's probably not a whole lot left that can be easily done by students. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
On 8/3/16, Michael Niedermayerwrote: > Hi all > > Sun, Jul 31, 2016 at 10:01:00PM +0200, Michael Niedermayer wrote: >> Hi all >> >> you have a great idea for a Outreachy task or a GSoC task ? >> Or something you always wanted to do but never had the time and >> it would fit in the time for GSoC/Outreachy ? >> Or some feature you always wanted which would fit as a task? >> Also keep in mind Outreachy is more flexible and not limited to >> coding tasks ! >> reply and dump it here below: > > ping ? > > also cc-ing ffmpeg-user > > or are all feature requests on trac fake and noone has anything they > think should be implemented ? > > we need ideas for Outreachy, the page is EMPTY: > https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 Hard stuff only left. > > > [...] > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > If you think the mosad wants you dead since a long time then you are either > wrong or dead since a long time. > ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
Hi all Sun, Jul 31, 2016 at 10:01:00PM +0200, Michael Niedermayer wrote: > Hi all > > you have a great idea for a Outreachy task or a GSoC task ? > Or something you always wanted to do but never had the time and > it would fit in the time for GSoC/Outreachy ? > Or some feature you always wanted which would fit as a task? > Also keep in mind Outreachy is more flexible and not limited to > coding tasks ! > reply and dump it here below: ping ? also cc-ing ffmpeg-user or are all feature requests on trac fake and noone has anything they think should be implemented ? we need ideas for Outreachy, the page is EMPTY: https://trac.ffmpeg.org/wiki/SponsoringPrograms/Outreachy/2016-12 [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you think the mosad wants you dead since a long time then you are either wrong or dead since a long time. signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] next Outreachy & GSoC ideas braindump [RFC]
Hi all you have a great idea for a Outreachy task or a GSoC task ? Or something you always wanted to do but never had the time and it would fit in the time for GSoC/Outreachy ? Or some feature you always wanted which would fit as a task? Also keep in mind Outreachy is more flexible and not limited to coding tasks ! reply and dump it here below: thanks -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Many things microsoft did are stupid, but not doing something just because microsoft did it is even more stupid. If everything ms did were stupid they would be bankrupt already. signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel