Add London Ruby User Group (LRUG)

[h-lame]

The videos.yml file is generated by the lrug site and hosted at https://lrug.org/rubyevents-video-playlist.yml so we've just copied it into the rubyevents repo for this PR. Currently fixed at 2020 onwards as while we have meetings on the site going back to 2006, all the links to recordings now go to a private vimeo account due to the long-time venue / host going into administration.

We would be interested in exploring something that allows us to ping ruby events when a change is published to our video playlist yml file to automatically update / enter events.

We have sponsor data, but haven't added it, no have we added CFP or Schedule info as these seem (understandably) tailored to one-off events like conferences, less so to meet-ups. For example, our CFP never ends.

[h-lame]

Oh, our to_yaml call that outputs the rubyevents_video_playlist.yml is producing yaml that falls afoul of the prettier rules. I'll fix for this PR, but would be interested in knowing if we can change the rules, or change our output (although formatting for to_yaml seems limited).

[h-lame]

I also removed the unused .png assets, since we only really use the .webp ones.

Oops! My bad, I knew we only wanted the webp ones, but then just yolo committed the png ones when I saw them sitting uncommitted in my working folder 🤦 - the dangers of doing this work in two sittings about a week apart.

I think your published_at timestamp is our announced_at timestamp (when the meetup/talk was announced).

Ah, yes, that's true! It's just the published_at from our writeup of the meeting. I'll fix that.

Our published_at timestamp is being used for when the recording of the talk got published, if at all. So if there is no published_at timestamp the talk recording isn't available. I usually set both announced_at and published_at to "TODO" if they are not known.

We don't have timestamps for the publication of the videos (although we could probably work it out from some git timestamps of when we added the coverage links). For now I'll do just put a placeholder published_at so they can be flagged as published.

We usually have all talks/events in videos.yml in date: asc order, while yours is in date: desc. Is there an easy way to update this?

Yup, swap a reverse_each for a each I think.

[h-lame]

@marcoroth I think I've fixed the videos.yml in this latest commit.

Does raise two questions though:

1. I've set both published_at and announced_at for the container talk that represents the meeting to be the publish date of the meeting writeup but for the individual talks inside the meeting I've set announced_at to the publish date of the meeting and published_at to "TODO". Does that work?
2. Our talk descriptions are markdown formatted and I've just copied that in directly to the videos.yml description field - do I need to do something to deal with that? Strip it out?

I'm tracking any changes to the generation of the file over in https://github.com/lrug/lrug.org/pull/407

[marcoroth]

Hey @h-lame, sorry for the delay on this. It's not forgotten! I will get back to this after my Rails World talk this Friday! 🙏🏼

[h-lame]

Hey @h-lame, sorry for the delay on this. It's not forgotten! I will get back to this after my Rails World talk this Friday! 🙏🏼

Not a problem! Good luck with the talk!

[marcoroth]

@h-lame I left some comments on https://github.com/lrug/lrug.org/pull/407, but other than that this looks good to go from my point of view, sorry for the delay on this! 🙏🏼

[ismasan]

Hi! Anything else needed to move this forward?

[marcoroth]

Maybe we can get https://github.com/lrug/lrug.org/pull/407 merged first and then the videos.yml in this PR updated based on that?

[marcoroth]

Thanks @h-lame! 🙏🏼

Finally got this merged! I opened https://github.com/lrug/lrug.org/pull/430 with the required changes so we can easily update and add future events as well.