From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 710744C88B for ; Tue, 16 Sep 2025 21:15:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ffmpeg.org; i=@ffmpeg.org; q=dns/txt; s=mail; t=1758057292; h=date : to : in-reply-to : message-id : references : mime-version : reply-to : subject : list-id : list-archive : list-archive : list-help : list-owner : list-post : list-subscribe : list-unsubscribe : from : cc : content-type : content-transfer-encoding : from; bh=5fvxdFumWpvQLuVgtSFbK+aLmIY9Vlhd/5Prfq30r+4=; b=RkRGDeTINGcqcQDqP+0REg2cXIFbJ7ilR6vtyntOsWHTKnMIeVNy9RtzTUjeg6STYhngn D3U6CiIPRFeTbbXuXaeTJ57oug2VXaooPJ40BvH6yNa/ffCdM0AMEgsw5tcRcTJnitUMigd rdDtbmQBZbA41AWixxEWgH11wNx/wjDpRlUyV8269zNvj4/zQRQ0e6spfLOW4PN7RSf3gUP kMZ1kIt05uUYntGKvdzy1AnlbttyZEab6vmx2L2FQgoYEHhOTJrVA8Mnl8rjiuOJJ/ClbLg GQdGZpJ2aFg0DA2ggeAkuK+EK5eXHOKGvM08UV4Y9wLu04KKdoL3DCzneB2Q== Received: from [172.19.0.4] (unknown [172.19.0.4]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 07D0768E8C2; Wed, 17 Sep 2025 00:14:52 +0300 (EEST) ARC-Seal: i=1; cv=none; a=rsa-sha256; d=ffmpeg.org; s=arc; t=1758057290; b=JiR3hf+RpY7Rs+uMBIB5d5V4IiVfKRz/BR64hvNYjW9CcNUVcIMTbjtwptqZZkx73B/tt BL4IsHS/PzcwXYlwCmyOoIdHdkxucEjiXue/FzMmbtKipvcR8CxPnjRIyXSkX/j+E0cNX7V GsblK6AxKRl1PCR+UG8zVuWBn5jmGrPoSBRpkN+OHe6Ihk6VMcAu7ky/b13TaC3vBjxaTIf pqF9KuGCNFPQ8yUtEkMuzNFgHDDOtzWiI1GanfYXkm3G5j9QuAVLU9TVAjHSf/QM2Br0kru KMsE2Kvo8Vv+FklekPtV0UHTnKAFxl73O1JXjy4VX0AD0ahkIDocTF7jAfxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=ffmpeg.org; s=arc; t=1758057290; h=from : sender : reply-to : subject : date : message-id : to : cc : mime-version : content-type : content-transfer-encoding : content-id : content-description : resent-date : resent-from : resent-sender : resent-to : resent-cc : resent-message-id : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive; bh=71Gl0wsboJls5tsQalanf1P9wqM8qQOIEHy+OpsOnr4=; b=fL29hgZTpLFxahDEki5jWbqDq2LMLaYAeWSncaurTXU61Xiu/bwH3gTa3ScR/+gL0RCMx EIgjm6SLUQ6jqyD1HoVKpQkMfJUxK5lXfFFqSkqUxsrNcNaWhohW1pAqMUurU9FOTeUI2dg S1H5NoxfGbKnVSSC9aBe7oHNpRbPSWNtmynL1oJXmh+J8pgLcsajVB6cbRpNhQhhRSB1wae qgIvDV3PNL/xw/3pdpqjvmoq8PXsYvaG8R3t+Y2nHU+wm9BTHn+/V+50BKKVOyLGeS+v/YC Ttvfcw2h9M8L8+QeP6mlzyPmyBCtAXOFDPpDoJuvBZKMmaSPkscMen8jwf8g== ARC-Authentication-Results: i=1; ffmpeg.org; dkim=fail; arc=none; dmarc=none Authentication-Results: ffmpeg.org; dkim=fail; arc=none (Message is not ARC signed); dmarc=none Received: from iq.passwd.hu (iq.passwd.hu [217.27.212.140]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 8E74768E754 for ; Wed, 17 Sep 2025 00:14:37 +0300 (EEST) Received: from localhost (localhost [127.0.0.1]) by iq.passwd.hu (Postfix) with ESMTP id 26A70EBF8E for ; Tue, 16 Sep 2025 23:12:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at passwd.hu Received: from iq.passwd.hu ([127.0.0.1]) by localhost (iq.passwd.hu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoRMOjZpzmph for ; Tue, 16 Sep 2025 23:12:55 +0200 (CEST) Received: from iq (iq [217.27.212.140]) by iq.passwd.hu (Postfix) with ESMTPS id A3E71EBF89 for ; Tue, 16 Sep 2025 23:12:55 +0200 (CEST) Date: Tue, 16 Sep 2025 23:12:55 +0200 (CEST) To: Michael Niedermayer via ffmpeg-devel In-Reply-To: <20250916084900.GR29660@pb2> Message-ID: References: <20250916084900.GR29660@pb2> MIME-Version: 1.0 Message-ID-Hash: L53XEK7KLPMIDF44352TKF353MK5NKEP X-Message-ID-Hash: L53XEK7KLPMIDF44352TKF353MK5NKEP X-MailFrom: SRS0=Qonp=33=passwd.hu=cus@ffmpeg.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ffmpeg-devel.ffmpeg.org-0; header-match-ffmpeg-devel.ffmpeg.org-1; header-match-ffmpeg-devel.ffmpeg.org-2; header-match-ffmpeg-devel.ffmpeg.org-3; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list Reply-To: FFmpeg development discussions and patches Subject: [FFmpeg-devel] Re: [POLL] [VOTE] code.ffmpeg.org vs. ML List-Id: FFmpeg development discussions and patches Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Balint Marton via ffmpeg-devel Cc: Balint Marton Content-Type: text/plain; format="flowed"; charset="us-ascii" Content-Transfer-Encoding: 7bit Archived-At: List-Archive: List-Post: On Tue, 16 Sep 2025, Michael Niedermayer via ffmpeg-devel wrote: > Hi all > > 2 months ago we voted on testing Forgejo vs Gitlab, we picked and tested > Forgejo. And as said in that vote, (and surprisingly, i have not forgotten it) > heres the "after testing" discussion and vote > > do we want to keep Forgejo or switch back to the ML workflow > (or something else) Forgejo was not bad, but I remember some issues: - When doing individual patch reviews and quoting code the code context gets messed up, maybe it is references the combined diff? - Comparing pull request versions does not remove the upstreamed commits from the comparison, so if a new version is newly rebased, I see upstream commits as well in the comparison. - I am not sure what would be the counterpart of doing a last-chance ping before applying a series in the foregejo system, it was a useful thing in the ML workflow. Maybe some "auto-apply this in 1 day even if there are no approvals" checkbox with mail notificaitons could work, and that would also resolve the issue of self-approval. - Bumping versions and final commit polishing is a bit tiresome with foregjo. E.g. it would be nice if I could also edit the commit message, not just the commit title in the web page... - Pull requests show up on the mailing list but not force pushes, so people only reading patches via email won't get notifications of new versions. Not sure how many of these are fixable... > > F. keep Forgejo as primary forge for patch/git workflow > M. switch back to the ML for patch/git workflow > > all GA members can vote, by publically replying here with a > "F." / "Forgejo" vs "M." / "ML" > End time is in 7 days unless teh community wants to extend that. > (Also if results are inconclusive like because a 3rd option emerges > then ill restart this with condorcet on vote.ffmpeg.org) > > * If we keep forgejo we will likely transition our issue tracker tickets > into forgejo too, discussing with timo yesterday night indicates that > this likely can be done cleaner and neater than at first expected. Forgejo issue tracker is seriously lacking features: - severities - resolutions - issue workflow - votes - custom keywords for components (e.g. mxf, mpegts) Simple tags to emulate all these is a hack, e.g. how can you enforce a single severity or a single resoluton for a resolved issue? Or do ordering by severity or status? So this vote being about ML v.s. forgejo should not cause any decision regarding the issue tracker, that should be another vote if any. Until forgejo catches up, I'd rather keep trac. Regards, Marton > > * if we switch back to the ML, we still could have subsystem maintainers > using their own forge > > > thx > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > I have often repented speaking, but never of holding my tongue. > -- Xenocrates > _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org