Questions for the 1 25 meeting

Do we need to come up with coordinate system? How do we keep the show centered if the field changes? Something like 0,0 is the middle of the field? Hashes can change, end zone lengths can change?

• The times that the field changes is going to be rare.
• 0,0 is going to be the Tunnel side -10 yard line (the end of the end-zone). (#55)

Do we need a view with adjustable sidebars? Something with a splitter that can be adjusted? How do we implement that?

• We'll need something. Might have to roll it ourselves...

How do we do LoadFile?

• Michael's looking for it. Can we inject the file blob directly in.

Discuss the “image vs movement” idea from Brandon’s design. Is this an improvement?

• Discussed during the meeting.

Does our software scale for editing 200+ marchers; can we improve our tools?

• tools that we have work fine.

Discuss the different types of users that will use this site. How do we design for these users? Ex. STUNT, TAs, bandsmen; laptop or mobile.

• definitely need to support mobile.
• Panning, zooming needs to work well for trackpad, second for mouse, 3 for touch via mobile.
• We should also make sure we have a smaller screen that works well. Design for a 13" laptop for stunt, should be "useable" from Mobile.

How can we keep our code maintainable and readable for future contributors? Are our tests and linting enough?

• can we adjust the line limits to 120? (#56)
• We should probably have a PR guide. let's add that to GitHub PR (#57)

Questions for STUNT

When designing stuntsheets with 200+ people, what are the biggest pain points (and how can we improve) when:

• Making a stuntsheet based off an image
• Making a stuntsheet based off a movement
• Figuring out the continuities to get between stuntsheets
• Resolving colliding marchers

What questions do bandsmen ask when given a complicated stuntsheet? What is not clear?

What events or mistakes create the biggest setbacks? Can we make resolving them smoother?