So I started playing with teams and ran into some issues which I started posting on the bugtracker. Some of them are more of a question of how teams are intended to be used than necessarily bugs.
What is the intention of teams? Is it to allow people to collaborate on writing/editing guides/fixes, or to allow people to connect to a guide or fix that they are working on but without editing any of the site?
Some of the issues I've run into that I'm not sure how they should be addressed are:
Any admin can remove the other admins of a group and seize total control. Perhaps there needs to be a tiered admin structure so that there is one root admin for a given team who cannot be removed by any other admins.
This is especially problematic since currently you need to be an admin in order to update guides/fixes. Reply to comment
Should an admin receive an email notification if a member leaves the group? (Maybe make it a selectable option, although this could be complicated by multiple admins) Reply to comment
My initial view of teams was lightweight groups of people working on common fixes / guides together. So more grouping people who are doing a common task, rather than editing/revising a guide/fix together.
My thoughts are that admins should be limited to trusted members only - if you don't trust them not to overthrow your group, you shouldn't make them an admin.
This does lead to the issue you raise in that only admins can take certain actions right now. That seems like the bug to me, and allowing two modes (admins only can make fixes or anyone on the team can edit a team fix) may fix that.
As for leaving notifications, my inclination is to say no. The only possible exception is notification that an admin left the group, or possibly notification anytime the admin group changes (someone new is added, leaves, etc).
In order to invite someone to join a team it looks to me like they need to have friended you. Is this correct. I think this makes sense, but figured I'd check that this is what is going on. Reply to comment
If you don't have an account, you'll need one. We recognize that this is a pain, but we do it to keep spambots from flooding the site. If this really bothers, you, please let us know. We're listening!
Get the Facts
Do Your Part
Me
My Part
Following
Community
Talk
Even More
Login or Get an Account!
Support SixLinks
What is the intention of teams? Is it to allow people to collaborate on writing/editing guides/fixes, or to allow people to connect to a guide or fix that they are working on but without editing any of the site?
Some of the issues I've run into that I'm not sure how they should be addressed are:
Any admin can remove the other admins of a group and seize total control. Perhaps there needs to be a tiered admin structure so that there is one root admin for a given team who cannot be removed by any other admins.
This is especially problematic since currently you need to be an admin in order to update guides/fixes. Reply to comment
My thoughts are that admins should be limited to trusted members only - if you don't trust them not to overthrow your group, you shouldn't make them an admin.
This does lead to the issue you raise in that only admins can take certain actions right now. That seems like the bug to me, and allowing two modes (admins only can make fixes or anyone on the team can edit a team fix) may fix that.
As for leaving notifications, my inclination is to say no. The only possible exception is notification that an admin left the group, or possibly notification anytime the admin group changes (someone new is added, leaves, etc).
More thoughts? Reply to comment
If you don't have an account, you'll need one. We recognize that this is a pain, but we do it to keep spambots from flooding the site. If this really bothers, you, please let us know. We're listening!