Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Dawid Kozinski/Multimedia \(PLT\) /SRPOL/Staff Engineer/Samsung Electronics" <d.kozinski@samsung.com>
To: "'FFmpeg development discussions and patches'" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in Changelog and MAINTAINERS files
Date: Wed, 14 Dec 2022 13:54:40 +0100
Message-ID: <008701d90fbb$3aeafd00$b0c0f700$@samsung.com> (raw)
In-Reply-To: <NJBmsPb--B-9@lynne.ee>

Hi,

Thank you for your prompt response.
We've removed from the MAINTAINERS file all our records and just submitted
new patches to the patchwork.

Regardless of the above, I will maintain the code related to the EVC codec
as long as I can.

Best regards 
Dawid


-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
Sent: wtorek, 13 grudnia 2022 19:42
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in
Changelog and MAINTAINERS files

Dec 13, 2022, 13:22 by d.kozinski@samsung.com:

> We made some changes in our EVC wrapper implementation and would like 
> to submit new patches to patchwork, but it's still unclear to me how 
> to deal with the MAINTAINERS file.
>
> Should I leave the following lines:
> +  libxevd.c                             Dawid Kozinski
> +  libxeve.c,                            Dawid Kozinski
> +  evc.c, evc.h                        Dawid Kozinski
> +  evcdec.c                             Dawid Kozinski
> +  evc_parser.c                      Dawid Kozinski
>
> or should I remove them?
>
> We are expecting a clear and consistent standpoint on this matter.
>

Get rid of them. Michael has made it clear anyone on the list must have
commit rights. I'm not for blocking anyone from having commit rights, but
you've made zero contributions to the project so far,

I hope it will change soon 

 and maintaining requires some level of dedication.

If you want someone to blame for this, blame Michael. He silently changed to
whom he gives out commit rights, without informing anyone, and without even
joining any discussions when this question is brought up.
_______________________________________________
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".

_______________________________________________
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".

  reply	other threads:[~2022-12-14 12:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221024074233eucas1p125b43125cce202641bf48d0f174a39a1@eucas1p1.samsung.com>
2022-10-24  7:42 ` Dawid Kozinski
2022-10-24 15:56   ` Lynne
2022-10-24 16:29     ` James Almer
2022-10-25 11:17       ` Lynne
2022-10-27 16:45         ` Michael Niedermayer
2022-10-28 21:08           ` Lynne
2022-12-13 12:22             ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-13 13:33               ` Ronald S. Bultje
2022-12-14 13:02                 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-14 21:36                 ` Michael Niedermayer
2022-12-15  9:14                   ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-15 19:22                     ` Michael Niedermayer
2023-01-27 12:03                       ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-01-29  9:57                         ` Michael Niedermayer
2023-01-29 23:18                           ` Lynne
2023-02-06  8:46                             ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-13  9:28                             ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-13 17:32                               ` Lynne
2023-02-14 12:10                                 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-14 18:00                                   ` Lynne
2023-02-15  8:50                                     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-03-06 10:46                                     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-03-18 17:53                                       ` Lynne
2023-03-21  9:22                                         ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-14 18:03                                   ` Kieran Kunhya
2023-02-15  8:49                                     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-15 13:05                                       ` Kieran Kunhya
2023-02-16  8:49                                         ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-01-02 13:07                   ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-13 18:42               ` Lynne
2022-12-14 12:54                 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics [this message]
2022-12-14 21:45                 ` Michael Niedermayer
2022-12-15  1:11                   ` Lynne
2022-12-15 19:15                     ` Michael Niedermayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='008701d90fbb$3aeafd00$b0c0f700$@samsung.com' \
    --to=d.kozinski@samsung.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git