[FFmpeg-devel] [POLL] [VOTE] code.ffmpeg.org vs. ML

[Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1185 bytes --]

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)

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.

* 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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org