Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team Management #251

Closed
dpslwk opened this issue Aug 30, 2017 · 7 comments
Closed

Team Management #251

dpslwk opened this issue Aug 30, 2017 · 7 comments
Labels
2.1 Issues will not be looked at until 2.0 is live Process question

Comments

@dpslwk
Copy link
Member

dpslwk commented Aug 30, 2017

Need to work out how we deal with adding and removing team roles to users, (this should be the preferred way rather than #250 )

  • direct add for trustees?
    • Trustees puts a person in a team
  • request add for a user?
    • Member can request to join a team, Who approves? (trustees, existing team members)
  • User opts to leave a team
    • notify team and trustees
  • trustees direct removal
@dpslwk dpslwk added this to the 2.1 Additional features milestone Aug 30, 2017
@geeksareforlife
Copy link
Member

I think that being able to add people to a team role should be a seperate permission. That way you can give it to the trustee role, but also give it out as needed.

Some teams would make sense to allow 1 or 2 of the existing team members to allow new team members, but for others it might not make much sense.

@dpslwk
Copy link
Member Author

dpslwk commented Aug 30, 2017 via email

@geeksareforlife
Copy link
Member

I was more thinking of just having a general:

role.team.add

etc, and making a role called something like team administrators, but I actually like your idea better

@dpslwk
Copy link
Member Author

dpslwk commented Aug 30, 2017 via email

@geeksareforlife
Copy link
Member

It would be manual, absolutely. That might be a good idea...

@obxjames obxjames added environment dev (Vagrant) / staging / production related question and removed environment dev (Vagrant) / staging / production related labels Oct 23, 2017
@alexmannuk
Copy link
Member

I'd suggest not allowing the "apply to join team" option, under the same logic as we require prospective members to visit the space and talk with one of the membership team before they can start the signup process. Currently the membership team have the ability to add other members to the membership groups on HMS, I'd consider a similar approach of "any existing team member has the ability to add a new team member", but create and document a more solid role description for each team and joining process. I plan on updating all the team pages on the Wiki, so I'll look into this?

@dpslwk dpslwk added the 2.1 Issues will not be looked at until 2.0 is live label Jan 10, 2019
@dpslwk dpslwk added the Process label May 24, 2019
@dpslwk
Copy link
Member Author

dpslwk commented Jun 23, 2019

closed via #400

@dpslwk dpslwk closed this as completed Jun 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.1 Issues will not be looked at until 2.0 is live Process question
Projects
None yet
Development

No branches or pull requests

4 participants