Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vasily <just.one.man@yandex.ru>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GitHub Integration
Date: Mon, 27 Dec 2021 18:36:12 +0300
Message-ID: <CABiDpknbfTsNoU+bfCo5Ep3vZBEsc2kQTEWS_igp4PRKYsppaw@mail.gmail.com> (raw)
In-Reply-To: <c5b7d575-1610-795e-b277-6b1bbd06be0f@zanevaniperen.com>

Not advocating for github (per this thread it's out of scope), but I think
using a self-hosted gitlab with an option to auth using github account
would help in reducing the "account overhead" at least for those who use
github.

пн, 27 дек. 2021 г., 17:59 Zane van Iperen <zane@zanevaniperen.com>:

>
>
> On 27/12/21 11:41, lance.lmwang@gmail.com wrote:
> > On Sun, Dec 26, 2021 at 04:37:54PM -0500, Ronald S. Bultje wrote:
> >> Hi,
> >>
> >> On Sun, Dec 26, 2021 at 3:21 PM Soft Works <softworkz@hotmail.com>
> wrote:
> >>
> >>> I'm not sure. My interpretation of Lance' and Steven's comments would
> >>> be that they'd prefer to stick to the ML.
> >>>
> >>
> >> No, it's not strictly related to that - they want something that is CLI
> >> accessible. Gitlab has this here:
> https://glab.readthedocs.io/en/latest/
> >> and github has this here: https://github.com/cli/cli - the next
> question is
> >> whether the gitlab/hub hosts are blocked by a firewall (no idea) and/or
> >> whether the instances are self-hosted (github: no, gitlab-videolan:
> yes).
> >
> > Yes, self-hosted is more preferable, I recall github has blocked
> devleopers
> > in some country by US trade controls. Who knows what's the rules will be
> > changed someday as it's controlled by company.
> >
>
> Something that doesn't require another account would be nice, which is why
> I like mailing lists. Although in this case a move to GitHub wouldn't
> affect me
> personally (I use it a lot) - if I didn't, I would seriously reconsider if
> the mental
> overhead of yet another account (and all the baggage that comes with it -
> passwords, MFA,
> data breaches, etc.) is worth contributing to the project.
>
> Ideally, something self-hosted like Gitea or GitLab with a federated
> approach (i.e. ForgeFed)
> would be fantastic for a case such as this. I'm not sure about GitLab, but
> I know Gitea is
> working towards this.
>
>
> _______________________________________________
> 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:[~2021-12-27 15:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 23:24 Soft Works
2021-12-23  7:35 ` Paul B Mahol
2021-12-23  8:10   ` Soft Works
2021-12-23 13:59 ` Tomas Härdin
2021-12-23 14:08   ` Soft Works
2021-12-23 14:16   ` Timo Rothenpieler
2021-12-23 20:50     ` Soft Works
2021-12-23 22:30 ` Soft Works
2021-12-25  9:31   ` Vasily
2021-12-25  9:33     ` Vasily
2021-12-25 11:12     ` Michael Niedermayer
2021-12-25 16:27       ` Soft Works
2021-12-25 16:23     ` Soft Works
2021-12-25 16:50 ` Lynne
2021-12-25 17:15   ` Soft Works
2021-12-26  0:54     ` lance.lmwang
2021-12-26  1:03       ` Steven Liu
2021-12-26 16:48         ` Lynne
2021-12-26 20:21           ` Soft Works
2021-12-26 21:37             ` Ronald S. Bultje
2021-12-26 23:10               ` Soft Works
2021-12-27  1:41               ` lance.lmwang
2021-12-27 14:59                 ` Zane van Iperen
2021-12-27 15:36                   ` Vasily [this message]
2021-12-28 21:21                   ` Niklas Haas
2021-12-28 21:57                     ` Soft Works
2022-01-02  3:28                       ` Soft Works
2022-01-02 14:04                         ` Lynne
2022-01-02 18:16                           ` Soft Works
2022-01-21  1:29                             ` Soft Works
2021-12-29 19:57               ` 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=CABiDpknbfTsNoU+bfCo5Ep3vZBEsc2kQTEWS_igp4PRKYsppaw@mail.gmail.com \
    --to=just.one.man@yandex.ru \
    --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