Automate call for champions and events issues

[gr2m]

Based on discussion at #438

🎯 we want automate repetitive maintenance work of lunch.js

WIP plan

1. Create two projects with fields
   1. Locations: address (string)
   2. Events: Location number (GitHub issue number), address (string), date
2. Create issues for all current past locations
   • assign the host(s) that have last been active
   • close the issue if the location is currently not active
3. Add all location issues and event issues to the respective projects and set the fields
   The data is probably parse-able, or we could use some LLM for parsing it into the data we need.
4. Use the events project filtered by status:open as a source to keep the repository README updated for "upcoming events"
5. Create an automation that posts the "Call for champions" issue at 1.30pm on every first Tuesday of the month (after the lunch.js events conclude). Close the last call for champions issue at the same time.
6. When a lunch.js event issue gets closed, automatically create a new issue with the correct information preset. Comment on the closed issue with a link to the new issue.

random thoughts

• location assignees are location hosts. That way we get a history of past hosts
• use 👍🏼 emoji as a means to "sign up". From the website, we could have a dedicated button to sign up which would add the 👍🏼 emoji reaction in the backend. We could then have a cron running hourly or so which could take the "signups" and list them as sign ups in the issue description.
• Hosts could be asked to post a comment in a certain format to keep track of who ended up attending. We could also provide a custom web-ui for it to make it easier.

let me know what you think @jarrettch @trillium @anguspiv

[anguspiv]

This is awesome and a great place to start.

Regarding the signup and host adds attendance, we should make sure to consider this with user tracking and privacy. It might be a stretch, but I like to always double check.

Taking a product features approach, riffed on your ideas, and added a few of my own

Automation Improvements (Things I do manually/forget to do)

• Automatically create a new Call for Champions every first Tuesday of the Month at 1:30pm
• Automatically close current Call for Champions issue and link to new Call for Champions issue
• Automatically Close Current Location Issues
• Automatically add Current Location issue Assignees (Champion) to new call for champions issue (just thought of this)
• Automatically create and assign a new issue to add new champion as contributor to repo (This way they can manage, and label their location issue)

New Features: (Improvements to help promote lunch.js)

• Update the Homepage of lunch.js.la with current locations and dates
• Add "How to Champion" page to lunch.js.la (SEO Improvement)
• Add "About" information to lunch.js.la (SEO Improvement)
• Display a map of current locations for Lunch.js on the homepage (we can start manually and iterate automate)
  • Automate updates to the map when a new location is created
  • automate updates to the map when a new location is closed
• Allow users to request a location without championing (and track # of requests per location)
• Display Location Evergreen Information on the site (Information that is pretty consistent from one event to the next)
  • Champions
  • Title
  • City/Neighborhood
• Display Current Event Information for location on the site:
  • Start Time
  • End Time
  • Title
  • Description
  • Current Champion
  • Location:
    • Name
    • Link
    • Address
• On Call for Champions and new Location Event, post to social media accounts

Let's keep riffing on these ideas here for a bit, and then start figuring out the work, and action items here

[gr2m]

could you create a separate issue for the website, to keep it easier to reason about? I'd scope this issue to automations in this repository only.

Regarding the signup and host adds attendance, we should make sure to consider this with user tracking and privacy. It might be a stretch, but I like to always double check.

Very good point. I don't see any problem since the repository is public and anyone who wants to could scrape that information. But maybe I'm missing something?

I think we can add two sub-issues to this one

1. Automate "Call for champions" issues
2. Automate "Events" issues

And creating the projects would be the first actionable item for both

Create two projects with fields

1. Locations: address (string)

2. Events: Location number (GitHub issue number), address (string), date

We can ignore historic data for now and focus on automating what we have today? If you don't have any concerns, I can get started on that.

It would be great to get a at least one other location from the get-go, maybe we can ask the Pasadena folks who organized lunch.js not too long ago?

[anguspiv]

@gr2m are you able to create the projects you need? I think you should have permissions for this.

[gr2m]

Yes, I can create projects now, thanks!

If you don't have any objections I'll get started on this