From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] trac backups Date: Wed, 13 Sep 2023 18:38:34 +0200 Message-ID: <20230913163834.GO8640@pb2> (raw) In-Reply-To: <400dd26f-ee8f-4bea-92ac-5efcaeb77a37@betaapp.fastmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2751 bytes --] On Wed, Sep 13, 2023 at 11:05:23AM +0200, Jean-Baptiste Kempf wrote: > On Wed, 13 Sep 2023, at 01:33, Michael Niedermayer wrote: > >> Who else other than you has access to the infrastructure? > > > > all the root admins do > > but that isnt the problem, even if 100 more people had access > > the only way that was noticable it seems was if someone looked > > I disagree. The infrastructure is un-documented, and the people accessing it are un-documented. Your reply isnt really related to the statment it follows Also it maybe sounds a little accusational. I just spoted the issue and fixed it and documented the issue here in public. So i get a "thanks for fixing the backups and thanks for the transparency" no, this is open source, so i get a mildly accusational reply Not even a "Where is the list of root admins" but a "the people accessing it are un-documented" are they ? the MAINTAINERS file lists teh admins, yes ubitux removed himself from it in MAINTAINERS and still has access which i think is good in case of an emergency and also thresh has access and is not listed in MAINTAINERS (he is more a last resort emergency and less a day to day admin). send a patch for MAINTAINERS if you feel the list is not good and what do you mean by infrastructure ? its a trac issue tracker in a VM, trac backup scripts written by beastd and a 2nd backup system setup by raz for all the ffmpeg infrastructure. what is missing and what do you want ? config files ? cronjobs ? making all that public is possible, if its a good idea for security and all i dont know. May i make a blunt suggestion, anyone who doesnt take the information in this mail and start writing/documenting the infrastructure should not complain its undocumented again in the future. > > This is a big problem. this really sounds more like a populistic statement than anything with the intend to improve a real problem. i mean you know, this is not a list of questions with the intend behind to document anything, its more finger-pointing. And somehow it feels like that pointing is going my way even though i havent writen or setup either backup system but it also would be deeply unfair to point to beastd or other admins here. Everyone did their best with the time they had available. So again if people want better documentation. First step i would suggest someone should volunteer to write that documentation. And then that person should start asking specific questions. Documentation does not write itself yet. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell [-- 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".
prev parent reply other threads:[~2023-09-13 16:38 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-12 22:13 Michael Niedermayer 2023-09-12 22:32 ` Marvin Scholz 2023-09-12 23:33 ` Michael Niedermayer 2023-09-13 9:05 ` Jean-Baptiste Kempf 2023-09-13 9:52 ` Paul B Mahol 2023-09-13 16:38 ` Michael Niedermayer [this message]
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=20230913163834.GO8640@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