Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add a separate list for those with push access
Date: Fri, 16 Dec 2022 23:05:03 +0100
Message-ID: <20221216220503.GW3806951@pb2> (raw)
In-Reply-To: <NJN6BmE--3-9@lynne.ee>


[-- Attachment #1.1: Type: text/plain, Size: 3400 bytes --]

On Fri, Dec 16, 2022 at 12:26:58AM +0100, Lynne wrote:
> Dec 15, 2022, 20:34 by michael@niedermayer.cc:
> 
> > On Thu, Dec 15, 2022 at 02:13:49AM +0100, Lynne wrote:
> >
> >> This list is incomplete, and just contains those I could see
> >> while looking at the recent git log. If it looks like I've forgotten you, I definitely haven't!
> >> We may complete the list at a later date.
> >>
> >> This makes it such that those who add themselves to MAINTAINERS do not
> >> get push access by default, but rather, they have to request it
> >> explicitly in a different commit. This used to be the situation
> >> before it was changed at the start of this year and is pretty much what
> >> everyone expects.
> >>
> >> Patch attached.
> >>
> >> MAINTAINERS |   15 +++++++++++++++
> >>  1 file changed, 15 insertions(+)
> >> 6a083061d75f6655771bde377f96aadad19b21c6  0001-MAINTAINERS-add-a-separate-list-for-those-with-push-.patch
> >> From 5c353412a25fd46c5077e5cf92ddfd6532eb46cb Mon Sep 17 00:00:00 2001
> >> From: Lynne <dev@lynne.ee>
> >> Date: Thu, 15 Dec 2022 02:05:00 +0100
> >> Subject: [PATCH] MAINTAINERS: add a separate list for those with push access
> >>
> >> This list is incomplete, and just contains those I could remember
> >> while looking at the recent git log.
> >> We may complete the list at a later date.
> >>
> >> This makes it such that those who add themselves to MAINTAINERS do not
> >> get push access by default, but rather, they have to request it
> >> explicitly in a different commit.
> >>
> >> This used to be the situation
> >> before it was changed at the start of this year.
> >>
> >
> > I remember no such change.
> > What i do remember is really long ago trying to push people toward pushing in
> > their own repository and sending pull requests similar to the kernel. But this
> > was not popular so i droped the idea.
> >
> > Whereever code is maintained teh maintainer should have write access to that
> > place other things become inconvenient quickly.
> >
> > maintainers who cannot change the code they maintain should stay an exception
> >
> 
> This is exactly what changed. Before, maintainers who didn't get push
> access was the norm, not the standard.
> 
> Regardless, if you agree with the patch, I see no reason to continue discussing this.

I see the need to reach some approximate consensus on the past because making
decissions should not be based on misremembering things.

I see that in 2015 the GSOC students who got added to MAINTAINERs
also got write access in 2015.
and IIRC x264 had a similar policy at the time where students would be treated like
any other developer and have equal access.

I use this as an example because several of these students came and left after
their project and still got write access.

Maybe all our memories are not 100% exact after so many years but I think you misremember
if you think we had alot of maintainers who did not have the same acccess
there where some exceptions but they where few.
Also some people like the students in the example above, left they did not use their write
access so maybe people forgot they had write access

Thanks

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I do not agree with what you have to say, but I'll defend to the death your
right to say it. -- Voltaire

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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-16 22:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15  1:13 Lynne
2022-12-15 19:34 ` Michael Niedermayer
2022-12-15 23:26   ` Lynne
2022-12-16 22:05     ` Michael Niedermayer [this message]
2022-12-18  6:31       ` Lynne
2023-01-29 23:14         ` Lynne
2023-01-30  3:44           ` Leo Izen
2023-01-30  3:59             ` Gyan Doshi
2023-01-30  4:22               ` Stephen Hutchinson
2023-02-07  2:40                 ` Steven Liu
2023-01-30 16:49 ` Michael Niedermayer
2023-01-30 19:03   ` Lynne
2023-02-06 12:10     ` Lynne
2023-02-06 14:49       ` Derek Buitenhuis
2023-02-07  1:27         ` Michael Niedermayer
2023-02-07  1:20       ` 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=20221216220503.GW3806951@pb2 \
    --to=michael@niedermayer.cc \
    --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