Is there a benefit in preventing the creation of events whose start date occurs prior to the course's start date? This was raised during MDL-62960 but deferred as it wasn't central to resolving the issue. This is the scenario rezaie9 described:

1. There is a course that is not available to students yet. The actual availability is not important here. Just assume that the course start date is in future for whatever reason.
2. There are some Teachers and course creators that are working on the course.
3. They want to create a course event for let's say "deadline for uploading course files"

We have a similar use case at Lafayette. Our start and end dates are populated from our student information system and common across the term. It's not possible to change them. We do however have certain courses, such as those with a study abroad component, where there are events taking place before the official start of term. Our teachers cannot schedule these events and get very frustrated. We work around the issue by creating a separate course with meta linked enrollments, but that's not a great solution.

In addition, there are no similar constraints with course end dates, which feels inconsistent. If the concern with the start date is to prevent a teacher from creating an event with a wildly inappropriate date, then a modal click-through acknowledging that the event precedes the course start date would accomplish the same purpose.