From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id E940D4DA29 for ; Thu, 27 Feb 2025 23:01:17 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 8C17D68D907; Fri, 28 Feb 2025 01:01:13 +0200 (EET) Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com [209.85.167.50]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 49C8F68D823 for ; Fri, 28 Feb 2025 01:01:07 +0200 (EET) Received: by mail-lf1-f50.google.com with SMTP id 2adb3069b0e04-5452df178b2so237183e87.0 for ; Thu, 27 Feb 2025 15:01:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proxyid.net; s=google; t=1740697266; x=1741302066; darn=ffmpeg.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=CQ/RPYwzXTDqTC5rVYRUBER2dvb7BKWhifCjFRUkKXk=; b=fa+eG1ZsPHn8gTdfp0kcMeNfp93zlAjMmEMob495sv8uSptsZLA2umOjsIrMF1k0jY OUtty2ltJDnPd5Qpj7XhOGu5/VhORUI1wxsQqPO31WIBLS9ozyoi795WW+icfj5hUtly hsWv0YBTDIVzLH6zTnhDAzmDOG/Lle8vR0VZ/oVWTJ0oHaBENp0XgapmX2fHlxTziMV8 WFXhqpQqF5msDZlZ5N6zh/st+8RI0GQ2QBidywTM0Ml65ggVMhj0zNOfNn1bw9db/hWP 1b5u0ZYcGOBijxm8sNzHGGroXOuBpZbZXDc1GWZiz0TuOEIGeAC9xGuSNle70zIOzxPg xkRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740697266; x=1741302066; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=CQ/RPYwzXTDqTC5rVYRUBER2dvb7BKWhifCjFRUkKXk=; b=tsbZax7EPVi3G4zH+sPyM6Ik/rU2H0gvl3vIZ6Ju9XNOH/Ea+A1E4PmrGKwo77WVKJ BeBSwXQNO9EhGGkWbtVpTRRUuqANr4VXqsDa5Y3UBJTcn7a5bsgyVJ5GUVYlHu6hp4ts Hvhm76o6Y9mFU6RkKkkPs0A1ZNDjkgJ8ZWtUezgr8n7KcpDI0ZVxAcxhVMHzHp0XNj28 qZzQM7ShmUoOleXNfkx6tdyTq9brPfml0beTquJPZCS/1yhW7+gjP6sAVQucGyO7Ar92 49mtZCiB5yJRQBL+SxBRkIYqhigFBMfPynDjsWZtrPh9sQLZomYFioes9tiG/fKKM/bE Josw== X-Gm-Message-State: AOJu0Yx84vX6hf9+XIxe+BYzr4LOesbXeNUfS3am3HfGrDiFmGzkFFHY pOD46seV2HqpaBXyhOvbHO4JOG4zHWTT8VA9UChbyLJ68GfyAdacjSZYaRc6qFrIVGJ5tXhFLAq z/3SYOxMg24o/spxxHlk47DG7K0jAmdxgc6jjNhB1LJjCGpEbVLXa+g== X-Gm-Gg: ASbGncsywFA7nocH07uJ2I6cE1ffca/Bk3wep84Ld4xN0r42N9tOSf4dGtRz1PijUc1 5iGJFTx8NvK9IM3oHOzvhayk+C4umlaJsTPiJgeMEBRwHG3RfYS8heoAMkFCnayBppiXvfEMPS5 nJugG5KGg= X-Google-Smtp-Source: AGHT+IGh4PBTwFHoNOdx3kCHuijixhmQHS06RpJdf3NQtiGSPGQIgMp0Ow4Ar/4rwVqGiVutUEWwZxiBKDybo4NoWFw= X-Received: by 2002:a05:6512:b97:b0:545:291:7ee5 with SMTP id 2adb3069b0e04-5494c35054cmr119664e87.11.1740697266189; Thu, 27 Feb 2025 15:01:06 -0800 (PST) MIME-Version: 1.0 References: <20250226015112.GC4991@pb2> <8c1d1b3f-8a76-42c2-9a18-9cc0cef5253d@betaapp.fastmail.com> <20250227181808.GG4991@pb2> In-Reply-To: <20250227181808.GG4991@pb2> From: Marth64 Date: Thu, 27 Feb 2025 17:00:30 -0600 X-Gm-Features: AQ5f1JqGEerQ-T3q3Rat4X-8He3ozdRPGtoclilL_ZvfXwqv7y916kzlCBHcfB0 Message-ID: To: FFmpeg development discussions and patches Subject: Re: [FFmpeg-devel] =?utf-8?q?FFmpeg_Community_Committee_=E2=80=93_Up?= =?utf-8?q?dates_=26_Next_Steps?= 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 Michael, Thanks for the reply & thoughts. To clarify on "internal panel" and "structured issue resolution", this is with regards to unresolved complaints sent to CC, such as publicly or privately reported interpersonal/CoC issues. Some high ticket items directed to the CC from last year remain unaddressed and we were elected to be accountable for this, so we have to move forward in some way. There are tough problem statements to unpack and it is not always simple. The point I was trying to convey is we are going to approach, review, and push to closure on reported issues in a methodical fashion. We have set up a cadence to meet on items that our attention was called to. Kind of like a standup meeting on the tasks we are assigned to. So the "panel" in that regard, is a check-in amongst ourselves. If we feel other people or opinions need to be involved we will navigate that bridge as we get there. If CC is engaged for a task then we have to look into it and figure out a plan or execution. IIRC one main concern of the CC last year was there was limited movement on problem solving. "laying a strong foundation for the future" is with regards to us putting a process in place and being a visibly effective CC. The phrase is ambitious but focused on issues that are on our docket. It's not a blanket statement for a revolution. For example, laying a parallel hypothetical, this is as if the TC met once a week to discuss "what's on our agenda this week? what actions do we need to take? how do we clear roadblocks? what is our north star for the future?" Does this help? Thank you, Marth64 _______________________________________________ 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".