From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] GSoC 2025
Date: Fri, 31 Jan 2025 09:51:57 -0300
Message-ID: <8254fe54-e4dd-4531-a91d-c5714eae5c84@gmail.com> (raw)
In-Reply-To: <CAO4LPj-pG9U6sXMkBc238k-p8hz5hywTy2kpcA4dQa=9n-Lnaw@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 574 bytes --]
On 1/30/2025 6:20 PM, Koushik Dutta 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.
The point is having full control of it, and not host the main repo in
either Github's or Gitlab's servers. Several devs have good experiences
with Videolan's Gitlab instance, so us setting up our own is a no brainer.
I also would be fine with Forgejo, but which one is ultimately chosen
will most likely depend on a vote.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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:[~2025-01-31 12:52 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
2025-01-31 12:51 ` James Almer [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=8254fe54-e4dd-4531-a91d-c5714eae5c84@gmail.com \
--to=jamrial@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