Mozillians/Events Manager/1.0/Events
What is an Event?
An Event is an online/offline gathering of Mozillians which is either officially hosted by Mozilla, one of our communities or an external entity (where a Mozillian is taking care part in). Examples of these events include: online events (e.g. Testdays, Support Days, L10n Days), offline (e.g. Reps Meetups, MozSpaces), Mozilla hosted (e.g. MozCamp, All-Hands, HackDays, Webmaker Days), etc.
Sign Up
- Desktop Mock-Up
- Mobile Mock-Up
Anyone should be able to see the Events Manager whether they're logged-in or not. Within each row entry is a green "Join" button which, when clicked, does two things depending on the user state:
- Logged-in Mozillians Phonebook User: The user is set as participating in the Event in our database and on the app. An e-mail is sent to the user saying that have signed up for the event explaining that the Event Coordinator will follow-up with them later for further details.
- Guest: A dialog pops up informing the user to submit a request to get involved in the Mozilla community (i.e. sign-up for a Phonebook profile). This functionality should tie in to the registration flow of the Mozillians Phonebook.
Leave an Event
- Mockup
Attendees of an event will be able to leave an Event prior to its start date/time via a button on the event listing page.
Sharing
Events are naturally social. People go to events to meet new people and to converse with the ones they already know. It should be easy to share the events Mozillians are participating in. So, each event on the Events Manager, should offer a way for Mozillians to tweet or post on Facebook an Event. Mozilla already offers a way to do this easily, we simply just need to implement it.
Event Fields
| Field | Description | Required? |
| Title | A short, one-line grabber that explains the topic or activity encompassing the event. Maximum of 50 characters. | YES |
| Start Date | The start date of the event. Most events will occur on a single day, but may occur over multiple days. Format used should be set to MMDDYYYY. Note: This may display differently depending on the user's location. | YES |
| End Date | The end date of the event. Most events will occur on a single day, but may occur over multiple days. Format used should be set to MMDDYYYY. Note: This may display differently depending on the user's location. | YES |
| Start Time | UTC+0 based and adjusted based on location of the event. If the event is virtual, then it will automatically be assigned to UTC+0. | NO (Set as all day is blank) |
| End Time | UTC+0 based and adjusted based on location of the event. If the event is virtual, then it will automatically be assigned to UTC+0. | NO |
| Frequency of Event | How often an event is hosted. This can be daily, weekly, monthly or quarterly. | NO (only once if blank) |
| Location | The address of the event. It can be a physical (2 Harrison St. San Francisco, CA) or virtual (e.g. IRC) address. | YES |
| Coordinator | This will be the Vouched Mozillian, Steward and/or Rep who created the event. | YES |
| Capacity | The maximum number of attendees. If set blank or "0", then there is no maximum. | NO |
| Description | Any ancillary information that the user should know about the event. This field should be able to include clickable links. | NO |
| Groups | Using the Phonebook groups list, the event will have Mozillian groups tagged to the event. | YES |
| When Created | This time/date stamp is shown in relation to the current date/time of page load. | YES (Automatic) |
