On Tue, 4 Mar 2025, 19:01 Kieran Kunhya, wrote:
>
>
> On Tue, 4 Mar 2025, 11:17 Michael Niedermayer,
> wrote:
>
>> Hi Kieran
>>
>> On Tue, Mar 04, 2025 at 08:13:11AM -0600, Kieran Kunhya via ffmpeg-devel
>> wrote:
>> [...]
>> > Hi Michael,
>> >
>> > Was all the STF discussion around the first ap
On Sun, 02 Mar 2025 12:16:37 +0200, Rémi Denis-Courmont wrote:
> FFmpeg MTA would actually be illegal.
i have seen multiple mails from you about how you think developers have
or may do something illegal against you.
it makes me personally never want to talk or work with you at all.
https://list
On Tue, 4 Mar 2025, 11:17 Michael Niedermayer,
wrote:
> Hi Kieran
>
> On Tue, Mar 04, 2025 at 08:13:11AM -0600, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
> > Hi Michael,
> >
> > Was all the STF discussion around the first application done in public?
>
> No, jb contacted STF in the name of F
Hi Kieran
On Tue, Mar 04, 2025 at 08:13:11AM -0600, Kieran Kunhya via ffmpeg-devel wrote:
[...]
> Hi Michael,
>
> Was all the STF discussion around the first application done in public?
No, jb contacted STF in the name of FFmpeg without any public discussion.
This crossed STFs own reaching out t
On Mon, 3 Mar 2025, 20:35 Michael Niedermayer,
wrote:
> Hi jb
>
> On Thu, Feb 27, 2025 at 12:11:39AM +0100, Jean-Baptiste Kempf wrote:
> > On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote:
> > > 1. I agree we need discussions, transparency and maybe IRC or some
> other
> > >audio/vide
Hi jb
On Thu, Feb 27, 2025 at 12:11:39AM +0100, Jean-Baptiste Kempf wrote:
> On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote:
> > 1. I agree we need discussions, transparency and maybe IRC or some other
> >audio/video form of commuication can be tried. Such discussion should be
> >
Le perjantaina 28. helmikuuta 2025, 21.29.53 UTC+2 Michael Niedermayer a écrit
:
> Also id like to ask for every of your meetings to be recorded and made
> public.
Your request has been noted and it is hereby formally denied.
My fellow CC members and I have freedom of reunion and privacy rights.
On Fri, Feb 28, 2025 at 8:27 PM Michael Niedermayer
wrote:
> Hi Marth64
>
> On Thu, Feb 27, 2025 at 05:00:30PM -0600, Marth64 wrote:
> > Hi Michael,
> >
> > Thanks for the reply & thoughts.
> >
> > To clarify on "internal panel" and "structured issue resolution", this
> > is with regards to unres
On Thu, Feb 27, 2025 at 05:00:30PM -0600, Marth64 wrote:
[...]
> 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
The TC has no agenda. It handles cases o
Hi Marth64
On Thu, Feb 27, 2025 at 05:00:30PM -0600, Marth64 wrote:
> 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 interp
On Fri, Feb 28, 2025 at 8:14 AM compn wrote:
> On Thu, 27 Feb 2025 23:41:14 +0100, Vittorio Giovara wrote:
>
> > them and make sure we can keep working together without grudges. Also
> there
> > are a lot of pending issues from that time (the most grave one IMO, how a
> > mailing list admin unila
On Thu, 27 Feb 2025 23:41:14 +0100, Vittorio Giovara wrote:
> them and make sure we can keep working together without grudges. Also there
> are a lot of pending issues from that time (the most grave one IMO, how a
> mailing list admin unilaterally censors a thread) whose resolution we
> should at
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
On Thu, Feb 27, 2025 at 7:18 PM Michael Niedermayer
wrote:
> Hi jb
>
> On Thu, Feb 27, 2025 at 12:11:39AM +0100, Jean-Baptiste Kempf wrote:
> > On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote:
> [...]
> > > 2. The CC is overstepping its authority.
> >
> > Literally, the email just says t
Hi jb
On Thu, Feb 27, 2025 at 12:11:39AM +0100, Jean-Baptiste Kempf wrote:
> On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote:
[...]
> > 2. The CC is overstepping its authority.
>
> Literally, the email just says that the CC is now meeting regularly; what
> authority can it be oversteppi
On 2/25/2025 10:51 PM, Michael Niedermayer wrote:
Hi Marth64
On Tue, Feb 25, 2025 at 05:04:00PM -0600, Marth64 wrote:
Dear FFmpeg Community,
We’d like to share an update on the work of the Community Committee
(CC). Starting this week, we will hold a weekly internal panel to
discuss community m
On Wed, 26 Feb 2025, at 02:51, Michael Niedermayer wrote:
> 1. I agree we need discussions, transparency and maybe IRC or some other
>audio/video form of commuication can be tried. Such discussion should be
>public and open. And they must include admins and main authors.
Great, the mailing
> While people who spent a significant time of their life working on FFmpeg
> may be great developers, their skillset might not be matching the one
> needed to handle a community.
>
> Cmon we've been over these points, let's not rehash the same drama over and
> over, and let the volunteers of the C
On Wed, Feb 26, 2025 at 2:51 AM Michael Niedermayer
wrote:
> Hi Marth64
>
> On Tue, Feb 25, 2025 at 05:04:00PM -0600, Marth64 wrote:
> > Dear FFmpeg Community,
> >
> > We’d like to share an update on the work of the Community Committee
> > (CC). Starting this week, we will hold a weekly internal
Hi Marth64
On Tue, Feb 25, 2025 at 05:04:00PM -0600, Marth64 wrote:
> Dear FFmpeg Community,
>
> We’d like to share an update on the work of the Community Committee
> (CC). Starting this week, we will hold a weekly internal panel to
> discuss community matters and ensure more structured issue res
Dear FFmpeg Community,
We’d like to share an update on the work of the Community Committee
(CC). Starting this week, we will hold a weekly internal panel to
discuss community matters and ensure more structured issue resolution.
One of our key goals is to address some of the lingering discussions
21 matches
Mail list logo
