Re: [FFmpeg-devel] Areas needing work
On Tue, Apr 07, 2015 at 10:22:17AM +1000, Peter Ross wrote: > On Mon, Apr 06, 2015 at 07:24:35PM +0100, Derek Buitenhuis wrote: > > On 4/6/2015 4:43 AM, Michael Niedermayer wrote: > [..] > > > * Conferences / exhibitions, public stuff > > > Theres a conference, linuxtag, fosdem, whatever, wherever in your local > > > area > > > and you think FFmpeg should be represented there ? > > > > FWIW, I attend FOSDEM and VDD representing both FFmpeg and Libav as well as > > $dayjob, > > (just to make sure everyone on every side hates me ;)). I also talked at > > IBC at EBU's > > booth about open source media, and will be in Berlin for SMPTE's > > circlejerk^Wforum > > in May, as talking about open source media (FFmpeg especially). I'm not the > > only > > one, and I think this is pretty well covered in recent years. > > I am thinking of submitting a FFmpeg themed paper to LCA'2016 (Linux > Conference Australia). > If anyone wants to contribute please yell out. > > Topic idea to be decided. Maybe: > - survey of compression algorithm reuse amongst all our codecs. Might be a > lot of work to do, but would be interesting. > - or describe less known capabilities of FFmpeg. > - ... > > The LCA call for proposals opens in July-August. > My spare time is limited, so to have something ready I need to make a start > soon. Anyone? Ping me. "The tentative close date for Presentations, Tutorials and Prototypes is 6th July. If you are proposing a Miniconf, you must submit your proposal by 6th July." http://linux.conf.au/cfp -- Peter (A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B) signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Wed, Apr 08, 2015 at 10:33:56PM +0530, AB wrote: > > > On Monday 06 April 2015 09:13 AM, Michael Niedermayer wrote: > > Hi all > > > > There are various areas in the project that are not maintained as well as > > they > > should be, heres a certainly not comlpete list, dont hesitate to reply and > > add to it. > > If someone wants to pick something up and contribute that is VERY welcome > > > > * Post merge review&cleanup, changes merged from libav would benefit from > > people reviewing and MUCH MUCH more importantly also people actually > > caring > > about and taking responsibility not just dumping comments with the idea > > "someone" will fix it. > > Ideally each area would have a maintainer who takes care of it and > > keeps it in good nick. > > > > > > * fate clients > > we lack a armcc test, a real android test > > someone should take over haiku and sunos/solaris fate clients, my haiku > > VM just > > keeps crashing > > > > I have some spare capacity, I'll try setting up a Haiku VM this weekend. great > > Are the sunos fate clients in a VM? Is it possible for you to export the VMs > for me to download? the sunos/solaris is a VM but i dont think the VM i have is a good starting point, i was unable to update it last i tried, it really needs a reinstall > > If someone can point me to what is required for an Android FATE client and > how to set one up I can do that as well. i dont know but some android device i think is needed and probably a cross build environment > > > > > > * our fate server lacks the ability to display a user specified release > > this makes the output look quite unwieldy > > Timothy was working on a rewrite > > > > > > * Paid maintainers > > a big problem is that we have areas in the codebase that have no > > maintainr or > > rather noone with sufficient time+will+abilty. > > It would help tremendiusly if maintainers could work full > > time on maintaining code instead of just a few hours in their free > > time > > > > > > * ffserver lacks a regression test > > code that is not tested will accumulate bugs. period > > there are people who use ffserver, they clearly like the lack of > > regression > > tests it seems as noone finds the need to look into changing that. > > > > > > * more people should help on https://trac.ffmpeg.org, like check that > > tickets > > contain all information needed to reproduce and ask the reporter to > > provide > > missing information, check if things are regressions, if they can be > > reproduced, > > bisect regressions or ask the reporter to bisect and help him if needed > > close tickets where there is not enough information to reproduce and the > > reporter doesnt react for months. ATM carl does all that and more but > > iam sure he wouldnt mind if more people would help him > > > > > > * Stipends and Sponsorship programs > > We do not have enough funds for basic things, for example OPW/Outreachy is > > twice a year and to participate we have to pay at least one stipend > > (about 6.5k USD). We participated in december 2014 and it allowed us to > > convert > > all remaining libmpcodecs filters to the native system. resulted in > > multiple > > new video filters and several block ciphers which are faster then all > > other > > tested implementations. For may 2015 we only way after the last minute > > managed > > to secure some funding so we are short of applicants now as for a long > > time ffmpeg was not listed as a participating org. > > > > > > * Decentralize > > Too many things are done and admined by me, iam doing security updates to > > the > > servers, doing the git merges, maintaining all releases, maintaining half > > the > > fate clients, submitting data to coverity and doing all the crap that > > noone > > else wants to do. > > Does the community care so little that they want me to be a single point > > of > > failure? > > We need people to take some of this over at least on the basis of a backup > > in case iam unavailable for whatever reason, and i think it should ideally > > be people who do not yet have their daily work shedule overflowing with > > ffmpeg > > work but better new volunteers. > > Besides the ones listed further up, which ones would you like me to host? anything that could run FFmpeg and is missing from fate.ffmpeg.org would be a welcome addition Thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The worst form of inequality is to try to make unequal things equal. -- Aristotle signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Wed, Apr 8, 2015 at 10:04 AM AB wrote: > > * fate clients > > we lack a armcc test, a real android test > > someone should take over haiku and sunos/solaris fate clients, my > haiku VM just > > keeps crashing > > > > I have some spare capacity, I'll try setting up a Haiku VM this weekend. > Cool! I can offer some help if needed as Haiku installation can get hairy… [...] Timothy ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Monday 06 April 2015 09:13 AM, Michael Niedermayer wrote: > Hi all > > There are various areas in the project that are not maintained as well as they > should be, heres a certainly not comlpete list, dont hesitate to reply and > add to it. > If someone wants to pick something up and contribute that is VERY welcome > > * Post merge review&cleanup, changes merged from libav would benefit from > people reviewing and MUCH MUCH more importantly also people actually caring > about and taking responsibility not just dumping comments with the idea > "someone" will fix it. > Ideally each area would have a maintainer who takes care of it and > keeps it in good nick. > > > * fate clients > we lack a armcc test, a real android test > someone should take over haiku and sunos/solaris fate clients, my haiku VM > just > keeps crashing > I have some spare capacity, I'll try setting up a Haiku VM this weekend. Are the sunos fate clients in a VM? Is it possible for you to export the VMs for me to download? If someone can point me to what is required for an Android FATE client and how to set one up I can do that as well. > > * our fate server lacks the ability to display a user specified release > this makes the output look quite unwieldy > Timothy was working on a rewrite > > > * Paid maintainers > a big problem is that we have areas in the codebase that have no maintainr > or > rather noone with sufficient time+will+abilty. > It would help tremendiusly if maintainers could work full > time on maintaining code instead of just a few hours in their free > time > > > * ffserver lacks a regression test > code that is not tested will accumulate bugs. period > there are people who use ffserver, they clearly like the lack of regression > tests it seems as noone finds the need to look into changing that. > > > * more people should help on https://trac.ffmpeg.org, like check that tickets > contain all information needed to reproduce and ask the reporter to provide > missing information, check if things are regressions, if they can be > reproduced, > bisect regressions or ask the reporter to bisect and help him if needed > close tickets where there is not enough information to reproduce and the > reporter doesnt react for months. ATM carl does all that and more but > iam sure he wouldnt mind if more people would help him > > > * Stipends and Sponsorship programs > We do not have enough funds for basic things, for example OPW/Outreachy is > twice a year and to participate we have to pay at least one stipend > (about 6.5k USD). We participated in december 2014 and it allowed us to > convert > all remaining libmpcodecs filters to the native system. resulted in multiple > new video filters and several block ciphers which are faster then all other > tested implementations. For may 2015 we only way after the last minute > managed > to secure some funding so we are short of applicants now as for a long > time ffmpeg was not listed as a participating org. > > > * Decentralize > Too many things are done and admined by me, iam doing security updates to > the > servers, doing the git merges, maintaining all releases, maintaining half > the > fate clients, submitting data to coverity and doing all the crap that noone > else wants to do. > Does the community care so little that they want me to be a single point of > failure? > We need people to take some of this over at least on the basis of a backup > in case iam unavailable for whatever reason, and i think it should ideally > be people who do not yet have their daily work shedule overflowing with > ffmpeg > work but better new volunteers. Besides the ones listed further up, which ones would you like me to host? -- Ashish > > > * Conferences / exhibitions, public stuff > Theres a conference, linuxtag, fosdem, whatever, wherever in your local area > and you think FFmpeg should be represented there ? > Simple, go there and represent FFmpeg! unless you are too shy ... of course. > FFmpeg is a large community of users and developers, the developers who > managed the last stands/booths arent special, every FFmpeg developer and > even > Users who know ffmpeg a bit better who like can do this too. > Also please add all conferences / exhibitions to > https://trac.ffmpeg.org/wiki/Conferences > > > You dont have time to help with any above or you prefer pretending that > you dont, well, maybe you know someone else who could help with something, > dont hesitate to ask them / forward this! > > please make sure to keep ffmpeg-devel in CC if you reply from ffmpeg-user > > > > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel > ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/f
Re: [FFmpeg-devel] Areas needing work
On Tue, Apr 07, 2015 at 09:08:10PM +0530, Mayank Agarwal wrote: > Hi > > I am interested in contributing to any of the projects.Please enroll > me and tell me the procedure how can > i contribute to ffmpeg You can work on anything you like to work on, anything thats fun to you. Add support for a not yet supported format, codec, feature, fix a bug, help improve the wiki, help on the bug tracker as previously explained, ... also see https://ffmpeg.org/developer.html [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Complexity theory is the science of finding the exact solution to an approximation. Benchmarking OTOH is finding an approximation of the exact signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
Hi I am interested in contributing to any of the projects.Please enroll me and tell me the procedure how can i contribute to ffmpeg Regards Mayank On Mon, Apr 6, 2015 at 10:18 PM, Timothy Gu wrote: > On Sun, Apr 5, 2015 at 8:43 PM Michael Niedermayer wrote: > >> Hi all >> >> There are various areas in the project that are not maintained as well as >> they >> should be, heres a certainly not comlpete list, dont hesitate to reply and >> add to it. >> If someone wants to pick something up and contribute that is VERY welcome >> >> * Post merge review&cleanup, changes merged from libav would benefit from >> people reviewing and MUCH MUCH more importantly also people actually >> caring >> about and taking responsibility not just dumping comments with the idea >> "someone" will fix it. >> Ideally each area would have a maintainer who takes care of it and >> keeps it in good nick. >> >> >> * fate clients >> we lack a armcc test, a real android test >> someone should take over haiku and sunos/solaris fate clients, my haiku >> VM just >> keeps crashing >> > > I can take care of the Haiku test if I have (access to) a better/faster > computer… > > >> * our fate server lacks the ability to display a user specified release >> this makes the output look quite unwieldy >> Timothy was working on a rewrite >> > > I haven't touched that thing in a few months but it's in a pretty good > shape. With a few minor updates it should be good to go at least on > fate-beta.ffmpeg.org or something like that. There are still a few minor > things I want to fix (like minirep/minilog, warning diff (is it really > useful now since most boxes are using make -jx and testing order changes > every time?), and some minor styling issue). > > [...] > >> * Decentralize >> Too many things are done and admined by me, iam doing security updates >> to the >> servers, doing the git merges, maintaining all releases, maintaining >> half the >> fate clients, submitting data to coverity and doing all the crap that >> noone >> else wants to do. >> Does the community care so little that they want me to be a single point >> of >> failure? >> We need people to take some of this over at least on the basis of a >> backup >> in case iam unavailable for whatever reason, and i think it should >> ideally >> be people who do not yet have their daily work shedule overflowing with >> ffmpeg >> work but better new volunteers. >> > > - Project servers: MAINTAINERS list four people [1], one of which I have > never > ever seen on this list, and it is not clear to me how the servers are > administered (who pays for it? who has access to it? who has access to the > hosting company's setting page?) [2] > - Git merges: when I first came to this project merges are still called > "Merge > from remote tracking branch 'qatar/master'." WTF is qatar? Now of course > that is not a problem any more, but the merges remain undocumented on any > official documentation I could find (maybe I didn't look hard enough?). If > the behavior itself is not known publicly how can anyone help? > - Coverity: one can easily hook it up to a FATE box. > > [1]: https://github.com/FFmpeg/FFmpeg/blob/master/MAINTAINERS#L48 > [2]: Yes I guess I can ask on IRC or whatever but I am lazy, and I know that > there are people lazier than me. If it is so hard to find out how to > *volunteer* I would not imagine many people trying to volunteer. > > But anyway, I can volunteer to take over coverage.ffmpeg.org. But again who > should I find to discuss this thing in detail? Michael? Clément? I don't > know. > > Also a news article on a call for maintainers would be beneficial (?). > > Timothy > ___ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On date Tuesday 2015-04-07 14:40:50 +0100, Derek Buitenhuis encoded: > On 4/6/2015 11:23 PM, compn wrote: > > i think we tried this a few years ago and found that we do still have > > ffserver users, they are just quiet until we threaten to rm it. if/when > > it breaks, someone will either be there to fix it or it will rot. > > That's stupid. Either someone steps up to fix it (read: actually cares), > or it remove it. Having a broken piece of crap that nobody cares about > in the repo benefits nobody. I did some consulting about the use of ffserver in the past, with variying degrees of success (hint: RTP streaming is usually tricky and highly depends on network and bandwith constraints). I agree that ffserver is painfully underkill, but still better than nothing. Also we have an official maintainer and some substantial work has been done on it recently. Use cases: real time streaming of interactive content through HTTP or RTSP/RTP. Probably these days there are better solutions but I think ffserver still cover an use case which cannot be fullfilled by the other FFmpeg tools. At the present days there are probably other valid alternatives (e.g. Flash/RTMP, webRTC, HTML5/Media Source Extensions, JavaScript native decoding + websockets, HLS, DASH) which cover similar areas, but are not completely equivalent. For example HLS is known to introduce some significative delay. -- FFmpeg = Fundamentalist & Fiendish Multimedia Pitiful Elfic Game ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On 4/6/2015 11:23 PM, compn wrote: > i think we tried this a few years ago and found that we do still have > ffserver users, they are just quiet until we threaten to rm it. if/when > it breaks, someone will either be there to fix it or it will rot. That's stupid. Either someone steps up to fix it (read: actually cares), or it remove it. Having a broken piece of crap that nobody cares about in the repo benefits nobody. - Derek ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/04/15 21:00, Michael Niedermayer wrote: [..] > we need to move things to a new server (we already have one but > against expectations moving things over is happening at a snails pace) > ATM fate-suite and samples are on the new server, rest is still on the > old. The reason for the need to move is the aging platform and > potential lack of future security support for it ... > maybe beastd and lou can comment on this as beastd was the one who did > most of the work that was done sofar and lou seemed to be willing to > help. > question is do we need another volunteer to make this move happen? > [...] As indicated elsewhere I am happy to assist with the bits I know about and have fiddled with in the past ;) - -- Tim. Key Fingerprint 38CF DB09 3ED0 F607 8B67 6CED 0C0B FC44 8B0B FC83 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVI8pfAAoJEAwL/ESLC/yD/BkH/3wCkyNG53mhW5YUcmlbFhhx 3MCdjKp/nzsvzMh43/UJEapTqdmQquAAQL2Sqv/pP96Ol8RYq1zPikjntdTUslP0 XFlD6eRqfIpuhZzn3IpmhxPYtxAzgydKppXIiL60borVGMsLfHBGfcphSKSP9Yx9 E+gaB6byoLS3nIWPFzWLWr6PE84OmnM4UDPZOQtZC249eaW6PkoZ4LcNhpOmxULI X0cwt2aQvptgwB/wFCofikC6n3dWKE0fFpixfPvBGd0jNyNgADHrHX8pXaa7kCAJ jBi4QKDI3JhuD6u1xWQO97LoiL9NlcaoBSzcmwAkGm4yeo8KAw0hnawTGaZ0DgY= =VvqM -END PGP SIGNATURE- ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Mon, Apr 06, 2015 at 07:24:35PM +0100, Derek Buitenhuis wrote: > On 4/6/2015 4:43 AM, Michael Niedermayer wrote: [..] > > * Conferences / exhibitions, public stuff > > Theres a conference, linuxtag, fosdem, whatever, wherever in your local > > area > > and you think FFmpeg should be represented there ? > > FWIW, I attend FOSDEM and VDD representing both FFmpeg and Libav as well as > $dayjob, > (just to make sure everyone on every side hates me ;)). I also talked at IBC > at EBU's > booth about open source media, and will be in Berlin for SMPTE's > circlejerk^Wforum > in May, as talking about open source media (FFmpeg especially). I'm not the > only > one, and I think this is pretty well covered in recent years. I am thinking of submitting a FFmpeg themed paper to LCA'2016 (Linux Conference Australia). If anyone wants to contribute please yell out. Topic idea to be decided. Maybe: - survey of compression algorithm reuse amongst all our codecs. Might be a lot of work to do, but would be interesting. - or describe less known capabilities of FFmpeg. - ... The LCA call for proposals opens in July-August. My spare time is limited, so to have something ready I need to make a start soon. -- Peter (A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B) signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Mon, Apr 06, 2015 at 10:17:22PM +, Timothy Gu wrote: > On Mon, Apr 6, 2015 at 10:42 AM Michael Niedermayer > wrote: > > > On Mon, Apr 06, 2015 at 04:48:24PM +, Timothy Gu wrote: > > > On Sun, Apr 5, 2015 at 8:43 PM Michael Niedermayer > > wrote: > > [...] > > > > > > > > > > * our fate server lacks the ability to display a user specified release > > > > this makes the output look quite unwieldy > > > > Timothy was working on a rewrite > > > > > > > > > > I haven't touched that thing in a few months but it's in a pretty good > > > shape. With a few minor updates it should be good to go at least on > > > fate-beta.ffmpeg.org or something like that. There are still a few minor > > > things I want to fix (like minirep/minilog, warning diff (is it really > > > useful now since most boxes are using make -jx and testing order changes > > > every time?), and some minor styling issue). > > > > ok, > > do you have your own server where i should make > > fate-beta.ffmpeg.org point to or its something that needs to be setup > > on the fate / or some other server ? > > > > I do have a server I can use for this purpose but i wonder how I am going > to get the FATE data submitted by the boxes if I'm using mine… (which is > another headache when writing my server) could the existing server be made to forward data to a 2nd server ? then all that gets submited to it would automatically get sent to yours or anyone elses who wants to run one we also might in case of a failure of the server then just change fate.ffmpeg.org to point to yours so this design could be considered to add some redundancy > > Right now I can get the data manually by wgetting files (like > http://fate.ffmpeg.org/aarch64-linux-qemu-ubuntu-gcc-4.8/20150406220127/summary), > but that's a pain in the ass. (Plus those files should not be public > anyway.) > > [...] > > > > and it is not clear to me how the servers are > > > administered (who pays for it? who has access to it? who has access to > > the > > > > main servers are provided by arpi > > > > You mean [git.]ffmpeg.org? ffmpeg.org, samples.ffmpeg.org, trac.ffmpeg.org also note to forget source.ffmpeg.org is provided by videolan > > I know this has been discussed before, but moving to a 3rd-party hosting > service like GitHub Pages might make this significantly easier. Who knows > what repos are still hosted on git.ffmpeg.org? the webpage repos, fateserver, some other random stuff probably too > > fate server by baptiste > > > Baptiste doesn't seem to be active these days. Should I contact him > personally? yes, that would probably be best, i suspect he would miss a mail here [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB While the State exists there can be no freedom; when there is freedom there will be no State. -- Vladimir Lenin signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Mon, 6 Apr 2015 05:43:29 +0200 Michael Niedermayer wrote: > * Decentralize > Too many things are done and admined by me, iam doing security > updates to the servers, doing the git merges, maintaining all > releases, maintaining half the fate clients, submitting data to > coverity and doing all the crap that noone else wants to do. > Does the community care so little that they want me to be a single > point of failure? its supply and demand. the community has a supply of you maintaining the whole thing and many other devs maintaining other pieces. supply is full. it might be wise for you to take a week off every month. to allow a demand for some one to step up. or maybe i'm crazy. or maybe just take breaks from doing particular jobs like coverity or maintaining fate clients. did you already setup the fate clients so they can be logged in by another devel to maintain? by maintain i'm guessing not much is needed, maybe upgrading libs or rebooting or something? easy stuff i'm assuming. > > * Conferences / exhibitions, public stuff > Theres a conference, linuxtag, fosdem, whatever, wherever in your > local area and you think FFmpeg should be represented there ? > Simple, go there and represent FFmpeg! unless you are too shy ... > of course. FFmpeg is a large community of users and developers, the > developers who managed the last stands/booths arent special, every > FFmpeg developer and even Users who know ffmpeg a bit better who like > can do this too. Also please add all conferences / exhibitions to > https://trac.ffmpeg.org/wiki/Conferences we need the conferences to attract developers? doh! now you tell me. some of us may need encouragement or some kind of description of what is needed to represent a booth. whats needed, how many hours, how much $$$ for a booth at a convention, what should we bring, etc. maybe people that have been to conferences can list what goes on and what you do. maybe report how fun it is or how boring! :) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Mon, 06 Apr 2015 19:24:35 +0100 Derek Buitenhuis wrote: > On 4/6/2015 4:43 AM, Michael Niedermayer wrote: > > * ffserver lacks a regression test > > code that is not tested will accumulate bugs. period > > there are people who use ffserver, they clearly like the lack of > > regression tests it seems as noone finds the need to look into > > changing that. > > Drop ffserver. It is crap, and I have been saying this for years. It > has no legitimate use cases as far as I am concerned. > i think we tried this a few years ago and found that we do still have ffserver users, they are just quiet until we threaten to rm it. if/when it breaks, someone will either be there to fix it or it will rot. removing it really helps no one, unless your larger goal is to seperate the project into library maint and a seperate project for tools like ffmpeg/ffserver . i'm not making the argument either way, i'm just trying to help. :) -compn ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Mon, Apr 6, 2015 at 10:42 AM Michael Niedermayer wrote: > On Mon, Apr 06, 2015 at 04:48:24PM +, Timothy Gu wrote: > > On Sun, Apr 5, 2015 at 8:43 PM Michael Niedermayer > wrote: > [...] > > > > > > > * our fate server lacks the ability to display a user specified release > > > this makes the output look quite unwieldy > > > Timothy was working on a rewrite > > > > > > > I haven't touched that thing in a few months but it's in a pretty good > > shape. With a few minor updates it should be good to go at least on > > fate-beta.ffmpeg.org or something like that. There are still a few minor > > things I want to fix (like minirep/minilog, warning diff (is it really > > useful now since most boxes are using make -jx and testing order changes > > every time?), and some minor styling issue). > > ok, > do you have your own server where i should make > fate-beta.ffmpeg.org point to or its something that needs to be setup > on the fate / or some other server ? > I do have a server I can use for this purpose but i wonder how I am going to get the FATE data submitted by the boxes if I'm using mine… (which is another headache when writing my server) Right now I can get the data manually by wgetting files (like http://fate.ffmpeg.org/aarch64-linux-qemu-ubuntu-gcc-4.8/20150406220127/summary), but that's a pain in the ass. (Plus those files should not be public anyway.) [...] > > and it is not clear to me how the servers are > > administered (who pays for it? who has access to it? who has access to > the > > main servers are provided by arpi > You mean [git.]ffmpeg.org? I know this has been discussed before, but moving to a 3rd-party hosting service like GitHub Pages might make this significantly easier. Who knows what repos are still hosted on git.ffmpeg.org? fate server by baptiste > Baptiste doesn't seem to be active these days. Should I contact him personally? [...] > > hosting company's setting page?) [2] > > my knowledge of the hosting details is limited > OK > > - Git merges: when I first came to this project merges are still called > > "Merge > > from remote tracking branch 'qatar/master'." WTF is qatar? Now of > course > > that is not a problem any more, but the merges remain undocumented on > any > > official documentation I could find (maybe I didn't look hard > enough?). If > > the behavior itself is not known publicly how can anyone help? > > They are probably undocumented on the FFmpeg side but iam not sure > what to document beyond what is in the git manual page > Adding a dedicated wiki page on Libav? > - Coverity: one can easily hook it up to a FATE box. > > maybe, but there are some special considerations > * as many as possible features, external libs, ... have to be enabled > as coverity only tests what is actually build > [...] > so a simple cronjob seems better suited /easier than fate > Well that. I just mentioned FATE since compiling is a part of FATE and one can just use that to submit to Coverity. but if you want to take coverity build/uploads over i can provide > you with the details needed to upload and what is currently enabled > (i dont want to loose testing for (m)any components) > > > But anyway, I can volunteer to take over coverage.ffmpeg.org. But again > who > > should I find to discuss this thing in detail? Michael? Clément? I don't > > know. > > coverage is 100% Cléments area, i dont know if he wants/needs any > volunteers for it > OK. See I didn't know that. [...] Timothy ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Areas needing work
On Mon, Apr 06, 2015 at 07:24:35PM +0100, Derek Buitenhuis wrote: > On 4/6/2015 4:43 AM, Michael Niedermayer wrote: > > * Post merge review&cleanup, changes merged from libav would benefit from > > people reviewing and MUCH MUCH more importantly also people actually > > caring > > about and taking responsibility not just dumping comments with the idea > > "someone" will fix it. > > Ideally each area would have a maintainer who takes care of it and > > keeps it in good nick. > > How would this actually work? Sit around and wait for merge commits and look > at them? yes in an ideal world each area would have a maintainer who would only have to review changes to his area. > > I sometimes do, but most of the commits that are merged are pretty boring > stuff, and > I tend not to read them. > > > * fate clients > > we lack a armcc test, a real android test > > someone should take over haiku and sunos/solaris fate clients, my haiku > > VM just > > keeps crashing > > Is there a wiki somewhere of stuff that needs to be tested? I shut down all > my FATE > instances 2 weeks ago for maintenance, but will be bringing them + more back > up. ive aded a link to a trac querry to https://trac.ffmpeg.org/wiki/FATE that way any ticket with keyword fateclient will be nicely vissible in the list until its closed, this should allow very easily keeping track of needed fate clients > > > * our fate server lacks the ability to display a user specified release > > this makes the output look quite unwieldy > > Timothy was working on a rewrite > > [...] > > > * Paid maintainers > > a big problem is that we have areas in the codebase that have no > > maintainr or > > rather noone with sufficient time+will+abilty. > > It would help tremendiusly if maintainers could work full > > time on maintaining code instead of just a few hours in their free > > time > > Where exactly would the money come from? Most, if not all of us have day jobs, > and/or are students. it would require a company or NGO to fund it of course, many companies use FFmpeg and would directly benefit from improvments in FFmpeg, be that bug fixes, features or anything else. Thus there is an advantage for a company to fund a full time maintainer. Sounds crazy? well, strictly speaking we do already have paid maintainers in some areas, its just not many but iam pretty sure some people in the MAINTAINERs file keep the code in good shape officially as part of their day job, not fulltime though. [...] > > > * Decentralize > > Too many things are done and admined by me, iam doing security updates to > > the > > servers, doing the git merges, maintaining all releases, maintaining half > > the > > fate clients, submitting data to coverity and doing all the crap that > > noone > > else wants to do. > > It's not really documented all the stuff which needs to be done, such as > server updates, > or who handles them and pay, etc. Basically what Timothy said. > > > Does the community care so little that they want me to be a single point > > of > > failure? > > Nobody wants that. I don't recall any previous requests for help with the > overhead work > such as server admin though. as we already are speaking of this we need to move things to a new server (we already have one but against expectations moving things over is happening at a snails pace) ATM fate-suite and samples are on the new server, rest is still on the old. The reason for the need to move is the aging platform and potential lack of future security support for it ... maybe beastd and lou can comment on this as beastd was the one who did most of the work that was done sofar and lou seemed to be willing to help. question is do we need another volunteer to make this move happen? > > > We need people to take some of this over at least on the basis of a backup > > in case iam unavailable for whatever reason, and i think it should ideally > > be people who do not yet have their daily work shedule overflowing with > > ffmpeg > > work but better new volunteers. > > I don't mind pitching in a small amount, and I can do a bit during work hours > perhaps > (whithin sanity/reason), but I also have a busy life with travel and > significant > other, etc. > > The main problem is it is not clear where or how to go about it, or what can > be volunteered. > > > * Conferences / exhibitions, public stuff > > Theres a conference, linuxtag, fosdem, whatever, wherever in your local > > area > > and you think FFmpeg should be represented there ? > > FWIW, I attend FOSDEM and VDD representing both FFmpeg and Libav as well as > $dayjob, > (just to make sure everyone on every side hates me ;)). I also talked at IBC > at EBU's > booth about open source media, and will be in Berlin for SMPTE's > circlejerk^Wforum > in May, as talking about open source media (FFmpeg especially). I'm not the > only > one, and I think this is pretty well covered in re
Re: [FFmpeg-devel] Areas needing work
On 4/6/2015 4:43 AM, Michael Niedermayer wrote: > * Post merge review&cleanup, changes merged from libav would benefit from > people reviewing and MUCH MUCH more importantly also people actually caring > about and taking responsibility not just dumping comments with the idea > "someone" will fix it. > Ideally each area would have a maintainer who takes care of it and > keeps it in good nick. How would this actually work? Sit around and wait for merge commits and look at them? I sometimes do, but most of the commits that are merged are pretty boring stuff, and I tend not to read them. > * fate clients > we lack a armcc test, a real android test > someone should take over haiku and sunos/solaris fate clients, my haiku VM > just > keeps crashing Is there a wiki somewhere of stuff that needs to be tested? I shut down all my FATE instances 2 weeks ago for maintenance, but will be bringing them + more back up. > * our fate server lacks the ability to display a user specified release > this makes the output look quite unwieldy > Timothy was working on a rewrite [...] > * Paid maintainers > a big problem is that we have areas in the codebase that have no maintainr > or > rather noone with sufficient time+will+abilty. > It would help tremendiusly if maintainers could work full > time on maintaining code instead of just a few hours in their free > time Where exactly would the money come from? Most, if not all of us have day jobs, and/or are students. > * ffserver lacks a regression test > code that is not tested will accumulate bugs. period > there are people who use ffserver, they clearly like the lack of regression > tests it seems as noone finds the need to look into changing that. Drop ffserver. It is crap, and I have been saying this for years. It has no legitimate use cases as far as I am concerned. > * more people should help on https://trac.ffmpeg.org, like check that tickets > contain all information needed to reproduce and ask the reporter to provide > missing information, check if things are regressions, if they can be > reproduced, > bisect regressions or ask the reporter to bisect and help him if needed > close tickets where there is not enough information to reproduce and the > reporter doesnt react for months. ATM carl does all that and more but > iam sure he wouldnt mind if more people would help him I can only speak for myself and a couple others, but we stay well away from the bug tracker because we cannot stand a certain prolific person there. > * Stipends and Sponsorship programs > We do not have enough funds for basic things, for example OPW/Outreachy is > twice a year and to participate we have to pay at least one stipend > (about 6.5k USD). We participated in december 2014 and it allowed us to > convert > all remaining libmpcodecs filters to the native system. resulted in multiple > new video filters and several block ciphers which are faster then all other > tested implementations. For may 2015 we only way after the last minute > managed > to secure some funding so we are short of applicants now as for a long > time ffmpeg was not listed as a participating org. And we have a bunch of massive failures too. I'm not 100% certain it's even worth it. Not that we have been accepted in GSoC it seems like a better route, financially, for attracting new people. Or, you know, people could contribute without cash incentives - but I guess that concept is lost nowadays? :/ > * Decentralize > Too many things are done and admined by me, iam doing security updates to > the > servers, doing the git merges, maintaining all releases, maintaining half > the > fate clients, submitting data to coverity and doing all the crap that noone > else wants to do. It's not really documented all the stuff which needs to be done, such as server updates, or who handles them and pay, etc. Basically what Timothy said. > Does the community care so little that they want me to be a single point of > failure? Nobody wants that. I don't recall any previous requests for help with the overhead work such as server admin though. > We need people to take some of this over at least on the basis of a backup > in case iam unavailable for whatever reason, and i think it should ideally > be people who do not yet have their daily work shedule overflowing with > ffmpeg > work but better new volunteers. I don't mind pitching in a small amount, and I can do a bit during work hours perhaps (whithin sanity/reason), but I also have a busy life with travel and significant other, etc. The main problem is it is not clear where or how to go about it, or what can be volunteered. > * Conferences / exhibitions, public stuff > Theres a conference, linuxtag, fosdem, whatever, wherever in your local area > and you think FFmpeg should be represented there ? FWIW, I attend FOSDEM and VDD representing both FFmpeg and Libav as well as
Re: [FFmpeg-devel] Areas needing work
On Mon, Apr 06, 2015 at 04:48:24PM +, Timothy Gu wrote: > On Sun, Apr 5, 2015 at 8:43 PM Michael Niedermayer wrote: [...] > > > > * our fate server lacks the ability to display a user specified release > > this makes the output look quite unwieldy > > Timothy was working on a rewrite > > > > I haven't touched that thing in a few months but it's in a pretty good > shape. With a few minor updates it should be good to go at least on > fate-beta.ffmpeg.org or something like that. There are still a few minor > things I want to fix (like minirep/minilog, warning diff (is it really > useful now since most boxes are using make -jx and testing order changes > every time?), and some minor styling issue). ok, do you have your own server where i should make fate-beta.ffmpeg.org point to or its something that needs to be setup on the fate / or some other server ? > > [...] > > > * Decentralize > > Too many things are done and admined by me, iam doing security updates > > to the > > servers, doing the git merges, maintaining all releases, maintaining > > half the > > fate clients, submitting data to coverity and doing all the crap that > > noone > > else wants to do. > > Does the community care so little that they want me to be a single point > > of > > failure? > > We need people to take some of this over at least on the basis of a > > backup > > in case iam unavailable for whatever reason, and i think it should > > ideally > > be people who do not yet have their daily work shedule overflowing with > > ffmpeg > > work but better new volunteers. > > > > - Project servers: MAINTAINERS list four people [1], one of which I have > never > ever seen on this list, There are mails from arpi on the list but he possibly didnt write his full name in the mails > and it is not clear to me how the servers are > administered (who pays for it? who has access to it? who has access to the main servers are provided by arpi fate server by baptiste coverage by ubitux > hosting company's setting page?) [2] my knowledge of the hosting details is limited > - Git merges: when I first came to this project merges are still called > "Merge > from remote tracking branch 'qatar/master'." WTF is qatar? Now of course > that is not a problem any more, but the merges remain undocumented on any > official documentation I could find (maybe I didn't look hard enough?). If > the behavior itself is not known publicly how can anyone help? They are probably undocumented on the FFmpeg side but iam not sure what to document beyond what is in the git manual page > - Coverity: one can easily hook it up to a FATE box. maybe, but there are some special considerations * as many as possible features, external libs, ... have to be enabled as coverity only tests what is actually build * the authorizaton token needed to upload must never end in any vissible fate results * actally running fate isnt needed so a simple cronjob seems better suited /easier than fate but if you want to take coverity build/uploads over i can provide you with the details needed to upload and what is currently enabled (i dont want to loose testing for (m)any components) > > [1]: https://github.com/FFmpeg/FFmpeg/blob/master/MAINTAINERS#L48 > [2]: Yes I guess I can ask on IRC or whatever but I am lazy, and I know that > there are people lazier than me. If it is so hard to find out how to > *volunteer* I would not imagine many people trying to volunteer. > > But anyway, I can volunteer to take over coverage.ffmpeg.org. But again who > should I find to discuss this thing in detail? Michael? Clément? I don't > know. coverage is 100% Cléments area, i dont know if he wants/needs any volunteers for it > > Also a news article on a call for maintainers would be beneficial (?). yes but the last one was not too effective, so maybe someone else should write that [...] -- 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] Areas needing work
On Sun, Apr 5, 2015 at 8:43 PM Michael Niedermayer wrote: > Hi all > > There are various areas in the project that are not maintained as well as > they > should be, heres a certainly not comlpete list, dont hesitate to reply and > add to it. > If someone wants to pick something up and contribute that is VERY welcome > > * Post merge review&cleanup, changes merged from libav would benefit from > people reviewing and MUCH MUCH more importantly also people actually > caring > about and taking responsibility not just dumping comments with the idea > "someone" will fix it. > Ideally each area would have a maintainer who takes care of it and > keeps it in good nick. > > > * fate clients > we lack a armcc test, a real android test > someone should take over haiku and sunos/solaris fate clients, my haiku > VM just > keeps crashing > I can take care of the Haiku test if I have (access to) a better/faster computer… > * our fate server lacks the ability to display a user specified release > this makes the output look quite unwieldy > Timothy was working on a rewrite > I haven't touched that thing in a few months but it's in a pretty good shape. With a few minor updates it should be good to go at least on fate-beta.ffmpeg.org or something like that. There are still a few minor things I want to fix (like minirep/minilog, warning diff (is it really useful now since most boxes are using make -jx and testing order changes every time?), and some minor styling issue). [...] > * Decentralize > Too many things are done and admined by me, iam doing security updates > to the > servers, doing the git merges, maintaining all releases, maintaining > half the > fate clients, submitting data to coverity and doing all the crap that > noone > else wants to do. > Does the community care so little that they want me to be a single point > of > failure? > We need people to take some of this over at least on the basis of a > backup > in case iam unavailable for whatever reason, and i think it should > ideally > be people who do not yet have their daily work shedule overflowing with > ffmpeg > work but better new volunteers. > - Project servers: MAINTAINERS list four people [1], one of which I have never ever seen on this list, and it is not clear to me how the servers are administered (who pays for it? who has access to it? who has access to the hosting company's setting page?) [2] - Git merges: when I first came to this project merges are still called "Merge from remote tracking branch 'qatar/master'." WTF is qatar? Now of course that is not a problem any more, but the merges remain undocumented on any official documentation I could find (maybe I didn't look hard enough?). If the behavior itself is not known publicly how can anyone help? - Coverity: one can easily hook it up to a FATE box. [1]: https://github.com/FFmpeg/FFmpeg/blob/master/MAINTAINERS#L48 [2]: Yes I guess I can ask on IRC or whatever but I am lazy, and I know that there are people lazier than me. If it is so hard to find out how to *volunteer* I would not imagine many people trying to volunteer. But anyway, I can volunteer to take over coverage.ffmpeg.org. But again who should I find to discuss this thing in detail? Michael? Clément? I don't know. Also a news article on a call for maintainers would be beneficial (?). Timothy ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
[FFmpeg-devel] Areas needing work
Hi all There are various areas in the project that are not maintained as well as they should be, heres a certainly not comlpete list, dont hesitate to reply and add to it. If someone wants to pick something up and contribute that is VERY welcome * Post merge review&cleanup, changes merged from libav would benefit from people reviewing and MUCH MUCH more importantly also people actually caring about and taking responsibility not just dumping comments with the idea "someone" will fix it. Ideally each area would have a maintainer who takes care of it and keeps it in good nick. * fate clients we lack a armcc test, a real android test someone should take over haiku and sunos/solaris fate clients, my haiku VM just keeps crashing * our fate server lacks the ability to display a user specified release this makes the output look quite unwieldy Timothy was working on a rewrite * Paid maintainers a big problem is that we have areas in the codebase that have no maintainr or rather noone with sufficient time+will+abilty. It would help tremendiusly if maintainers could work full time on maintaining code instead of just a few hours in their free time * ffserver lacks a regression test code that is not tested will accumulate bugs. period there are people who use ffserver, they clearly like the lack of regression tests it seems as noone finds the need to look into changing that. * more people should help on https://trac.ffmpeg.org, like check that tickets contain all information needed to reproduce and ask the reporter to provide missing information, check if things are regressions, if they can be reproduced, bisect regressions or ask the reporter to bisect and help him if needed close tickets where there is not enough information to reproduce and the reporter doesnt react for months. ATM carl does all that and more but iam sure he wouldnt mind if more people would help him * Stipends and Sponsorship programs We do not have enough funds for basic things, for example OPW/Outreachy is twice a year and to participate we have to pay at least one stipend (about 6.5k USD). We participated in december 2014 and it allowed us to convert all remaining libmpcodecs filters to the native system. resulted in multiple new video filters and several block ciphers which are faster then all other tested implementations. For may 2015 we only way after the last minute managed to secure some funding so we are short of applicants now as for a long time ffmpeg was not listed as a participating org. * Decentralize Too many things are done and admined by me, iam doing security updates to the servers, doing the git merges, maintaining all releases, maintaining half the fate clients, submitting data to coverity and doing all the crap that noone else wants to do. Does the community care so little that they want me to be a single point of failure? We need people to take some of this over at least on the basis of a backup in case iam unavailable for whatever reason, and i think it should ideally be people who do not yet have their daily work shedule overflowing with ffmpeg work but better new volunteers. * Conferences / exhibitions, public stuff Theres a conference, linuxtag, fosdem, whatever, wherever in your local area and you think FFmpeg should be represented there ? Simple, go there and represent FFmpeg! unless you are too shy ... of course. FFmpeg is a large community of users and developers, the developers who managed the last stands/booths arent special, every FFmpeg developer and even Users who know ffmpeg a bit better who like can do this too. Also please add all conferences / exhibitions to https://trac.ffmpeg.org/wiki/Conferences You dont have time to help with any above or you prefer pretending that you dont, well, maybe you know someone else who could help with something, dont hesitate to ask them / forward this! please make sure to keep ffmpeg-devel in CC if you reply from ffmpeg-user -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I know you won't believe me, but the highest form of Human Excellence is to question oneself and others. -- Socrates signature.asc Description: Digital signature ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
