Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] GSoC 2025
Date: Fri, 31 Jan 2025 01:24:47 +0100
Message-ID: <CABLWnS97T2WbARxM2bcrHCzYtVKKT6oF+Ws-gKxY=hU-JKH4_Q@mail.gmail.com> (raw)
In-Reply-To: <CAO4LPj-pG9U6sXMkBc238k-p8hz5hywTy2kpcA4dQa=9n-Lnaw@mail.gmail.com>

On Thu, Jan 30, 2025 at 10:20 PM Koushik Dutta <koushd@gmail.com> wrote:

> Why gitlab and not GitHub? If the intent is on making contribution from new
> developers easier, I think the workflow should be where the majority of
> developers are actively participating.
>

Because Github is hosted on servers in the US, which are easy to seize for
whatever reason, and controlled by a for-profit corporation, with a past of
unfriendliness towards open source. While lately that company has been
opening up more towards FOSS, there is no guarantee that things won't
change again.
-- 
Vittorio
_______________________________________________
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".

  parent reply	other threads:[~2025-01-31  0:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28  2:21 Michael Niedermayer
2025-01-29 15:51 ` Yigithan Yigit
2025-01-29 19:01   ` Michael Niedermayer
2025-01-29 19:31     ` Kieran Kunhya via ffmpeg-devel
2025-01-29 20:01       ` Ronald S. Bultje
2025-01-30  6:36         ` Vittorio Giovara
2025-01-30 10:21           ` Sean McGovern
2025-01-30 18:40       ` Michael Niedermayer
2025-01-30 21:20       ` Koushik Dutta
2025-01-30 14:53         ` compn
2025-01-31  5:01           ` Soft Works
2025-01-31  0:24         ` Vittorio Giovara [this message]
2025-01-31 12:51         ` James Almer

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='CABLWnS97T2WbARxM2bcrHCzYtVKKT6oF+Ws-gKxY=hU-JKH4_Q@mail.gmail.com' \
    --to=vittorio.giovara@gmail.com \
    --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