[FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org

* [FFmpeg-devel] [PATCH] web: announce code.ffmpeg.org
@ 2025-07-22  3:53 Lynne
  2025-07-22  8:44 ` Kacper Michajlow
  2025-07-22 15:01 ` Leo Izen
  0 siblings, 2 replies; 4+ messages in thread
From: Lynne @ 2025-07-22  3:53 UTC (permalink / raw)
  To: ffmpeg-devel; +Cc: Lynne

---
 src/contact | 11 +++++++++++
 src/index   | 52 ++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 63 insertions(+)

diff --git a/src/contact b/src/contact
index 6943d06..8a59864 100644
--- a/src/contact
+++ b/src/contact
@@ -1,3 +1,14 @@
+<div class="well">
+  <h3 id="Contributions">
+    <i class="fa fa-pencil"></i>
+    Contributions</h3>
+  <div style="color: white">
+    <p>
+      To contribute to FFmpeg, login or sign up for an account on <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>.
+      The main repository of the project is <a href="https://code.ffmpeg.org/FFmpeg/FFmpeg">code.ffmpeg.org/FFmpeg/FFmpeg</a>.
+    </p>
+  </div>
+</div> <!-- well -->
 
 <div class="well">
   <div class="row">
diff --git a/src/index b/src/index
index 52829e1..1f45dec 100644
--- a/src/index
+++ b/src/index
@@ -35,6 +35,58 @@
     News
   </h1>
 
+  <h3 id="forge">July 22nd, 2025, Modernization of contributions</h3>
+  <p>
+    The project is modernizing its contribution methods and switching to a software forge.
+  <p>
+  </p>
+    We have setup a platform on <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>. The new process
+    features continuous integration on all commits and merge requests, labelling for categorization,
+    conflict resolution, and logging in via OpenID or Github.
+  </p>
+  <p>
+    The main repository will become <a href="https://code.ffmpeg.org/FFmpeg/FFmpeg">code.ffmpeg.org/FFmpeg/FFmpeg</a>,
+    with all others being mirrored to it.
+    Users are encouraged to begin using it, effective now.
+  </p>
+  <p>
+    Mailing lists have supported our development for
+    <span title="with a total of 346,615 emails since April 2005">nearly 25 years</span>,
+    but as more and more contributors started to become involved, the ratio of merged patches to total mails begun
+    <span title="perhaps just correlation">falling</span>. Mailing lists became a source of friction,
+    with discussions frequently stalling and uncategorized noise drowning out patches by bumping them down in inboxes.
+  </p>
+  <p>
+    Although <a href="https://patch.ffmpeg.org/">patchwork.ffmpeg.org</a> was set up to track submissions,
+    it was less than reliable, with many patches and mails slipping though. Since its activation exactly
+    9 years ago, it recorded 54,476 patches, with 53,650 patches having the state of not archived.
+    In comparison, the mailing list has had a total of 150,736 emails during the same time period.
+  </p>
+  <p>
+    Additionally, new users have frequently encountered difficulties with mailing list development.
+    From finding out the correct SMTP login details, configuring git send-email, new email security
+    mechanisms interfering with mailing list operations, and finally not having a comfortable workflow
+    to review patches.
+  </p>
+  <p>
+    After years of discussions, and a vote, we officially announce the new platform,
+    <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>, running <a href="https://forgejo.org/">Forgejo</a>.
+    Documentation will be updated to reflect the change.
+  </p>
+  <p>
+    Mailing lists will continue to be monitored, and used for project discussions and other topics
+    better discussed elsewhere, but traffic and noise should become significantly reduced over time.
+  </p>
+  <p>
+    Bugs/issues will be accepted on <a href="https://code.ffmpeg.org/">code.ffmpeg.org</a>, alongside
+    with <a href="https://trac.ffmpeg.org/">trac.ffmpeg.org</a> for the time being.
+  </p>
+  <p>
+    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.
+  </p>
+
   <h3 id="pr7.1">September 30th, 2024, FFmpeg 7.1 <span title="Rózsa Péter">"Péter"</span></h3>
   <p>
     <a href="download.html#release_7.1">FFmpeg 7.1 "Péter"</a>, a new
-- 
2.50.0
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 4+ messages in thread