Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

As an organizer I can see how many times a participant has come to my chapter's events as well as their attendance rate. #95

Closed
QuincyLarson opened this issue Oct 20, 2019 · 5 comments
Assignees
Labels
Roadmap This is an issue/feature that is on the road map for the future UI/UX This issue deals with UI/UX

Comments

@QuincyLarson
Copy link
Contributor

No description provided.

@vkWeb vkWeb added the Help Wanted Extra attention is needed label Oct 24, 2019
@QuincyLarson QuincyLarson changed the title As an organizer I can see how many times a participant has come to my chapter's events as well as their attendance rate. API: As an organizer I can see how many times a participant has come to my chapter's events as well as their attendance rate. Nov 30, 2019
@QuincyLarson QuincyLarson removed the Help Wanted Extra attention is needed label Nov 30, 2019
@QuincyLarson QuincyLarson changed the title API: As an organizer I can see how many times a participant has come to my chapter's events as well as their attendance rate. As an organizer I can see how many times a participant has come to my chapter's events as well as their attendance rate. Feb 11, 2020
@allella allella added the UI/UX This issue deals with UI/UX label Mar 6, 2021
@ojeytonwilliams
Copy link
Contributor

What do we want the attendance rate to be? Is it going to be the percentage of invitees that actually attend? If so, we need to track if a member was invited. Then attendance rate would be "percentage of invited users that confirmed attendance".

While we could allow organizers to mark attendance, I don't think that's worth putting in the MVP. Instead I recommend using what the member says they will do in the calculation.

Finally, what do we want for non-invite-only events? Attendance rate would have to be different, in that case. I'm not sure it makes sense unless organizers can mark attendance (again, probably not an MVP thing).

@allella
Copy link
Contributor

allella commented Nov 10, 2021

I don't recall the source of this issue. I don't consider this an MVP feature so I'd vote to close and tag with "Roadmap" and deal with it after MVP.

It appears Quincy created this issue and I'm not sure if it was something he felt was needed or something from a meeting or split off from another issue that was closed and roadmapped.

@ojeytonwilliams ojeytonwilliams added Roadmap This is an issue/feature that is on the road map for the future and removed MVP labels Nov 15, 2021
@ojeytonwilliams
Copy link
Contributor

I'm fine with this being a post MVP feature. Do we need to close it, though?

@allella
Copy link
Contributor

allella commented Nov 15, 2021

@ojeytonwilliams Quincy was the one closing them with Roadmap during previous meetings as a way to filter out noise but still be able to find them for post-MVP. I think it's a decent pattern as long as we Roadmap tag them, but I'm open to other suggestions.

@ojeytonwilliams
Copy link
Contributor

No, that's fine. Let's just stick with that pattern. Should all the Roadmap issues be closed, then?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Roadmap This is an issue/feature that is on the road map for the future UI/UX This issue deals with UI/UX
Projects
None yet
Development

No branches or pull requests

5 participants