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] doc: Add infra.txt
Date: Sat, 24 Feb 2024 15:04:59 +0100
Message-ID: <20240224140459.GK6420@pb2> (raw)
In-Reply-To: <GV1P250MB07375CED210EA8BE104336C88F562@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>


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

On Thu, Feb 22, 2024 at 10:05:36PM +0100, Andreas Rheinhardt wrote:
> Michael Niedermayer:
> > ---
> >  doc/infra.txt | 99 +++++++++++++++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 99 insertions(+)
> >  create mode 100644 doc/infra.txt
> > 
> > diff --git a/doc/infra.txt b/doc/infra.txt
> > new file mode 100644
> > index 0000000000..5947a2c715
> > --- /dev/null
> > +++ b/doc/infra.txt
> > @@ -0,0 +1,99 @@
> > +FFmpeg Infrastructure:
> > +======================
> > +
> > +
> > +
> > +
> > +Servers:
> > +~~~~~~~~
> > +
> > +
> > +Main Server:
> > +------------
> > +Our Main server is hosted at telepoint.bg
> > +for more details see: https://www.ffmpeg.org/#thanks_sponsor_0001
> > +Nothing runs on our main server directly, instead several VMs run on it.
> > +
> > +
> > +ffmpeg.org VM:
> > +--------------
> > +Web, mail, and public facing git, also website git
> > +
> > +
> > +fftrac VM:
> > +----------
> > +trac.ffmpeg.org         Issue tracking
> > +
> > +
> > +ffaux VM:
> > +---------
> > +patchwork.ffmpeg.org    Patch tracking
> > +vote.ffmpeg.org         Condorcet voting
> > +
> > +
> > +fate:
> > +-----
> > +fate.ffmpeg.org         FFmpeg automated testing environment
> > +
> > +
> > +All servers currently run ubuntu
> > +
> > +
> > +
> > +Cronjobs:
> > +~~~~~~~~~
> > +Part of the docs is in the main ffmpeg repository as texi files, this part is build by a cronjob. So is the
> > +doxygen stuff as well as the FFmpeg git snapshot.
> > +These 3 scripts are under the ffcron user
> > +
> > +
> > +
> > +Git:
> > +~~~~
> > +Public facing git is provided by our infra, (https://git.ffmpeg.org/gitweb)
> > +main developer ffmpeg git repository for historic reasons is provided by (git@source.ffmpeg.org:ffmpeg)
> > +Other developer git repositories are provided via git@git.ffmpeg.org:<NAME_OF_REPOSITORY>
> > +git mirrors are available on https://github.com/FFmpeg
> > +(there are some exceptions where primary repositories are on github or elsewhere instead of the mirrors)
> > +
> > +Github mirrors are redundantly synced by multiple people
> > +
> > +You need a new git repository related to FFmpeg ? contact root at ffmpeg.org
> > +
> > +
> > +Fate:
> > +~~~~~
> > +fatesamples are provided via rsync. Every FFmpeg developer who has a shell account in ffmepg.org
> 
> ffmpeg.org
> 
> > +should be in the samples group and be able to upload samples.
> > +See https://www.ffmpeg.org/fate.html#Uploading-new-samples-to-the-fate-suite
> > +
> > +
> > +
> > +Accounts:
> > +~~~~~~~~~
> > +You need an account for some FFmpeg work? Send mail to root at ffmpeg.org
> > +
> > +
> > +
> > +VMs:
> > +~~~~
> > +You need a VM, docker container for FFmpeg? contact root at ffmpeg.org
> > +(for docker, CC Andriy)
> > +
> > +
> > +
> > +IRC:
> > +~~~~
> > +irc channels are at https://libera.chat/
> > +irc channel archieves are at https://libera.irclog.whitequark.org
> 
> archives
> 
> > +
> > +
> > +
> > +Currently open positions:
> > +~~~~~~~~~~~~~~~~~~~~~~~~~
> > +volunteer postfix / mailman expert.
> > +    You will need to do a mailman2 -> 3 update, old archieve links must continue to work
> 
> archive
> 
> > +    Some evaluation and improvments of DMARC/DKIM/... handling
> 
> improvements
> 
> > +    general long term maintaince of the mailman lists
> 
> maintenance

will apply with fixes and without the "open positions" because that
seems not to fit in the ffmpeg-git that well.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Does the universe only have a finite lifespan? No, its going to go on
forever, its just that you wont like living in it. -- Hiranya Peiri

[-- 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:[~2024-02-24 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 20:54 Michael Niedermayer
2024-02-22 21:05 ` Andreas Rheinhardt
2024-02-24 14:04   ` Michael Niedermayer [this message]
2024-02-24 15:56 ` Ronald S. Bultje
2024-02-24 18:28   ` Michael Niedermayer
2024-02-24 19:00     ` Ronald S. Bultje
2024-02-29 15:27 ` [FFmpeg-devel] [ infra] Does main server hang? Zhao Zhili
2024-02-29 15:57   ` J. Dekker
     [not found]   ` <457023F8-2E1E-4695-9C2D-B41000CC2D9B@cosmin.at>
2024-02-29 18:25     ` Cosmin Stejerean via ffmpeg-devel
2024-03-01  0:53       ` 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=20240224140459.GK6420@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