taskReproducible paper template - Tasks: task #15620, Creating a series of short videos...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #15620: Creating a series of short videos explaining all angles to Maneage

Submitted by:  Mohammadreza Khellat <mkhellat>
Submitted on:  Thu 30 Apr 2020 10:01:54 AM UTC  
 
Should Start On:  Thu 30 Apr 2020 12:00:00 AM UTC Should be Finished on:  Tue 30 Jun 2020 12:00:00 AM UTC
Category:  None Priority:  5 - Normal
Status:  None Privacy:  Public
Percent Complete:  0% Assigned to:  None
Open/Closed:  Open Effort:  0.00

( Jump to the original submission)

Thu 21 May 2020 11:22:34 PM UTC, comment #7: 

I put a link to the peertube.live instance of the video
at https://savannah.nongnu.org/task/index.php?15654 , since
that seemed more appropriate for specific web pages/URLs.

I agree that one concern with git-LFS would be
that it apparently needs a third party server. Between
git-LFS and peertube, I think I would tend to go for peertube
as more decentralised - by default, people who view the
video in the web interface do it peer-to-peer by torrent; those
who select "..." (next to the like/dislike/share icons in the
main interface below the video) have the choice of downloading
by torrent or directly, in any of various compressed formats
that they find convenient. This sounds technically more
reasonable than git-LFS for human-viewable videos -
which are not like observational data files.

As for deleting a big file from a git repository, it seems to
me that unless you manage to make the file inaccessible in
the git history by something unrecommended like
git reset --hard, and you make sure that nobody accidentally
re-pushes that part of the history tree up to the public
repository(ies), then it's quite hard to convince git prune
and git gc to really get rid of what you think is useless
garbage. I tried this once on in a temporary directory with
a local git repository and was unable to get the .git/
directory down to a small size after trying to delete all
history of a fake big file that I committed and then tried
to "hide" completely. Git is about the worst thing to use
by any group/organisation that is uncomfortable about transparency;
it's just not designed for censorship - unless you remove
the .git/ directory hierarchy itself, losing your whole
git history. And this includes "tidying" by removing big
useless stuff as "censorship". That's my impression, in any
case; it could be that my git skills were still too elementary.

Boud Roukema <boud>
Project Member
Thu 21 May 2020 12:15:44 AM UTC, comment #6: 

Thanks for mentioning Git LFS! I also confronted it while learning the LSST pipeline.

The problem with it is that it requires a third repository for the large files.

In our context, if we had such a repository, we wouldn't need Git any more ;-)! In our usage, Git is effectively just to allow easy copying/pasting of the files, to move them around. As I mentioned before, we won't be editing/changing the videos, once they go in the repository, the only change we may(!) do is to delete them.

