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 ESMTPS id 6C8DA4AF11 for ; Wed, 29 Jan 2025 19:01:41 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 7F45468BD4B; Wed, 29 Jan 2025 21:01:37 +0200 (EET) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 1CC2268BB86 for ; Wed, 29 Jan 2025 21:01:31 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 538D7442E3 for ; Wed, 29 Jan 2025 19:01:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1738177290; 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=0xMJkaW2xacTpNkWp9V3dJT5VGCog3lTo0GijTgkAVw=; b=OqgFPmqBWOS+RmViBdol6LWAj8KKjO1luOtibDx3V6g8NxDiAh22a9LwFF+bohTTc62J0K M/a1xk+evfe4+Twl9nmqkLr4ndrHoxYTAtEoOJTavJdS0yZ2qn6ytaQLONdgtCScsv2VcV 2oXGKcTNaVjt/7C23sTNnFFuJPH9C0+SMA0vDx/W+ynfZlBPR0s2qS/5Cg2Cux5bETTnsQ jJO1svysVtFhbWcSkHL0qKRVTcVd8xyq2KHtC1hlfno2i9CbEd2BAD8RW299bM9fJwwcxZ B8TFlc22rMUrw2v52pYfjwylWlmegLGpjwP3Q2vUlSaEy84ZUxkjb7oSIJUGDg== Date: Wed, 29 Jan 2025 20:01:29 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20250129190129.GA4991@pb2> References: <20250128022117.GT4991@pb2> <79E2A15A-F7FD-4F05-AEDA-58633633B512@gmail.com> MIME-Version: 1.0 In-Reply-To: <79E2A15A-F7FD-4F05-AEDA-58633633B512@gmail.com> X-GND-State: clean X-GND-Score: -70 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgdefjeelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdeftddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttdejnecuhfhrohhmpefoihgthhgrvghlucfpihgvuggvrhhmrgihvghruceomhhitghhrggvlhesnhhivgguvghrmhgrhigvrhdrtggtqeenucggtffrrghtthgvrhhnpeelkeeggfffiedufeejueffjeduhedttdduledtheevveevtdeiueelhfdtuedtkeenucfkphepgedurdeiiedrieejrdduudefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepgedurdeiiedrieejrdduudefpdhhvghloheplhhotggrlhhhohhsthdpmhgrihhlfhhrohhmpehmihgthhgrvghlsehnihgvuggvrhhmrgihvghrrdgttgdpnhgspghrtghpthhtohepuddprhgtphhtthhopehffhhmphgvghdquggvvhgvlhesfhhfmhhpvghgrdhorhhg X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] GSoC 2025 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="===============8902848623993466004==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8902848623993466004== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="/Devbt5yi+ZKfv8W" Content-Disposition: inline --/Devbt5yi+ZKfv8W Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Yigithan Its good that you bring these issues up. Discussing about them is a step towards solving them see my coments inline below On Wed, Jan 29, 2025 at 06:51:40PM +0300, Yigithan Yigit wrote: > Hi Michael, >=20 > I want to give some feedback before GSoC=E2=80=9925 as GSoC=E2=80=9924 pa= rticipant. I speak for myself but I know some of other colleagues are shari= ng similar thoughts with me.=20 >=20 > First of all community has incredible talented people and I am not even s= ingle percent of those people. However I tried my best during the qualifica= tion stage and after that. My main problem was finding answer's inside a hu= ge codebase. I might come stupid ideas, bad implementations but to be hones= t when I asked about something in IRC I couldn=E2=80=99t get any answers, e= ven in my volumedetect(qual patch) I couldn=E2=80=99t get a proper review f= rom community.=20 >=20 > Guessing contributors are mostly the passionate driven. I find that passi= on beginning but lost day by day. I tried to share similar thought during V= DD, they told me this is normal and happening. Which shouldn=E2=80=99t be i= n my opinion. If project wants to yes, i also agree that this should not happen > newcomers or continuous contributors people should be more welcoming. I = understand you can=E2=80=99t force people to review some patches but still = there are some parts needed to be change, I can=E2=80=99t say specifically = which parts but they should be changed. Its a complex problem The average age of developers is becoming older, (meaning there are fewer n= ew developers joining than in the past) many now are payed by companies to do specific work for a company. Meaning they have less time to do what the community and FFmpeg needs as they spend time to do what the company needs I think people should attempt to shift payed feature implementation towards= payed maintaince and reviewing patches, picking up an area and maintaining it as their day job What is impotant is to have maintainers for every part of the codebase. But to have a passionate and dedicated maintainer, often either he needs to have authority or needs to be paid. Both we fail at. AND also it needs the mindset that maintainers are needed. For the payment, for example carl, who took care of the bug tracker for years (something tru= ly important) should have been hired by some company to continue that work, it would have made economic sense to these companies actually. Another example for Payment is the souvereign tech fund. last year we for t= he first time got accepted BUT first it was really hard to find developers who where willing to agree to do the work. And then there was a huge amount of infighting. The problem is there is not a mindset of "this makes sense", "lets do it" b= ut much more a mindset of bickering on whatevr the other did. Also various company executives could have encouranged the employees to do maintaince work for FFmpeg STF. Would have cost them 0, would have made a huge difference in how many people would have been available! And about authority. We have some developers who want to have a say in everything. That just tak= es all passion out for some people. I also think this was a big factor why Pau= l forked So IMO, the mindset of the FFmpeg team needs to change. If one sees another working on something lets say a booth or STF, or anything code related or anything code unrelated the idea would be to be supportive. <--- This would= help I belive The other change would be to draw clear lines and clearly give authority to people in their area so they have some borders that shield them from things that take their passion away. Which then makes them stop maintaining the co= de and that then takes the passion of contributors away. Or maybe to put this another way. Try to have exactly 1 cook in every kitch= en If you intend to eat the resulting food. >=20 > In addition to that I am very thankful to my 2 mentors (Thilo, Kyle) for = helping me every step. I do not want to understood like my mentors didn=E2= =80=99t help me. yes, id also like to thank them for working on GSoC thx [...] --=20 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. --/Devbt5yi+ZKfv8W Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZ5p7BgAKCRBhHseHBAsP q0S4AJ47x+0EzIwtqDATjtEFN9HON0U6DQCffnd6qvPcfcehVP3hiu/Ltcl5Abc= =FGXw -----END PGP SIGNATURE----- --/Devbt5yi+ZKfv8W-- --===============8902848623993466004== 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". --===============8902848623993466004==--