Hi Gyan On Tue, Sep 16, 2025 at 12:39:37AM +0530, Gyan Doshi via ffmpeg-devel wrote:
> It's best to have a single issue tracker. +1 > It's best for the issue tracker to be integrated with the code workflow. +1 > > 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. It can _IF_ someone spends the extra time and work. How many people want to do that ? And how many will do it ? And what do we gain by avoiding "wholesale migration" ? thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are too smart to engage in politics are punished by being governed by those who are dumber. -- Plato
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
