Skip to content

Add London ruby User Group (LRUG) #889

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 7 commits into
base: main
Choose a base branch
from
Open

Add London ruby User Group (LRUG) #889

wants to merge 7 commits into from

Conversation

h-lame
Copy link
Contributor

@h-lame h-lame commented Aug 10, 2025

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 added 3 commits August 10, 2025 08:18
@h-lame
Add comments to the event images about sizes
ef753cf 
I found it useful to know the dimensions when creating these images for LRUG,
but didn't see it documented elsewhere.
@h-lame
Provide scripts/import_event for reimporting a single org
854d2ca 
Run as

    bundle exec rails runner scripts/import_event -- lrug

This will look through data/organisations.yml to find the org with the supplied
slug and run the reimport for that org. This is otherwise a copy and paste of
the organisation creation part of db/seeds.rb.

I found this useful while I was prepping the LRUG data, so I hope it's useful
for others.
@h-lame
Add London Ruby User Group (LRUG)
c820685 
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.
@h-lame
Copy link
Contributor Author

h-lame commented Aug 10, 2025

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 and others added 3 commits August 10, 2025 10:18
@h-lame
Run prettier over the lrug videos.yml
18dca46 
This yml file was generated from lrug.org via a `to_yaml` call, but the default
output isn't in keeping with the default yaml prettier rules which is annoying.
@marcoroth
Merge branch 'main' into add-lrug
414ff0b
@marcoroth
Set type to meetup and remove .png assets
c688e24
marcoroth
marcoroth approved these changes Aug 10, 2025
View reviewed changes
Copy link
Member

@marcoroth marcoroth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you so much for tackling this @h-lame, this is awesome! I'm just gonna mention this PR here for future reference: lrug/lrug.org#406

I set the type: "meetup" which should remove the "Sponsors", "CFP" and "Schedule" Tabs for now, since we haven't really optimized those for Meetup Groups yet, as you noticed. I also removed the unused .png assets, since we only really use the .webp ones.

We are in the middle of trying to figure out how to automate a lot of things for RubyEvents, similar to what we do with RubyConferences.org.

Your videos.yml generator is awesome and is already a great start! I feel like as long as we don't have a good way of automating things in general it's probably fine for now the keep updating it manually and running prettier/the lint step as part of that workflow.

I also love the scripts/import_event script you wrote, thanks for that! I've been meaning to do that for quite some time since the seeding can take a bit to finish.

A few nits about the videos.yml file:

  • I think your published_at timestamp is our announced_at timestamp (when the meetup/talk was announced).
  • 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 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?

But otherwise, this looks good to go from my side, thanks for working on this! <3

@h-lame
Copy link
Contributor Author

h-lame commented Aug 10, 2025

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
Update lrug videos.yml file
2e6dd9d 
Extracted from a branch version on the lrug/lrug.org repo to address feedback:

1. put things in oldest first order
2. sort out published_at vs announced_at
@h-lame h-lame mentioned this pull request Aug 10, 2025
Open
@h-lame
Copy link
Contributor Author

h-lame commented Aug 10, 2025

@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 lrug/lrug.org#407

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@marcoroth marcoroth marcoroth approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@h-lame @marcoroth