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 60E314C10D for ; Tue, 29 Jul 2025 21:43:06 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id C3ACD68C339; Wed, 30 Jul 2025 00:43:01 +0300 (EEST) Received: from mail-yw1-f180.google.com (mail-yw1-f180.google.com [209.85.128.180]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 26CC4687DB3 for ; Wed, 30 Jul 2025 00:42:54 +0300 (EEST) Received: by mail-yw1-f180.google.com with SMTP id 00721157ae682-71a27d982f1so23120177b3.2 for ; Tue, 29 Jul 2025 14:42:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1753825372; x=1754430172; darn=ffmpeg.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ahrEqcEiVGKVOZMlJ3wa1qiIyzuHi0PhW3tiYkHc6D4=; b=XFapjjTsYPS7j4eN9HjxS/loUG5WyhriWhiHIk/WcH7uyzC8qCJQKuao4xjOVzsyHN Rd5HO2j+588JAauXGTOVPSpm6Z+Dw/EFnS2gqCnTznC9Z1pYjSXzmat9Wu3NvgjNacnm T/2y0IdyJ2V1NVyY6y/qUxWo9hFbGsYnsMYLTkdEXpVQAzJt4OvrESZEEzqhf+KwCmGu q1HVAE11jX9rcKopIPP4lZsfarz4613N5G4MZdr/9y8EQ1UUUwlHSbwn6ArAAfCFVsOb sD+UAXk4fUnmXIP86MZj8/f+YlBM4TgvWZ61NOhfGjtK1sdWSFppRLNbX0NipP0tisyc nQew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753825372; x=1754430172; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ahrEqcEiVGKVOZMlJ3wa1qiIyzuHi0PhW3tiYkHc6D4=; b=Z6pIguEPHVnlyq+tsFlX773fbyZ3PdzPye6Ww0ARXAka9foEhNxE4ShVTK5qEvNyu7 wl7dGc1dBuAQEpPuHiaLm09Lrl87ncnDTRVlODyP5NSAqWSExo2A9R6bv9hy3+5g6pTU ayhOq4CbAe/Qc5F1EQou22esOUqGtkfvNf/OaTHxzvfEmMACdyOmieWJFcUG788HkvS1 rZJ56kN4ZqoFt4wLCWyDuxOgJ/gQSJmGgFbiObMU4KQK4C2tgUQlDnCj7pREHxe9NUnW 82YFwz231zZDRA+ZQ8gPd7tXwozcAMwwk2+RVN25R6FhJgtaHRaBu4Q8dP5RqeeWsgJu /jCg== X-Gm-Message-State: AOJu0YxdCpKKTOBNba4f+9mQWRHHsl0tVEbcRf/9suRKj9UqgUiVySXy sIZABr+/r1W7kVlzRSbb65YtbQ/6lEIsILnOv4YSAhrNRPUBW+BQlTESowN4g93Ru0sohxh/vlB x15U2sV+IMXfFFZsr8sba/7wVHMDos7izoTzgP3E= X-Gm-Gg: ASbGncvdTOjEGx6Wuzq+mEv+EkG1SKBhwYosbHWxUJFCqkTSdZuUZ5GqywaJzR7M+6b 5wC9fANrFZghKUpBS1kxCGj8eqI92TildXoZYfimAbRHYTlxKXrXdg6oVtD1tzAOMrmsDeJRlxE E6bzVBCfM7vdOaYCIpb1Zlyuwgvmzl0bfQvxVmcEXbLYXOmSfuc9CuGPLznUMsCxuafgYpvn0oh r/4hirn5mdKPbKXNSo= X-Google-Smtp-Source: AGHT+IE+9eSmAYiFlgDI97mxIsVpO8HQcxPK4ZVWPWA0qIDwdf94cbiUrGB+wYbfXWX4fX8b3A9My3h3az9SyVLzwJo= X-Received: by 2002:a05:6902:2207:b0:e8b:d2d0:8b07 with SMTP id 3f1490d57ef6-e8e314f51c0mr1623310276.13.1753825372274; Tue, 29 Jul 2025 14:42:52 -0700 (PDT) MIME-Version: 1.0 From: Romain Beauxis Date: Tue, 29 Jul 2025 16:42:41 -0500 X-Gm-Features: Ac12FXwyxptmvNaV8LE9zU2h_QPYKlBj8WxMbl6annGlC5a0q0NeBNNRtEXSyIU Message-ID: To: FFmpeg development discussions and patches X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: [FFmpeg-devel] Recommendations to facilitation patch reviews on forgejo/ML? X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Hi all, Are there any recommendations on how to best get attention to some patches/changes? With the introduction of the new forgejo workflow (which I personally welcome!), I am wondering how casual contributors like myself should approach the task of finding reviewers. So far, I am aware of the following: * Contact a listed MAINTAINER if they are still active * Get attention on the Mailing List. * Ping people on IRC * Forgejo? The advantage of the ML for this problem is that all patches are visible to all subscribers. But, for Forgejo, it seems very easy to have PRs fall through the cracks. The only thing that I can think of at the moment is to assign to people that have been active in reviewing other PRs. Is there a better suggested way? Should the ML be used to advertise PRs up for review? For a practical reference, here's my situation: while working on fixing ogg muxer/demuxer, I have had success getting some response from a general standpoint but I have never found someone committed to working on the ogg subset of the project and the listed MAINTAINER does not seem active anymore. I understand that ogg is an old container but it is still the standard container for a lot of online streaming and ffmpeg is the default implementation for most browsers reading (and more). It seems like it should be in the interest of the project to improve its support? The patch in question is here: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20026 Or here on the ML: https://ffmpeg.org/pipermail/ffmpeg-devel/2025-June/344442.html The larger context is a rewrite of the ogg/demuxer when working with sequential streams to: * Remove stream packet headers from the demuxer (as suggested by Lynne) * Fix PTS/DTS discontinuity. Subsequent ogg logical stream currently reset the PTS/DTS counter which is a problem. * Support copy-only repackaging of sequentialized ogg streams. Any advice would be welcome. Thanks! -- Romain _______________________________________________ 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".