Discontinued conferences

[jefftriplett]

Would it make sense to lump discontinued events into its own section?

It feels like we have a pretty big list of discontinued events and events that haven't returned for 2 to 3 years, and it's a lot to visually process to find active events.

[jonafato]

I'm in favor of this and think it would reduce clutter on the site, especially once updated to reflect those events that haven't happened for several years.

[jefftriplett]

@jonafato did you have thoughts on the name "discontinued"?

If an event has happened since 2020, 2022, or 2023 is there a threshold?

[jonafato]

@jonafato did you have thoughts on the name "discontinued"?

I would be in favor of a less permanent word than discontinued (e.g. "dormant" or "inactive") in the hopes that these events will come back or that we can help make the right connections to pass the torch to new groups of organizers. I expect that most of these are cases of "we don't have the time or energy to run an event right now" rather than "this event is never coming back".

If an event has happened since 2020, 2022, or 2023 is there a threshold?

I'm sure there are a ton of events that have not come back since 2020. If we (collectively) know that a group is working on bringing one of these back, it makes sense to leave it as active. For others, it's probably disruptive to past organizers to just mark the events discontinued / dormant / whatever now and update the page again when they return.

[jefftriplett]

I'm struggling a little bit with what the vision of this project was and should be.

Listing all PyCon and related Python events feels like what we started with, which is great.

Should we make it easier to find active events, or does that take away from the original intent of the project?

I personally lean towards making it more obvious which events are current and active over ones that may not have returned.

[glasnt]

I would be a fan of "past" or "previous" events. I think for data ease, this should be a flag on existing events, as opposed to moving events to a new file (which allows for a one-line change to mark an event as (past/dormant/discontinued, etc).

[jonafato]

"past" or "previous"

I find these words to be a bit overloaded in this context, i.e. talking about past iterations of continuing conferences vs. conferences that are no longer active.

I think for data ease, this should be a flag on existing events

I'm interpreting this issue as how to best render discontinued events on the page (using the existing discontinued attribute present on a few events now but applicable to several more) rather than moving files around to different categories. I expect that most visitors of this site would be more interested in seeing the active Python conferences they can participate in, so pushing the inactive ones into a section below the active ones should streamline their experience on the site. Happy to put together a PR for review and iteration.

[glasnt]

Apologies, let me clarify:

I think for data ease, I think it should be a flag on the yaml for existing events. This flag can be used by the site's logic to filter events, so only active events appear in the listing, and inactive appear elsewhere.

[jonafato]

I think we're all in agreement. This flag exists and is used today e.g. with PyCon Uruguay (and a couple of others):

pycon.org/_national/pycon-uruguay.yml

Line 4 in 67e1ba7

discontinued: true

Today, this is used to annotate the event via CSS

pycon.org/css/main.css

Lines 358 to 364 in 67e1ba7

	.discontinued {
	font-style: italic;
	float:right;
	}
	.discontinued::before {
	content: "(discontinued)"
	}

I believe we're all saying that listing inactive events elsewhere would be an improvement, but let me know if I've misunderstood.