Skip to content

Add gig attendance-taking feature#760

Open
bklang wants to merge 4 commits into
mainfrom
attendance-taking
Open

Add gig attendance-taking feature#760
bklang wants to merge 4 commits into
mainfrom
attendance-taking

Conversation

@bklang

@bklang bklang commented Jun 21, 2026

Copy link
Copy Markdown
Collaborator

This feature allows band admins to track who actually showed up at a gig. This can be used to know whether the band is waiting for more people to arrive, and can be used to help determine gig payouts later.

Future work:

  • Reporting
  • Lock down attendance updates for past gigs
  • Lock down attendance updates for future gigs
ScreenRecording_06-21-2026.15-46-52_1.mov

This feature allows band admins to track who actually showed up at a gig. This can be used to know whether the band is waiting for more people to arrive, and can be used to help determine gig payouts later.
@aaronoppenheimer

Copy link
Copy Markdown
Contributor

That's great! I love it. Two suggestions:

  • integrate it with the archive view, which currently just shows how the person answered the gig - could also add a "here's what really happened" note for the band admin to see.
  • on the gig page, I changed the "see all [which did not show occasionals]/see only committed" toggle to "see all/see all+occasionals/see committed" because it made sense that if I want to update the plan for an occasional member (who might not use the gig-o very often) I need a way to see them on the list. On the attendance sheet it might be "see all/see all+occasionals/see everyone who committed" in the same way.

@bklang bklang force-pushed the attendance-taking branch from b406925 to 28ad350 Compare June 21, 2026 22:57
@aaronoppenheimer

Copy link
Copy Markdown
Contributor

Is this good to merge?

@bklang

bklang commented Jul 5, 2026

Copy link
Copy Markdown
Collaborator Author

Is this good to merge?

It is merge-able, yes. I have held off for 2 reasons:

  1. I wanted to address your feedback
  2. (more importantly) I wanted to give you a chance to merge the Django upgrade before adding more code to the project

@aaronoppenheimer

Copy link
Copy Markdown
Contributor

Oh, don’t wait for me. It’s gonna take me a little while to get back to porting. The python stuff doesn’t change at all, actually, it’s just some changes to bootstrap to bring it up to the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants