backstage-technical-services / hub

The starting place for anything related to the website.
0 stars 1 forks source link

Allow uninducted members to be given accounts #108

Closed bnjns closed 4 years ago

bnjns commented 4 years ago

In GitLab by @ACascarino on Oct 27, 2019, 10:34

Request

Currently, our internal policy is to only add members to the website when they have both a) paid membership and b) attended induction. This makes keeping track of late joining members difficult, and creates a strange middle ground for members who have bought membership but have not done an induction - we tend to then run an induction for them on-event, but having then sign up to an event without website access is tricky!

Further, this restriction on having members only added to the website once they've been inducted makes the induction skill fairly redundant and an administrative faff.

A proposed solution would be a simple visual indicator, visible to committee and the TEM, on members who sign up to an event without having level 2, in combination with an email alert warning the committee and the TEM that this member would need an induction before they can crew the event.

This provides a nice middle ground, allowing paid members to have website access, making it more obvious for TEMs and committee that certain members require an induction, and gives the induction skill a purpose.

Where should this go?

Events diary! And a small crossover with the skills section

Rationale

Mostly explained above I guess

Urgency

Realistically too late to be useful this year, so in place by next academic year would be the deadline

bnjns commented 4 years ago

In GitLab by @jordanlkirk99 on Oct 27, 2019, 22:05

Sounds like a good idea.

How about a simple orange excalmation mark next to their name, with a simple explanation line underneath like 'requires induction'?

How do the SU tell committee who has paid for membership?

bnjns commented 4 years ago

In GitLab by @bnjns on Oct 27, 2019, 22:12

having members only added to the website once they've been inducted makes the induction skill fairly redundant and an administrative faff

Yup, agreed. The induction skill has always seemed a bit unnecessary. I'd like to detach any important logic from a skill level, so this could easily be achieved with something like a flag on a user's account. It could even be expanded to track whether members have paid too (although only if wanted).

How about a simple orange exclamation mark next to their name, with a simple explanation line underneath like 'requires induction'?

That would be my suggestion.

How do the SU tell committee who has paid for membership?

Pretty sure you can see this on BathStudent (or whatever it's called now) if you're a committee member.


My only other thought is that this would be a fairly substantial change to how we handle new members and I don't think is in the remit of us (maintainers of the website) to make that change. While an administrative faff, not giving new members accounts was a deliberate step to ensure that we knew anyone with an account is allowed to be involved and I think we need approval from higher up (whoever that is) that changing this is okay.

bnjns commented 4 years ago

In GitLab by @bnjns on Oct 27, 2019, 22:16

changed title from {-Better tracking for uninducted member-}s to {+Allow uninducted members to be given account+}s

bnjns commented 4 years ago

In GitLab by @bnjns on Oct 27, 2019, 22:16

changed the description

bnjns commented 4 years ago

In GitLab by @bnjns on Oct 27, 2019, 22:17

@Hypothawits Would you be able to take this idea to the committee?

bnjns commented 4 years ago

In GitLab by @Hypothawits on Nov 3, 2019, 19:33

Committee has decided not to allow un-inducted members web accounts. (obvs the next committee might feel different). I believe the issue of the induction skill being redundant will be dealt with the skills rework that's ongoing. I will add this idea as part of my handover docs, not sure if we should close this issue for now or just ignore until next year.

bnjns commented 4 years ago

In GitLab by @bnjns on Nov 3, 2019, 20:00

That's mildly disappointing - thought this was a good idea. I don't think we can justify keeping it open if the idea's been rejected by the committee. Would not object to it being re-opened next year though.

bnjns commented 4 years ago

In GitLab by @bnjns on Nov 3, 2019, 20:00

closed

ACascarino commented 4 years ago

Just to chime in here whilst I remember - I believe the committee then later voted to reverse that decision and give uninducted members accounts... might be worth confirming and adding as a feature either to the current website if desired or to the new SPA

bnjns commented 4 years ago

Ooh, did they? Would you be able to open a new issue if they okayed it (just so not everything is written by me :joy: )?

We can definitely include this in the scope of the API/SPA.

ACascarino commented 4 years ago

They did! Opening a new issue now :)