If we later generate videos automatically (for example through some fancy feature like asciinema, then we'll keep the source of that and won't archive any resulting video, since we can always reproduce it ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Thu 21 May 2020 12:02:01 AM UTC, comment #5: 

You guys know about Git much more than me. But let me point out one thing about large data sets in Git: Git LFS (Git Large File Storage, https://git-lfs.github.com/). I heard it when I had to deal with datasets for the LSST (https://pipelines.lsst.io/install/git-lfs.html). I hope it can be of help, although I did not investigate. Maybe it is very complicated or not useful in our scenario. Let me know what do you think ;-)

Raul Infante-Sainz <infantesainz>
Project Member
Wed 20 May 2020 01:42:55 PM UTC, comment #4: 

Just one small addition to my first paragraph before: as long as we don't change a file, it is propagated in the later commits as a link (not a full copy). So since we won't be changing/editing the videos any more, effectively the size of the Git repo will be the size of the sum of the videos.

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Wed 20 May 2020 01:41:14 PM UTC, comment #3: 

You are right about Git, it doesn't store diffs, it just keeps copies. But the thing with binary files (like videos) is that they aren't edited. For example I don't see why we should edit this uploaded presentation any more. In the future, if Maneage changes sufficiently enough to warrant many changes, we'll just make a new video. The thing is that these videos (at least for now) aren't automatically generated files, they are manually recorded. So in effect, Git won't be used to track the history of the files, it will just be a way to keep a backup of them.

About the license of the YouTube upload, I did choose "CC BY" (Attribution, which was the only option along-side YouTube's own lisence). But you are right, as I look around that page on YouTube, I can't find it mentioned anywhere!

In the Git repo, I just [pushed http://git.maneage.org/videos.git/commit/?id=d10b58d9e] a copy of CC BY-SA 4.0 in the project that can be assumed for all the files in this project.

We will not put a single link to the YouTube pages on 'manage.org', this is only for those who search videos in YouTube. Hopefully by the end of task #15654, we'll be able to play the videos directly in 'maneage.org', and we'll have all the necessary information there.

If we ever do need to link to the YouTube videos, we'll do it through Invidious, for example for this talk, the relevant link is this: https://invidio.us/watch?v=AtinDGUnhVw

After submitting the paper, I'll also record the slides in English, and maybe you guys (Raul and Boud) can do a Spanish, French/Polish version if you like ;-). The slides are ofcourse also reproducible and maintained on our Git repo, so you can edit them if you like or propose changes/corrections, and most importantly add your name when you want to present ;-).

Mohammad Akhlaghi <makhlaghi>
Project Administrator
Wed 20 May 2020 10:59:24 AM UTC, comment #2: 

> I created a videos.git project under git.maneage.org as a permanent place to keep these videos. Hopefully we'll add more as time goes by and through Git, we can easily have a distributed archival system. Since its just the slides, its not big (~170Mb).


That still makes it huge for git. If people make 100 minor edits, then that risks being 100 Gb of storage. AFAIK git does not just store differences, even though that's the impression it gives to users.

> * I defined a channel on YouTube to also host the videos. This first talk is already uploaded there.


What's the video's licence? CC-BY? CC-BY-ND? I couldn't find a licence.

To redistribute the video in the free world ;), using a better system for distributing videos than git, a proper licence will be needed.

Boud Roukema <boud>
Project Member
Wed 20 May 2020 12:58:08 AM UTC, comment #1: 

Today we had an introductory talk on Maneage for around 15 researchers in Iran (so the talk was in Persian). But since one of the participants recorded it, it is now our first recorded video on Maneage :-). So I took these steps:

  • I created a videos.git project under git.maneage.org as a permanent place to keep these videos. Hopefully we'll add more as time goes by and through Git, we can easily have a distributed archival system. Since its just the slides, its not big (~170Mb).
  • I defined task #15654, so hopefully when Pedram has time, he can embed the videos in an dedicated HTML page.
  • I defined a channel on YouTube to also host the videos. This first talk is already uploaded there. This is just to help people that search for talks in Youtube. In our own page, we'll always link to our own copy of the video.
Mohammad Akhlaghi <makhlaghi>
Project Administrator
Thu 30 Apr 2020 10:01:54 AM UTC, original submission:  

I think it could be a good idea to prepare a series of short videos in which the following are discussed and explained regarding Maneage

  • Problem statement and the objective,
  • the main strategy and scope,
  • the role Git plays in the strategy,
  • the design and components, and
  • each component

It could be like a live version of the article with a nice context and demonstration.

This video should be hosted on the main webpage and even a youtube channel with cross references in the git page, the main page, and the youtube channel to each other.

I have recently been watching videos in this youtube channel called Web of Stories and I liked the way they have broken down very long interviews...
Even for someone like me whose working days are very unpredictable, those videos were easy to follow and watch whenever I found the time.

Mohammadreza Khellat <mkhellat>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by infantesainz (Posted a comment)
  • -email is unavailable- added by boud (Posted a comment)
  • -email is unavailable- added by makhlaghi (Posted a comment)
  • -email is unavailable- added by mkhellat (Submitted the item)
  • -email is unavailable- added by mkhellat
  • -email is unavailable- added by mkhellat
  • -email is unavailable- added by mkhellat
  • -email is unavailable- added by mkhellat
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-04-30 mkhellat Carbon-Copy- => Added boud
        Carbon-Copy- => Added infantesainz
        Carbon-Copy- => Added makhlaghi
        Carbon-Copy- => Added pedram

    Back to the top


    Powered by Savane 3.5