From patchwork Wed Feb 1 05:09:41 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: compn X-Patchwork-Id: 2395 Delivered-To: ffmpegpatchwork@gmail.com Received: by 10.103.89.21 with SMTP id n21csp2275173vsb; Tue, 31 Jan 2017 21:09:54 -0800 (PST) X-Received: by 10.28.109.70 with SMTP id i67mr20302109wmc.102.1485925794037; Tue, 31 Jan 2017 21:09:54 -0800 (PST) Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org. [79.124.17.100]) by mx.google.com with ESMTP id o64si19841807wmi.143.2017.01.31.21.09.53; Tue, 31 Jan 2017 21:09:54 -0800 (PST) Received-SPF: pass (google.com: domain of ffmpeg-devel-bounces@ffmpeg.org designates 79.124.17.100 as permitted sender) client-ip=79.124.17.100; Authentication-Results: mx.google.com; spf=pass (google.com: domain of ffmpeg-devel-bounces@ffmpeg.org designates 79.124.17.100 as permitted sender) smtp.mailfrom=ffmpeg-devel-bounces@ffmpeg.org Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 04BE2680D2C; Wed, 1 Feb 2017 07:09:48 +0200 (EET) X-Original-To: ffmpeg-devel@ffmpeg.org Delivered-To: ffmpeg-devel@ffmpeg.org Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id A4869680BC3 for ; Wed, 1 Feb 2017 07:09:40 +0200 (EET) Received: from [97.70.209.181] ([97.70.209.181:4934] helo=localhost) by cdptpa-omsmta01 (envelope-from ) (ecelerity 3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 16/E3-05048-69D61985; Wed, 01 Feb 2017 05:09:42 +0000 Date: Wed, 1 Feb 2017 00:09:41 -0500 From: compn To: ffmpeg-devel@ffmpeg.org Message-ID: <20170201000941.000012d2@mi.rr.com> X-Mailer: Claws Mail 3.9.2-94-gc6f41d (GTK+ 2.16.6; i586-pc-mingw32msvc) MIME-Version: 1.0 X-RR-Connecting-IP: 107.14.168.6:25 Subject: [FFmpeg-devel] [PATCH] [rfc] web/index request incoming ftp server X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" not sure if this is the right way to do it, maybe its easier to ask for someone on twitter? it would be nice to have a backup just in case videolan has problems. then we dont have to ask users to use datafilehost heh. i dont want to burden ffmpeg admins to maintain some ftp either. carl, what do you think? ideas welcome. -compn diff --git a/src/index b/src/index index c203676..cf45f4f 100644 --- a/src/index +++ b/src/index @@ -37,6 +37,15 @@ News +

February 01, 2017, Backup ftp server needed.

+

+ We are in need of a ftp backup for users to upload sample files to us. + Our current ftp, hosted by videolan, is still being worked on, with no ETA for a fix. +

+

+ What we need: public ftp with anonymous upload only, and authenticated read/downloads for developers. + space a few TB, speed 1mb/s+. Nothing fancy. Please send mail to projects@ffmpeg.org if you want to help. +

October 30th, 2016, Results: Summer Of Code 2016.

This has been a long time coming but we wanted to give a proper closure to our participation in this run of the program and it takes time. Sometimes it's just to get the final report for each project trimmed down, others, is finalizing whatever was still in progress when the program finished: final patches need to be merged, TODO lists stabilized, future plans agreed; you name it.