Skip to content
This repository has been archived by the owner on Nov 26, 2021. It is now read-only.

Provide a view of member's tool induction status for admin purposes #110

Open
alex-wells opened this issue Nov 2, 2015 · 9 comments
Open

Comments

@alex-wells
Copy link
Contributor

It's been suggested that it may be useful for teams responsible for tool maintenance/inductions to have access to the list of inducted members for those tools; it should be a fairly trivial matter to add a view that renders the contents of the tl_members_tools table for individual tools that is accessible only to the inductors, maintainers for that tool and the admins/membership team.

Thoughts?

@daniel1111
Copy link
Member

I think this is a very good idea. It might also be nice to allow maintainers/admins to promote inducted members to inductor and/or maintainer in the system, as well as removing access from previously inducted members (ok, so that last part is probably unnecessary, as I don't think we've ever needed to do that).

@dpslwk
Copy link
Member

dpslwk commented Nov 2, 2015

Actually ability for maintainers to remove access would be good, some one abuses a tool they loose access and need to have a refresher induction.

'RepRap' Matt

On 2 Nov 2015, at 08:47, D [email protected] wrote:

I think this is a very good idea. It might also be nice to allow maintainers/admins to promote inducted members to inductor and/or maintainer in the system, as well as removing access from previously inducted members (ok, so that last part is probably unnecessary, as I don't think we've ever needed to do that).


Reply to this email directly or view it on GitHub.

@alex-wells
Copy link
Contributor Author

The un-induct feature sounds like a good idea to me; I'm quite happy to pick this up once I've finished with the rest of bouncer, if no-one has any problems with me doing so?

@geeksareforlife
Copy link
Member

Sounds good, but it should be maintainers (not inductors) that can un-induct

@alex-wells
Copy link
Contributor Author

do we want to include trustees/membership admins in the list of those able to do the un-induct?

@geeksareforlife
Copy link
Member

This just shows up the issue we have with permissions as HMS gets bigger

It might be better to deal with that issue first, before we add the promote/un-induct parts of this

@daniel1111
Copy link
Member

I'd say probably not membership admin's but maybe those in the 'full access' group should be able to? (if not limited to just maintainers)

@dpslwk
Copy link
Member

dpslwk commented Nov 2, 2015

yeah full access, and leave the rest till we sort ACL out

‘RepRap’ Matt

On 2 Nov 2015, at 10:20, D [email protected] wrote:

I'd say probably not membership admin's but maybe those in the 'full access' group should be able to? (if not limited to just maintainers)


Reply to this email directly or view it on GitHub #110 (comment).

@daniel1111
Copy link
Member

But yes - what @geeksareforlife said: permissions in HMS aren't that great atm

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants