Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [RFC] the role of maintainers
Date: Fri, 24 Mar 2023 15:29:18 +0100
Message-ID: <167966815810.27013.14421474053930764026@lain.khirnov.net> (raw)

Hi,
during the recent discussion on git repo push rights vs maintainership
there was some disagreement on what does (or should) it mean to be a
maintainer of a piece of code. It seems that different people have very
different ideas on this, so I think it would be good to reach some kind
of consensus.

I propose that people submit their opinions on what the rights and
responsibilities of a maintainer should be to this thread, so their
relative merits can be discussed.
The we have a GA vote, and write down the result in the dev rules.

To start, some of the specific questions that I believe should be
considered are:
1. Should the concept of maintainership exist at all? Does it serve a
   useful purpose? If so, what is it?
(further questions assume that the answer to 1. is yes)
2. Should maintainers automatically get git push access?
3. Should maintainers be allowed to push to their code without sending
   patches for review?
4. How much control do maintainers get over their code. Can they
   override other developers' opinions or is the role merely advisory?
5. Do maintainers have duties? E.g. are they required to fix bugs in
   their code, perform reviews, etc. Do they lose maintainership if they
   fail to perform those?

Cheers,
-- 
Anton Khirnov
_______________________________________________
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:[~2023-03-24 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 14:29 Anton Khirnov [this message]
2023-03-24 15:14 ` Paul B Mahol
2023-03-25  0:14 ` Michael Niedermayer
2023-03-28 11:37   ` Anton Khirnov

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=167966815810.27013.14421474053930764026@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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