| Message ID | 20170201000941.000012d2@mi.rr.com |
|---|---|
| State | New |
| Headers | show |
On Wed, 1 Feb 2017 00:09:41 -0500 compn <tempn@mi.rr.com> wrote: > 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 Who maintains this piece of infrastructure at all?
On Wed, 1 Feb 2017 07:34:11 +0100 wm4 <nfxjfg@googlemail.com> wrote: > On Wed, 1 Feb 2017 00:09:41 -0500 > compn <tempn@mi.rr.com> wrote: > > > 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 > > Who maintains this piece of infrastructure at all? videolan maintained the server, carl does most of the moving files to our samples repo and bug trac. but heres the new news from #videolan: [05:41] <thresh> Compn, http://streams.videolan.org/upload/ should work more or less ^ this is currently where we should send users to upload files. an http uploader (not sure about resume support...). [05:49] <thresh> Compn, there will be no ftp access to streams, ever [05:50] <thresh> Compn, we're following the Great Leadership of kernel.org ^^ this is the news on the ftp that we currently have in our docs. so we should change all of our docs over to the http uploader. also i suggest we ask for a backup ftp server from another host (by applying this or similar patch), for those people who prefer to use ftp. -compn
2017-02-01 14:10 GMT+01:00 compn <tempn@mi.rr.com>: > [05:41] <thresh> Compn, http://streams.videolan.org/upload/ > should work more or less > > ^ this is currently where we should send users to upload files. > an http uploader (not sure about resume support...). > > [05:49] <thresh> Compn, there will be no ftp access to streams, ever Apart from the fact that this contradicts a promise that has been made: How are we supposed to access the samples? Carl Eugen
On Wed, 1 Feb 2017 17:45:16 +0100, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote: > 2017-02-01 14:10 GMT+01:00 compn <tempn@mi.rr.com>: > > > [05:41] <thresh> Compn, http://streams.videolan.org/upload/ > > should work more or less > > > > ^ this is currently where we should send users to upload files. > > an http uploader (not sure about resume support...). > > > > [05:49] <thresh> Compn, there will be no ftp access to streams, ever > > Apart from the fact that this contradicts a promise that has been > made: yes i noticed that too. oh well. i've made the changes to mplayer DOCS, although it would be nice to also have a backup ftp server for people using old docs and the old ftp url. (todo: update urls in the homepage repo). > How are we supposed to access the samples? files uploaded with the vlc http upload http://streams.videolan.org/upload/ are immediately accessable publically here, with no login. http://streams.videolan.org/ffmpeg/incoming/ i just tested and all seems to be working. aside from having to put in a vlc version for ffmpeg and mplayer. has anyone reviewed the files in http://streams.videolan.org/ffmpeg/ ? go to http://streams.videolan.org/ and there is a dir for mplayer and mplayer/incoming as well http://streams.videolan.org/MPlayer/ http://streams.videolan.org/MPlayer/incoming/ -compn
2017-02-01 19:36 GMT+01:00 Compn <tempn@mi.rr.com>: >> How are we supposed to access the samples? > > files uploaded with the vlc http upload > http://streams.videolan.org/upload/ > > are immediately accessable publically here, with no login. > http://streams.videolan.org/ffmpeg/incoming/ Meaning our promise to our users that we can keep the samples to ourselves is broken;-( That's apart from the fact that from my pov the whole idea was of course that we are able to access the vlc samples to get more bug reports... This is fantastic disappointment! Carl Eugen
On Thu, 2 Feb 2017 09:30:30 +0100, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote: > 2017-02-01 19:36 GMT+01:00 Compn <tempn@mi.rr.com>: > > >> How are we supposed to access the samples? > > > > files uploaded with the vlc http upload > > http://streams.videolan.org/upload/ > > > > are immediately accessable publically here, with no login. > > http://streams.videolan.org/ffmpeg/incoming/ > > Meaning our promise to our users that we can keep the > samples to ourselves is broken;-( thats what we need a private ftp for, private samples. > That's apart from the fact that from my pov the whole > idea was of course that we are able to access the vlc > samples to get more bug reports... the vlc samples are http://streams.videolan.org/ i have just now asked about getting a login for the vlc incoming. -compn
diff --git a/src/index b/src/index index c203676..cf45f4f 100644 --- a/src/index +++ b/src/index @@ -37,6 +37,15 @@ News </h1> + <h3 id="incomingftp">February 01, 2017, Backup ftp server needed.</h3> + <p> + 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. + </p> + <p> + 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. + </p> <h3 id="gsoc2016finalreport">October 30th, 2016, Results: Summer Of Code 2016.</h3> <p> 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.