[Event] "May Maintainers Circle 2023" should not longer be "upcoming"

[leecalcote]

Current Behavior

This event - https://layer5.io/community/events/may-maintainers-circle-2023 - needs it's upcoming property set to false.

---

Contributor Resources and Handbook

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

• 📚 See contributing instructions.

• 🎨 Wireframes and designs for Layer5 site in Figma (open invite)

• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.

Join the Layer5 Community by submitting your community member form.

[Kneatrum]

Hi @leecalcote , I would like to work on this issue. Can you please assign it to me?

[Anand-Theertha]

I would like to work on this issue as well!

[Ashparshp]

Thank you, @Kneatrum. I've assigned it to you, go ahead!

@Anand-Theertha, thank you for your interest! Since we assign issues in chronological order, we've already assigned this one. Please feel free to check out the other issues — we have a bunch of open ones!

[Kneatrum]

Thank you, @Ashparshp . However, if this task is only about setting the property, I notice that the upcoming property is already set to false.

[Kneatrum]

@Ashparshp Specifically on the closed issue #5896 , commit b25fd69

[hustlernik]

Upcoming is already set to false.

---

title: "May Maintainer's Circle 2023"
description: "Join Lee Calcote and Nate Waddington in the upcoming Maintainer’s Circle special session and explore their insights, and experiences from their mentorship journey within the CNCF."
date: 2023-05-30
thumbnail: ./Maintainer-Circle.png
darkthumbnail: ./Maintainer-Circle.png
eurl: https://calendar.google.com/calendar/u/0/r?cid=linuxfoundation.org_o5avjlvt2cae9bq7a95emc4740@group.calendar.google.com
type: Event
published: true
upcoming: false
resource: true
speakers: ["Lee Calcote", "Nate Waddington"]

Join Lee Calcote and Nate Waddington in the upcoming Maintainer’s Circle special session and explore their insights, and experiences from their mentorship journey within the CNCF.

[hustlernik]

Is this issue still open to work? @leecalcote