> + Bugs/issues will be accepted on code.ffmpeg.org, alongside > + with trac.ffmpeg.org for the time being. > +
People should not submit bug reports randomly to 2 trackers, thats a problem. It would make searching for issues 2x as hard. If we discuss and decide to change the bug tracker (which we have not discussed, less decided) -> than we should import all the issues from trac into the new tracker first. In fact i suggest we make the forgejo issue tracker forward people to trac currently > +> + We are also hoping that this will significantly reduce the amount of unmerged patches. > + If you submitted a patch which received no replies or conclusion, we apologize, and you are encouraged > + to resubmit it on the new platform. > +
The announcment should probably mention that performance, as in number of submissions / percentage of applied / not reviewed patches will be monitored compared to the mailing list. (and obviously someone has to do that, i do think such basic performance monitoring is important after/ during such a change) later then (in a month or whatever) we should make an announcment with the performance numbers [And if we want to have strong statistics, then it is neccessary to pre-announce _exactly_ when and what will be meassured how. https://en.wikipedia.org/wiki/Preregistration_(science) ] just thought this would be a interresting subject for a statistics paper, if someone (maybe outside the ffmpeg team) wants to do it ... thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB I am the wisest man alive, for I know one thing, and that is that I know nothing. -- Socrates