On Tue, 07 Jan 2025 20:20:00 +0200, Rémi Denis-Courmont wrote:
> The new CC members such as I myself don't have access to previous
> communications and deliberations, at least not that I'd know.
the previous cc has not responded to all people who made previous
complaints. i dont think this was a
Hi,
Le 7 janvier 2025 21:54:06 GMT+02:00, Leo Izen a écrit :
>On 1/7/25 1:20 PM, Rémi Denis-Courmont wrote:
>> Le tiistaina 7. tammikuuta 2025, 6.46.24 UTC+2 Vittorio Giovara a écrit :
>>> S not to poke a bee's nest, but what's going on here? Are there any
>>> blockers for the elected people
On Tue, Jan 7, 2025 at 1:20 PM Rémi Denis-Courmont wrote:
> Le tiistaina 7. tammikuuta 2025, 6.46.24 UTC+2 Vittorio Giovara a écrit :
> > S not to poke a bee's nest, but what's going on here? Are there any
> > blockers for the elected people to assume their roles?
>
> I can't speak for the ot
On 1/7/25 1:20 PM, Rémi Denis-Courmont wrote:
Le tiistaina 7. tammikuuta 2025, 6.46.24 UTC+2 Vittorio Giovara a écrit :
S not to poke a bee's nest, but what's going on here? Are there any
blockers for the elected people to assume their roles?
I can't speak for the other members, so I'll st
Hi,
> The new CC members such as I myself don't have access to previous
> communications and deliberations, at least not that I'd know.
I'm in the same boat, I am getting to learn the issues and assisting
where I can. I think it will take a little time after the new year
for everyone to get reacqu
Le tiistaina 7. tammikuuta 2025, 6.46.24 UTC+2 Vittorio Giovara a écrit :
> S not to poke a bee's nest, but what's going on here? Are there any
> blockers for the elected people to assume their roles?
I can't speak for the other members, so I'll stick to pure facts... So far
there have been t
On Thu, Jan 2, 2025 at 3:12 PM Vittorio Giovara
wrote:
>
>
> On Mon, Dec 30, 2024 at 11:29 AM Leo Izen wrote:
>
>> On 12/28/24 11:53 AM, Ronald S. Bultje wrote:
>> > Hi all,
>> >
>> > (Prior note: the election was scheduled to end on the 23rd of December.
>> > Anton is currently taking a break s
On Mon, Dec 30, 2024 at 11:29 AM Leo Izen wrote:
> On 12/28/24 11:53 AM, Ronald S. Bultje wrote:
> > Hi all,
> >
> > (Prior note: the election was scheduled to end on the 23rd of December.
> > Anton is currently taking a break so I've asked him to let me announce
> the
> > election results.)
> >
On 12/28/24 11:53 AM, Ronald S. Bultje wrote:
Hi all,
(Prior note: the election was scheduled to end on the 23rd of December.
Anton is currently taking a break so I've asked him to let me announce the
election results.)
The poll has concluded, with 31 votes out of 52. Results are available at
[
Ronald S. Bultje 于2024年12月29日 周日00:54写道：
> Hi all,
>
> (Prior note: the election was scheduled to end on the 23rd of December.
> Anton is currently taking a break so I've asked him to let me announce the
> election results.)
>
> The poll has concluded, with 31 votes out of 52. Results are availabl
Hi all,
(Prior note: the election was scheduled to end on the 23rd of December.
Anton is currently taking a break so I've asked him to let me announce the
election results.)
The poll has concluded, with 31 votes out of 52. Results are available at
[1], the winning committee is:
* James Almer
* M
> Btw, i also wanted to say, in case you fail to receive enough
> support for a CC seat. Please ignore that and try to help anyway
> the ffmpeg community is in need for your help, i think
Thank you. I am not easily discouraged. At the end of the day,
I care most about FFmpeg being a good program a
Hi Marth64
On Wed, Dec 18, 2024 at 10:27:40PM -0600, Marth64 wrote:
> Hi Michael,
>
> > 2. and the most recent case
> Continuing where I left off.
>
> Let us analyze the s337m situation.
> * Contributor shares significant work, as an RFC, in good faith
> * A back and forth exchange happens with
On Thu, Dec 19, 2024 at 7:25 PM Michael Niedermayer
wrote:
>
> Hi Kieran
>
> First before replying, id like to say, that i hope we can resolve this and
> in the future work together in a mutually more friendly way.
>
> On Wed, Dec 18, 2024 at 10:18:20PM -0500, Kieran Kunhya via ffmpeg-devel
> wro
Hi Kieran
First before replying, id like to say, that i hope we can resolve this and
in the future work together in a mutually more friendly way.
On Wed, Dec 18, 2024 at 10:18:20PM -0500, Kieran Kunhya via ffmpeg-devel wrote:
> > 1a. Prior context:
> > For a long time FFmpeg booths where organize
Hi,
On Thu, Dec 19, 2024 at 2:02 PM Michael Niedermayer
wrote:
> Hi
>
> On Thu, Dec 19, 2024 at 08:27:50AM -0500, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Thu, Dec 19, 2024 at 8:05 AM Kieran Kunhya via ffmpeg-devel <
> > ffmpeg-devel@ffmpeg.org> wrote:
> >
> > > On Thu, 19 Dec 2024, 02:22 Mich
Hi
On Thu, Dec 19, 2024 at 08:27:50AM -0500, Ronald S. Bultje wrote:
> Hi,
>
> On Thu, Dec 19, 2024 at 8:05 AM Kieran Kunhya via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
> > On Thu, 19 Dec 2024, 02:22 Michael Niedermayer,
> > wrote:
> >
> > > Kieran reports this to the CC
> > > and jb
Hi
On Wed, Dec 18, 2024 at 07:40:43PM -1000, compn wrote:
> On Thu, 19 Dec 2024 03:22:46 +0100, Michael Niedermayer wrote:
>
> i think we need to have a separate mailing list to talk about non
> development stuff.
>
> i think there are a lot of people who wish to contribute to ffmpeg and
> deve
Hi J-B:
> The 2 situations are not the same at all:
> One claims to be from this community and uses the FFmpeg name,
> the other one does not make any claims.
> Please don't confuse the 2 situations.
Thanks for clarifying, I was going off of my interpretation
based on how I read through it last n
Hi,
On Thu, Dec 19, 2024 at 8:05 AM Kieran Kunhya via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> On Thu, 19 Dec 2024, 02:22 Michael Niedermayer,
> wrote:
>
> > Kieran reports this to the CC
> > and jb and ronald vote for a third ban of Nicolas,
> > ronald states that he would not have vote
Hello,
On Thu, 19 Dec 2024, at 04:40, Marth64 wrote:
> Statement #1 (NAB 2023)
>
> * Trademarked FFmpeg branding was used by a different organization
> without clear authorization.
Incorrect: FFmpeg is not trademarked in the USA.
Actually, in 2023, FFmpeg was not trademarked anywhere in the
On Thu, 19 Dec 2024, 02:22 Michael Niedermayer,
wrote:
>
> Kieran reports this to the CC
> and jb and ronald vote for a third ban of Nicolas,
> ronald states that he would not have voted for a ban if Nicolas apologized.
>
Hi Michael,
If the CC has voted to ban someone, why has it not happened?
On Thu, 19 Dec 2024 03:22:46 +0100, Michael Niedermayer wrote:
i think we need to have a separate mailing list to talk about non
development stuff.
i think there are a lot of people who wish to contribute to ffmpeg and
develop on ffmpeg but they dont care about booths or which dev said
what to wh
PS - I am analyzing this as if I was an outsider.
I hold no grudges or negative feelings of anyone here,
I am thankful for being welcomed into this community.
My general philosophy is simple:
We can do better than this.
___
ffmpeg-devel mailing list
ffm
Hi Michael,
> 2. and the most recent case
Continuing where I left off.
Let us analyze the s337m situation.
* Contributor shares significant work, as an RFC, in good faith
* A back and forth exchange happens with technical feedback and history
* Then, two senior contributors exchange inflammatory
Hi Michael,
> can you maybe provide a few more details so I and people know better
> how you would handle concrete examples, here are some:
Yes, sure.
Let us start with the booths.
Unpacking this one based on information provided above and what I
found in archives,
Statement #1 (NAB 2023)
> 1a. Prior context:
> For a long time FFmpeg booths where organized by various FFmpeg developers
> like Thilo but also others. They where always announced publically, they
> surely had a touch of hobbyists and a "non professional" community
>
> On NAB 2023 theres a booth paid by VideoLabs, with Vi
Hi Marth64
On Thu, Dec 05, 2024 at 12:39:49PM -0600, Marth64 wrote:
> I volunteer. I have no revolutionary agenda or financial skin in this game,
> and my current career does not intersect with A/V. I have been generally
> reading the mailing list since March 2023. I can provide the following
> se
Hi all,
the vote has been started. If you are in the GA (the
tools/general_assembly.pl script lists your name), you should have
received an email by now. If you did not, complain in this thread.
--
Anton Khirnov
___
ffmpeg-devel mailing list
ffmpeg-deve
Hi all,
this is a reminder that the CC election starts tomorrow morning (CET),
with the following candidates:
* Vittorio Giovara
* James Almer
* Marth64
* Anton Khirnov
* compn
* Jean-Baptiste Kempf
* Rémi Denis-Courmont
Cheers,
--
Anton Khirnov
___
ffm
Le sunnuntaina 8. joulukuuta 2024, 18.46.18 EET Anton Khirnov a écrit :
> Hi all,
> we currently have 5 candidates for CC:
> - Vittorio Giovara
> - James Almer
> - Marth64
> - Anton Khirnov
> - compn
>
> A the number of candidates equals the number of CC members, there is no
> point in holding a v
Hello,
I volunteer for CC
jbk
On Sun, 8 Dec 2024, at 17:46, Anton Khirnov wrote:
> Hi all,
> we currently have 5 candidates for CC:
> - Vittorio Giovara
> - James Almer
> - Marth64
> - Anton Khirnov
> - compn
>
> A the number of candidates equals the number of CC members, there is no
> point in
Hi all,
we currently have 5 candidates for CC:
- Vittorio Giovara
- James Almer
- Marth64
- Anton Khirnov
- compn
A the number of candidates equals the number of CC members, there is no
point in holding a vote. I therefore propose to wait a week. If any new
candidates appear in that time, we hold
On Thu, 28 Nov 2024 15:32:52 +0100, Anton Khirnov wrote:
> If you would
> like to be a CC member, please say so in a reply to this email.
>
> Cheers,
I volunteer for the CC.
My goal is to moderate and reject all personal discussion on the
mailinglist. Before it reaches the list. But also to enc
Hi all,
we only have 4 volunteers for the CC so far, so need at least one more
person. Ideally several, since elections are better when they are
competitive.
--
Anton Khirnov
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailm
I am hereby volunteering for CC.
I believe this community is deeply sick and has been for a very long
time. I also believe an active CC can make important steps towards
fixing that. If elected, I will advocate for the following:
1) Swift and determined action against uncivil behaviour,
no matte
I volunteer. I have no revolutionary agenda or financial skin in this game,
and my current career does not intersect with A/V. I have been generally
reading the mailing list since March 2023. I can provide the following
services,
1) Being an effective de-escalator and diplomat. There are bursts of
On 11/28/2024 11:32 AM, Anton Khirnov wrote:
Hi all,
the current Community Committee (CC) was elected on 2023-12-05 and its
mandate lasts for one year, so we should hold a new election soon. If
there are no unforeseen circumstances, I would like to start the vote on
Monday 2024-12-09.
As a remin
On Thu, Nov 28, 2024 at 9:33 AM Anton Khirnov wrote:
> Hi all,
> the current Community Committee (CC) was elected on 2023-12-05 and its
> mandate lasts for one year, so we should hold a new election soon. If
> there are no unforeseen circumstances, I would like to start the vote on
> Monday 2024-
39 matches
Mail list logo
