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 2FACA4ACA9 for ; Sun, 19 May 2024 11:29:58 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 2041168CF47; Sun, 19 May 2024 14:29:52 +0300 (EEST) Received: from shout01.mail.de (shout01.mail.de [62.201.172.24]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id BDD6768A7ED for ; Sun, 19 May 2024 14:29:45 +0300 (EEST) Received: from postfix03.mail.de (postfix03.bt.mail.de [10.0.121.127]) by shout01.mail.de (Postfix) with ESMTP id 4A9B1240CE5 for ; Sun, 19 May 2024 13:29:45 +0200 (CEST) Received: from smtp01.mail.de (smtp03.bt.mail.de [10.0.121.213]) by postfix03.mail.de (Postfix) with ESMTP id 3054180192 for ; Sun, 19 May 2024 13:29:45 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp01.mail.de (Postfix) with ESMTPSA id 07705240A4D for ; Sun, 19 May 2024 13:29:43 +0200 (CEST) Message-ID: Date: Sun, 19 May 2024 13:29:43 +0200 MIME-Version: 1.0 To: ffmpeg-devel@ffmpeg.org References: <20240517134958.GQ6420@pb2> Content-Language: en-US In-Reply-To: X-purgate: clean X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate-type: clean X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de X-purgate: This mail is considered clean (visit http://www.eleven.de for further information) X-purgate: clean X-purgate-size: 4447 X-purgate-ID: 154282::1716118185-CCE261F9-9F887F34/0/0 Subject: Re: [FFmpeg-devel] [RFC] STF 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: , From: Thilo Borgmann via ffmpeg-devel Reply-To: FFmpeg development discussions and patches Cc: Thilo Borgmann Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: [...] >> * Fund administrative / maintainance work (one example is the mailman upgrade that is needed >> with the next OS upgrade on one of our servers (this is not as trivial as one might >> expect). Another example here may be some git related tools if we find something that >> theres a broad consensus about. > > I agree that this should be paid but I would expect that STF would not be too keen on it, not that I'd know really. We should absolutely pay for such activity and STF is very well willing to fund such things. >> * Fund maintaince on the bug tracker, try to reproduce bugs, ask users to provide >> reproduceable cases, close bugs still unreproduceable, ... >> ATM we have over 2000 "new" bugs that are not even marked as open > > This is a double-edged sword. If somebody gets paid to do that, then that is one more reason for others not to do it. > > And again, it is completely reasonable to be paid for that, and also for code reviews and writing test cases (if we want to complete the menial task list), but I am perplexed as to STF's stance on that. Same as above about that we should and STF would. Especially since no corporate interest usually pays anyone for these tasks (in case of reviews it might of course be considered a good thing). The one problem to solve here AFAICT is we don't know exactly what quantity of bugs, reviewable code submissions and other maintenance work will come up in the next 12 months. So it renders impossible to define in prior the workload, milestones and compensation per contributor interested as we did this year for well-defined tasks. What we should consider IMO is defining the tasks (patch review, bug review & fix, FATE extensions, checkasm extensions, etc. as well such things for the administrative tasks from above) and defining a budget for these tasks. Then, allow 'everyone interested' (aka git push access?) to claim a part of that budget every N-months, depending what the corresponding contributor actually did and can somehow be determined. Regarding STF, this could visualize as one big milestone per task with a budget of X and this group of people working on it. How exactly the money distributes from there, depends on the actual work done afterwards. However, there are many questions about the details for our side and probably on the STF side. We should however start with at least one of these tasks aiming for next year, trying to setup some process that would work for us and can then be aligned with what is possible with STF. >> * Fund professional real live presence on multimedia / FOSS / buisness related >> events. we already refund individuals but i think we are lacking on the organizational >> side. We should also have on these events at least one person who can awnser developer/user >> questions and someone who can awnser buisness questions (on buisness related events). >> Also we need some eye catching things there, a big screen/projector that plays some >> real time filtered version from a camera. Or maybe have more people remotely be available >> from the FFmpeg team through real time streaming (as in, if someone wants to be on some event >> but cant physically go there, we could put a notebook on the table facing visitors showing >> something like a video chat. Also we need more cute girls on these events, everything i hear >> its 100% male geeks/hackers. Also a "24/7" realtime stream from any booth would be nice > > This is not something that STF should pay for, AFAIU. This is something that professionals should pay out of their budget (or their employer's) for the business events, and SPI for cheap/community events, IMO. I think we should fund all non-b2b appearances. About b2b, I wouldn't like our donation based money to be spent. We had corporate sponsorship in the past not having to think about it and possibly will have that as well in the future. The companies are interested in seeing us there and some are willing to pay for that happening. I think we could as well get dedicated STF money to cover such costs not being dependent on supportive companies and plan ahead better. That is nothing that 'professionals' should pay out of their budget or should even be allowed to do as we talk about a presence for the open-source project, not some company's presence. -Thilo _______________________________________________ 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".