Hi. Michael Niedermayer via ffmpeg-devel (HE12026-04-26): > I suggest you get a backtrace and report this to the gcli developers > it seems it is actively developed
As I said in the mail I just sent, using git head instead of the version in Debian seems to work. But now just replying to the mailing-list just works, and that is very good, I will just do that. Thanks again for that. > I agree 100% that it should be documented > > I dont think threats and force would bring anyone to document it > What works is if people understand the importance, and care about the project > The other way that works, is if someone is payed to do it. It is not a threat. Am I the only one who remembers this whole thing is an EXPERIMENT? Well, when there is an experiment, at some point one must observe the results and draw conclusions. So, as leader, what observations do you make and what conclusions do you draw? Is it a frank success, shall we continue? Is it a failure, shall we drop it and go back to something that works? Or is it in-between, shall we go back to what we were doing and try again in a few years fixing our mistakes? What I observe from here: - Promises of documentation were made and not kept. - We have a worsening of the communication in the project due to a fragmentation of the discussions into pull requests that only a handful of people follow, it has lead to patches being applied without a proper review and containing severe flaws. I do not call that a success. > I think if you just wrote (and pushed, ideally after review) documentation, > that would work > better. I cannot write documentation for things I am not capable of doing. By the way, I just enable 2FA on my account, so you can make it able to approve or close pull requests and such if you please. Regards, -- Nicolas George _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
