My take is that patches need to be dealt-with first. Looking over the history, many issue reports just have links to patches that have been submitted quite some time ago or from custom builds. Without a response to patch submissions, its not hard to see why the repo has slipped from its authoritative state. Considering its still the primary source for many builds despite most active development done in community forums, this seems ironic. With fixes already available (albeit many scattered across the internet), I think this should be the first and easiest to complete. The idea of building a patch archive over time and constantly having to apply it during every build scares the hell out of me and probably would most would-be developers. If we can get some of the more senior members all together and to build a list of current issues and a general project status, I think it would go a long way. I don't see attracting developers if it means their having to go through months of mailing list threads just to get an idea of what doesn't work. Matt On Mon, Dec 15, 2014 at 7:03 AM, compn <tempn@mi.rr.com> wrote:

On Sat, 13 Dec 2014 19:27:53 -0800 Timothy Gu <timothygu99@gmail.com> wrote:

...

On Saturday, December 13, 2014, compn <tempn@mi.rr.com> wrote:

...

anyone out there want to volunteer?

What's wrong with the current website?

Timothy

builds are outdated no releases have been made since 2010? http://rtmpdump.mplayerhq.hu/download/

information is outdated, still talking about 2.2 librtmp change. manual has no examples (maybe a good idea, let frontends front.) probably more projects need to be added to project list. no screenshots! the humanity! needs a layout? some color? black background? i dunno. donation button / bitcoin addy?

might need someone to fix up rtmpdump wiki page too http://en.wikipedia.org/wiki/RTMPDump

-compn _______________________________________________ rtmpdump mailing list rtmpdump@mplayerhq.hu https://lists.mplayerhq.hu/mailman/listinfo/rtmpdump