More actions
Nessie Blue (talk | contribs) |
Nessie Blue (talk | contribs) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
** For E-Uni #lecture-hall events select 'Stage Channel' | ** For E-Uni #lecture-hall events select 'Stage Channel' | ||
** For events in any other E-Uni voice channels (including Mumble) select 'Voice Channels' category | ** For events in any other E-Uni voice channels (including Mumble) select 'Voice Channels' category | ||
** The 'Somewhere Else' option is suitable for any other public events | ** The 'Somewhere Else' option is suitable for any other '''public''' events | ||
* Your event visibility will be tied to the visibility of the 'Location' you have selected | * Your event visibility will be tied to the visibility of the 'Location' you have selected | ||
** Public events such as classes, talks, and public fleets should be scheduled in public voice channels (marked with a blue diamond) | ** Public events such as classes, talks, and public fleets should be scheduled in public voice channels (marked with a blue diamond) | ||
** EVE University specific events (e.g. Strat-Ops) should be scheduled in E-Uni gated channels to avoid them being publicly visible (even if it takes place elsewhere, e.g. on Mumble) | ** EVE University specific events (e.g. Strat-Ops) should be scheduled in E-Uni gated channels to avoid them being publicly visible (even if it takes place elsewhere, e.g. on Mumble) | ||
*Use the correct title Prefix for your event. For fleets use: [STRATOP], [PVP], [FW], [PVE | *Use the correct title Prefix for your event. For fleets use: [STRATOP], [PVP], [FW], [PVE]. For classes use: [CLASS]. For anything else use [EVENT]. | ||
* Use your '''local time''' when creating event | * Use your '''local time''' when creating event | ||
** People viewing the event will see it in | ** People viewing the event will see it in their local time of their own Discord server | ||
** Consider adding EVE time in the event description for added clarity | ** Consider adding EVE time in the event description for added clarity | ||
* Include a description. | * Include a description. | ||
** A brief description of the event should give potential attendees a reason to want to attend your event. | ** A brief description of the event should give potential attendees a reason to want to attend your event. | ||
** Specify the | ** Specify the form-up location for fleets. | ||
** If its a class that is going to include a practical ensure you note that. | ** If its a class that is going to include a practical ensure you note that. | ||
** Get creative! | ** Get creative! | ||
| Line 36: | Line 36: | ||
* If a '''one-off event''' is cancelled, you may delete the Discord Event, but communicate this to members in relevant ping channels | * If a '''one-off event''' is cancelled, you may delete the Discord Event, but communicate this to members in relevant ping channels | ||
** If it is short notice, ping @everyone | ** If it is short notice, ping @everyone | ||
** With more advance notice, consider posting a 'silent' ping (without the @ | ** With more advance notice, consider posting a 'silent' ping (without the @everyone) in the appropriate ping channel | ||
* If you need to cancel '''an event in a repeating series''' - cancel that specific event (it will show to viewers as Cancelled) | * If you need to cancel '''an event in a repeating series''' - cancel that specific event (it will show to viewers as Cancelled) | ||
** You can do that by clicking the 'triple dot' menu next to the individual date in a series, rather than the whole overarching Event | ** You can do that by clicking the 'triple dot' menu next to the individual date in a series, rather than the whole overarching Event | ||