Some expected types of events:
- Large-scale: FLOCK, FUDcon
- Teams: FAD
- Local: education and open to the public, highly geeky and open to the public, just people in the group, other?

I will take a look at my interview notes and links and attachments and come up with ideas of what these might need to include.

From today's meeting:
if you have the event already in fedocal or google cal, etc, allow copy/pasting an event URL into the create event UI.

thats one issue that happens with a lot of events systems, is that the event already exists in one system and the others are just used to syndicate. eg if ambassadors are going to be at an event that is not a fedora event

Event creation stuff relating to recurring events:
- We need a ‘fedora-specific’ data-field for events
- “Meetups” are most easily defined as recurring events, so we need to allow events to be recurring.
- However, to avoid the problem of an event having no one showing up (or worse, someone new showing up alone), recurring event isn’t publicized outside the group until someone takes ownership of that instance.
- We also need a notification to remind the last instance’s organizer and the hub’s leadership that the next one needs an organizer.
- If not enough other people will be attending, the owner should cancel that meeting. To enable this, we need a notification to remind the organizer a day or two before the event to check in and make a call if there are enough attendees, the weather will permit, etc.
- If an event is cancelled, people who are signed up need to be sent a message about it (and perhaps remove it from the event calendar?).
- Guest presenters may not have accounts on Hubs, but will also need to be notified if the event is cancelled. Event creation should support putting in an email address for a guest presenter, so that they can be notified.

I'm not sure if we also need to support event planning within hubs; if we do, that would make it much easier to add events that were planned there.

I've tried to summarize the event-related information from the interviews (https://pagure.io/fedora-hubs/issue/raw/05c8ff88c7d6dba7a25ef42dd8c39ebeb3d66aa8b146fbfc3a8d007f53a7e57c-Interview_Summaries_anonymized.pdf) into the attached document. The first part is planning, the second creation, and the third is post-event.

I've tried to summarize the event-related information from the interviews (https://pagure.io/fedora-hubs/issue/raw/files/05c8ff88c7d6dba7a25ef42dd8c39ebeb3d66aa8b146fbfc3a8d007f53a7e57c-Interview_Summaries_anonymized.pdf) into the attached document. The first part is planning, the second creation, and the third is post-event.

Remember that budgeting information is important!
"events created through Hubs should provide fields in events for budgetary data like allocation, actual costs, and investment returns."