What is the point of the 'Minimal Event' setting in the Add event modal? And why is it separate?

[nathank (Nathan Kershaw)]

I’m referring to this:

I struggle to see how this would be helpful, but I’m sure it has some history. A Standalone event almost certainly does what is needed though, and I believe that this is completely redundant.

My users often tick it without realising what it does, and I had to go in and undo that quite a bit. Therefore, now I hide it in my instances with this CSS:

// hides minimal event option
.event-field.minimal-event {
        display: none;
}

Perhaps it could simply be removed from the plugin?

[awesomerobot (Kris)]

We added it for internally tracking events like version bumps, which don’t require attendees.

I imagine other sites would have use for these types of FYI events, but I’d be interested in feedback if anyone else has it as well.

Personally I think we could rename it to clarify slightly, maybe it gets reversed to “Collect RSVPs” and it’s default on.

[renato (Renato Atilio)]

@awesomerobot

We added it for internally tracking events like version bumps, which don’t require attendees.

@nathank

A Standalone event almost certainly does what is needed though, and I believe that this is completely redundant.

Maybe the Standalone “Status” already covers the “don’t collect RSVPs” scenario?

“Minimal event” still shows Interested, while “Standalone” allows no RSVP at all

[awesomerobot (Kris)]

Oh completely glossed over standalone … minimal seems extra pointless if the only difference is the interested button. Maybe standalone just gets a reminder option in the … menu

[nathank (Nathan Kershaw)]

Yup! That is my angle.

I do wonder if ‘Minimal event’ was added before ‘Standalone’ was implemented, and never removed as intended.

The function of ‘Interested’ is easily replaced by watching for what it is worth.