Closed Bug 917968 Opened 11 years ago Closed 10 years ago

Repository for Restricted Video Produced by Mozillians

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: richard, Unassigned)

References

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/121] )

We need a directory in videos-origin.mozilla.org/manage/ to act as a repository for restricted video produced by community members.  Producers uploading to this repository will be either MoCo/MoFo staff (with LDAP logins) or vouched Mozillians from mozillians.org.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Adding :peterbe... how does the authentication work on AirMo such that vouched Mozillians have a different level of access? I'm wondering if there's any way we can do something similar for videos-origin.

The obvious problem is that videos-origin isn't a real web app... it's just Apache with WebDAV. We can definitely do LDAP auth that way, but more complicated stuff is tricky. Someday I'd like to do a lot better, and have this *be* a real app, and get rid of the WebDAV system entirely. Perhaps such a system could be a part of AirMozilla? Some sort of management interface where you could upload files...


We are working on an Apache module that will do Persona-based authentication, rather than LDAP. This might be relevant here. I really don't know how well that would interact with WebDAV, but theoretically it should be fine. Using this, we would theoretically be able to provide a list of email addresses that are allowed access... the list could be built from LDAP and vouched Mozillians (or maybe just the latter) on a cron. The videos-origin / videos.mozilla.org system is already so bizarre and one-off-ish that I'm not too worried about it getting a little weirder. (which is another reason I'd love for it to become a real web app)

I'm also CC'ing William Reynolds (owner of Mozillians and this whole project, as I understand it) and gozer (who's doing the dev work on this Apache module), just so they know what's going on here.
I'm a huge fan of Ink File Picker. That would make it possible for people to upload files using drag-and-drop from their hard drive, from Google Drive, from Dropbox, etc. It could potentially cost us $99/month.

With this we could leverage the authentication of Air Mozilla and we could, on our server, securely download it in the right place on videos origin. 

What Ink File Picker does, when integrated into a site is that it gives you a URL to filepicker.io which you would then download in a background task or something. 

What we could also do, is not bother at all with videos origin and dedicate a piece of filesystem somewhere that the airmozilla webheads could write to. Then we don't have to worry about the ssh keys of transferring files between servers. 

This way, airmozilla would become a little Dropbox for every airmozilla user who can sign in.
I am severely in favor of this plan. I don't like much of anything about the current videos.mozilla.org system, and I like a lot about AirMozilla. If we can make AirMozilla even more awesome *and* get rid of something that I feel is pretty hacky / one-off-ish at the same time, that's a very good win.

I'd prefer to set you up with storage space right in AirMozilla, rather than try to shoehorn it into the current videos-origin system. If this works, we'd deprecate videos-origin as much as possible and recommend this system instead.

For that matter, if you're interested, we could set you up with S3 storage as well. That might scale better in terms of allowable disk space, and you wouldn't have to deal with the filesystem at all.



What do we need to do to make it happen? Who do we need to convince, and what resources do we need to acquire?

Obviously there's some coding time on your end, and somehow we need to license the software, and storage space on our end. Any other major pieces?

Is this bug suitable for doing all that (maybe with dependent bugs for each piece), or do we want to WONTFIX this and start over?
Jake, 

Ink File Picker supports upload straight to S3. I've never used it.
https://developers.inkfilepicker.com/docs/web/#custom-s3
https://developers.inkfilepicker.com/page/s3/

What we need the file for ultimately is to send a URL to Vid.ly so they can turn it into a watchable file. 

In Django I think we'll make a table that simply maps a user to a URL and an event (or something) that is initially null until the user attaches it. The user could then click on "Suggest and event" and a drop-down appears that shows the files they have successfully uploaded.
I whole-heartedly agree with Jake and Peter.  Having a repository to which we can directly upload video from within an AirMozilla page would be a HUGE win.  The expandability of S3 storage would also eliminate any future pain if we succeed in getting a lot of community members to start generating content.   Right now having a way to upload video is a big stumbling block in that effort.
...and it would also help eliminate problems like bug #926590
As a consideration for a restricted video repository, we are building a "curated group" features on mozillians.org. This will allow any vouched Mozillian to create a curated group and then manage the members of the group. The Mozillians API can be used with this to look up if user XYZ is a member of a curated group.

In effect, these curated group could be used for authorization that determines which restricted videos someone can see.

See bug 936569 for details.
See Also: → 936569
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/121]
The new workflows on Air Mozilla for both pre-recorded video and live events now solve this problem.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.