magfest / ubersystem

MAGFest's Ubersystem - handles ticketing, staffing, analytics, volunteers, and tons more
http://magfest.org
GNU Affero General Public License v3.0
48 stars 55 forks source link

As a stage operations manager, I need to know the exact technical requirements of each performing act #3376

Open Travis-Snoozy opened 5 years ago

Travis-Snoozy commented 5 years ago

Presently, technical requirements are variably placed by bands into their stage plots. This frequently requires me, as the manager in charge of the stage operations, to carefully go through each band's stage plot, extract required information from it, and then bug the bands for any additional, missing, or unclear information on a band-by-band basis.

Examples of important information include:

Other issues (like #3069, #2923, #2563, #2489, #609) probably need to be considered in tandem with this one, since "visualists" can be fluid, a "band member" could technically be part of two bands. Overall, this is very easily bordering, if not straight-up talking about, revamping the whole way that groups vs. people are managed/modeled (e.g., what makes a member of an act a member of an act is the inclusion of that person in an act -- likewise, a visualist is somebody who's included in an act, and designated within that act as a visualist -- rather than having their status determined by their badge type in a cart-before-horse fashion).

Travis-Snoozy commented 5 years ago

A preliminary "spec" that's mostly done form-wise for band-type acts is available for review here: https://docs.google.com/document/d/18849OeRRphsTLnb9WlpIzog1JD_O7IpPZcy3NUHMBX8

EliAndrewC commented 5 years ago

This seems like something we can work on in time for the Band checklist opening for MAGWest. I'll make sure that we circle back to this after the dust clears from Super.