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 362D04C7BE for ; Mon, 15 Sep 2025 19:10:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ffmpeg.org; i=@ffmpeg.org; q=dns/txt; s=mail; t=1757963400; h=message-id : date : mime-version : to : references : in-reply-to : 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=rxMPr0pxjLXSSCGHz61ixOwj+yZqIg0aR/i60+jxjmU=; b=P9X30I0UeEgTebkmT4xuD7v1Izrago0ydn1tAJ80SSrn6Fb64OKF7HPk56IAZQLlfE1bX C4E9AeMeunXRZPKJR1m4EH59wLpdiWHxzi8B6IVTtqvUYWDLFNx22A32GkR2AFdQeCmuN8E Hd31/rKoP5sPCaQfU3HmMfkW0WqZS0gDEPM56XsrRqfM3jI2VZzPcEF1FbeouiueSW/FDwk d5LElzVXE9ivh2iRfXlp7bbbA5+u/mGpmKY3djw1YHDoOLPYgQ8zMJ/95+iKia13QU2QjkK B101ke1Nv5ApAwGX3/1Z8wQ/RUIq+u45GRzxxWMuZAbY7pllfGrzrAXMjwxg== Received: from [172.19.0.4] (unknown [172.19.0.4]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 7774268E874; Mon, 15 Sep 2025 22:10:00 +0300 (EEST) ARC-Seal: i=1; cv=none; a=rsa-sha256; d=ffmpeg.org; s=arc; t=1757963399; b=HRLgIAkM58r5a+Z72Cu93qSTDipTXIB8G3FXrG29o7XndVJpw1YagRg/SPl82U4x3wxCZ sVsg+Itamsg8y1XXq3G4t3Opv8bu84/iaT4WAqxBQls8AG9gzSb9cHOZt2bhh8BW6L29rr+ b5XGHPCvqOFCUwi0h6aqLX8TDxB0gq8k0acGsFOjDfgG/AWF4w69tq7MQs91lQbKiUbSgo2 i7OWEZK00azHww3kGYTB2TkLM27vfoVKqh16KgI1dat74NMdhIUV5P8o0ku2nqMcxMgJSSx mIR95pTozCPNFC9TTAz9yyFVINzfncjfi+QfOOQ/OO0CdiHdlIcNGZuFYiDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=ffmpeg.org; s=arc; t=1757963399; 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=WL+9qolg+qYKYQ2TZzkz5YlV3uz/YWzAxbWhVRHWcKo=; b=s5teTFRULE625LeTJ7UfzmQ9yNl/Nfb7ZStekYrGnGvMI3GYkocTbq029Gjn34UsCie/o ZtVYzLTpy4urLfC0wQpY4qSLqMhyMQygVRY7rKZui8D8uN4FKSKUtC7vRT50vXwEY7R7Olf o2elnlxHV6IDTjxxBBUEZrF6e6d3HPc4bdgLOCa3xNI+WtW/XSfgJKOcCinYTIo5ZhQXKX6 Iq9COvKNrsNjHGFEN/YYRqMoks1AMZHaWJVF8AoV94ktEPMpUgb7H6i1ofv2z4wfzZyOWC8 wKpB2blrmbZSqQeHEBlQMvYfgYuGK4wBj4aoc24CTswhucctsKVIGXHYHuVQ== 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 mout-p-202.mailbox.org (mout-p-202.mailbox.org [80.241.56.172]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 9E8C268E7FF for ; Mon, 15 Sep 2025 22:09:45 +0300 (EEST) Received: from smtp102.mailbox.org (smtp102.mailbox.org [IPv6:2001:67c:2050:b231:465::102]) (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 mout-p-202.mailbox.org (Postfix) with ESMTPS id 4cQZN70k1Dz9t6L for ; Mon, 15 Sep 2025 21:09:43 +0200 (CEST) Message-ID: <612e19bf-919d-4a6b-8180-d7d655fbae83@gyani.pro> Date: Tue, 16 Sep 2025 00:39:37 +0530 MIME-Version: 1.0 To: ffmpeg-devel@ffmpeg.org References: <20250914212317.GG29660@pb2> <20250915110947.GH29660@pb2> <62f9da36-5260-49d3-8cf7-d59d6456fb0d@rothenpieler.org> <20250915125753.GK29660@pb2> <0d0942ee-82f9-4a40-a9c9-80f9cc00fe67@rothenpieler.org> <20250915182620.GM29660@pb2> <1298de15-af42-4280-b897-97aadab95087@rothenpieler.org> Content-Language: en-US In-Reply-To: <1298de15-af42-4280-b897-97aadab95087@rothenpieler.org> X-Rspamd-Queue-Id: 4cQZN70k1Dz9t6L Message-ID-Hash: N72U3FKRIDML4TQIIRPGWMSP25J44IUO X-Message-ID-Hash: N72U3FKRIDML4TQIIRPGWMSP25J44IUO X-MailFrom: SRS0=vkWB=32=gyani.pro=ffmpeg@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: [RFC] Issue tracker 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: Gyan Doshi via ffmpeg-devel Cc: Gyan Doshi Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit Archived-At: List-Archive: List-Post: On 2025-09-16 12:05 am, Timo Rothenpieler via ffmpeg-devel wrote: > On 9/15/2025 8:26 PM, Michael Niedermayer via ffmpeg-devel wrote: >> Hi Timo >> >> On Mon, Sep 15, 2025 at 07:19:17PM +0200, Timo Rothenpieler via >> ffmpeg-devel wrote: >>> On 9/15/2025 2:57 PM, Michael Niedermayer via ffmpeg-devel wrote: >>>> Hi >>>> >>>> On Mon, Sep 15, 2025 at 02:06:07PM +0200, Timo Rothenpieler via >>>> ffmpeg-devel wrote: >>>>> On 15/09/2025 13:09, Michael Niedermayer via ffmpeg-devel wrote: >>>> [...] >>>>>> Ideas, Comments ? >>>>> >>>>> I do think trac is a dead end software, and we want to eventually >>>>> retire it. >>>> >>>> btw, anyone knows why the trac project seems dieing / dead ? >>>> Its a quite capable issue tracker ... >>>> >>>> also how is it related to redmine, which seems to have some support >>>> for importing trac ? >>>> >>>> Have we considered redmine as alternative ? >>>> If we could do a full import of trac, this may be a smoother >>> >>> redmine is apparently a "trac clone written in ruby". >>> No idea if it's database-compatible, or just similar idea but full >>> re-implementation. >>> >> >>> But really, I don't see how in the long run a separate issue tracker >>> from >>> Forgejo makes sense. >>> The issue IDs will eventually clash, and integration and linking >>> between >>> them will be a right mess. >> >> the mix of trac and Forgejo is already a mess if theres no _clean_ >> way to import the tickets >> We would always have 15 years of ticket history outside our issue >> tracker >> >> if you really want to have pull requests and issues have distinct >> positive numbers >> well, make one even and the other odd above the value where they >> would clash >> so it would be >> 0..20k Trac >> 20k-25k Forgejo >> 25k+ even Forgejo >> 25k+ odd redmine > > That is not something that can be done, and honestly seems a bit silly > to me. > >> >>> >>> Plus the multi-account issue you mentioned. >> >> redmine can accept OAuth2/OIDC logins via plugins IIUC >> would need to be tested in a test setup but there seems support for >> shared >> accounts in principle > I honestly don't understand the insistence on an external issue tracker. > That just makes things more complex for no real reason. > > And I also firmly disagree about the current setup being "a mess". > With no new tickets being allowed on trac, its quite the opposite of > that. > If issues/tickets could be opened on both, then it'd be a mess. > This way it's just a migration. > > And the tickets on trac won't go away, so no history will be lost. > If you really want, I can import them all into Forgejo, but _that_ > will be horribly messy. It's best to have a single issue tracker. It's best for the issue tracker to be integrated with the code workflow. What can happen is that if an existing open trac issue is taken up for active resolution, then a new issue at Forgejo can be opened, with a reference to the trac issue. A comment can be left at trac linking to this new Forge issue, so all further activity occurs at code.ffmpeg. This would avoid any wholesale migration or duplication. Regards, Gyan _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org