From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 01A4049716 for ; Thu, 18 Apr 2024 19:51:00 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 204B668D230; Thu, 18 Apr 2024 22:50:58 +0300 (EEST) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id AA16768CA2F for ; Thu, 18 Apr 2024 22:50:51 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id D7D80E0004 for ; Thu, 18 Apr 2024 19:50:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1713469851; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+k0w61YN7XDv8B3rwHjRpZUaGZladcxKlKMVfb5rRNc=; b=nGDaoWSKTHO1sMb+XKikeOYJz6J0C7ex5/UX2e4GzwOEgK3a/otPcDGB7aFo3ylxBFdPYB mo5/fRN2mdBdLeSd7LkBMHUGZLZn1xj3rgOJFxEOekDBltXAmwe7LgB2hNdZ4WVHJ9V/Jn ZspSIbZ1aIBRNlzVOyK13P32DT0Uhua/cXsFAv/pshciCQzU4hJ0MkY0o3Q8fhAleqUb0s WhhKtL9Ju7D6aOO3BTuIHmT0CgzE7gPjZ3m1pNhL4fiO4pa7Bh/TLWiiFHEPn85VBnTjdO swujGv15/6kftHwZAq9H6chuxOgJhP3HZpeXpBrzK0OGl71kUuaYWqcpOKqE4g== Date: Thu, 18 Apr 2024 21:50:50 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240418195050.GQ6420@pb2> References: <20240417135832.GJ6420@pb2> <6633f8dd-8198-4544-88f9-0938d74f5734@pileofstuff.org> <45C32695-88F4-4BE0-BA67-F5F4D0187967@gmail.com> <67e5052d-15e1-4c60-aa5f-88bc2a74c8d0@pileofstuff.org> MIME-Version: 1.0 In-Reply-To: <67e5052d-15e1-4c60-aa5f-88bc2a74c8d0@pileofstuff.org> X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [RFC] 5 year plan & Inovation X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============8815822313719856422==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8815822313719856422== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ZbngGSxm9NmzB4Qp" Content-Disposition: inline --ZbngGSxm9NmzB4Qp Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 18, 2024 at 11:22:09AM +0100, Andrew Sayers wrote: > On 18/04/2024 10:13, epirat07@gmail.com wrote: > > On 18 Apr 2024, at 9:52, Stefano Sabatini wrote: > > > On date Wednesday 2024-04-17 17:24:02 +0100, Andrew Sayers wrote: > > > > On 17/04/2024 14:58, Michael Niedermayer wrote: > > > [...] > > > > I've occasionally tried getting into ffmpeg for over a decade now, = and have > > > > lurked here for the past few months as I put in the effort to grok = it. > > > > On behalf of people who could contribute but don't, I'd like to sug= gest > > > > ffmpeg focus on *learnability*. > > > >=20 > [...] > > > > But other issues seem like quick wins - for example I've lost count= of > > > > all the times I typed two functions into Google, spent hours trying= to > > > > make them work together, then finally realised I was looking at the > > > > documentation for 3.0 in one tab and 5.0 in the other.=A0 Surely yo= u can > > > > just add a line to the top of the documentation like "click here to= see > > > > the trunk version of this file"? > > > Functions are documented in doxygen, so they depend on the major.minor > > > version, while you seem to refer to the FFmpeg version. Also on the > > > website we usually only have the latest mainline documentation, so I > > > don't understand how can you have different versions in different tabs > > > (unless you didn't update that tab since months/years). > > Thats not true and same things has happened to me multiple times, > > thats why I always have to check the URL to make sure the docs > > are the ones for master or latest release I am working with. > >=20 > > For example see this ancient documentation here: > > https://ffmpeg.org/doxygen/1.2/index.html >=20 > I'm glad I'm not the only one making that mistake!=A0 In fact, older vers= ions > don't just exist, they're often the first link in Google.=A0 For example, > typing "avformat_init_output" into Google and clicking on the first link > takes me to [1] (version 3.2). >=20 > The website doesn't have documentation for 6.1 or 7.0 ([2] and [3]), the docs for master are generated by a cronjob the docs for releases are manually generated, thx for reminding me about it, ive generated the 6.1 and 7.0 ones now [...] > Without getting too far off-topic, I would also be interested in knowing = how > docs are actually generated in practice. I've tried generating documentat= ion its just running doxygen with a Doxyfile the Doxyfile is not doc/Doxyfile from git because that could be a security issue. But its a very similar file thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Dictatorship: All citizens are under surveillance, all their steps and actions recorded, for the politicians to enforce control. Democracy: All politicians are under surveillance, all their steps and actions recorded, for the citizens to enforce control. --ZbngGSxm9NmzB4Qp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZiF5kwAKCRBhHseHBAsP q/SRAJ9XQfgY+UR/Br2T7ZiTyNJDzQvk9ACdEy5E9JJjDjH6au7ACHNoIgh4m8E= =zjJZ -----END PGP SIGNATURE----- --ZbngGSxm9NmzB4Qp-- --===============8815822313719856422== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". --===============8815822313719856422==--