Open patcon opened 11 years ago
rogierslag
commented
11 years ago Would be awesome if you could, as an owner, send a "request" to a user to allow being part of a organisation. Now you have to send them an E-mail, let them go to github and handle it there. Would be much more convenient for everyone if this could be part of the workflow while those people are on github.
Or publicize their membership and they have to allow it for example (again with some sort of request)
patcon
commented
11 years ago @rogierslag :+1: for github workflow.
Also, would be great if it defaulted to allowing orgs to publicize, but then after the first time, the user has the option to lock it down if they disagree. This would keep a smooth workflow for most people, and would stop irritating the small number of presumably high-rollers who are fending off "organization abductions" :)
ghost
commented
11 years ago @patcon You beat me to it. This seems to be the best option. Going through the hassle of contacting each member outside of github to get them to declare their membership is annoying at best.
patcon
commented
11 years ago Just sent an email to support@github.com:
Hey!
No expectation for you guys to follow any ongoing convo, but just wanted to direct-link to a suggestion for managing teams from someone who's trying to manage a growing org of 80 :)
https://github.com/isaacs/github/issues/115#issuecomment-27514964
Patrick
cc: @ayr-ton @LB--
LB--
commented
11 years ago I like the idea of requesting users to join organizations - it could be automatic when adding them to teams and they're not already in the organization.
As for who controls the publicity, that's a trickier question. The organization should be able to publicize their membership or hide their membership, but the user should only be able to hide their membership. Maybe in the user's organization settings they can prevent specific organizations from publicizing their membership.
I can't think of an elegant solution off the top of my head.
patcon
commented
11 years ago Heard back from @balevine:
Hey Patrick
Thanks for the heads up on the discussion. We're aware that those two solutions are imperfect, and we're still considering better ways to handle organization management and user publicity. If you have any specific ideas, you're obviously welcome to toss them our way.
Cheers
Context: https://github.com/holman/feedback/issues/274
It used to be that publicizing membership in orgs was controlled totally by the org. So an org owner could go to its "members" page and choose to publicize any user who was a part of any team, so that they would show up publicly as part of the org.
This led to some inconvenient behavior where people would get "abducted" into teams. (Total conjecture, but this likely affected a minority of very popular/influential github users.)
It seems there was a change and recently this management ability was put in the hands of users. If I go to an orgs member page for which I'm on any team, then I have the option to publicize my being part this org. This distributes responsibility and makes it very hard for an entity to manager the public face that is its team.
Both of these approaches have pros and cons, but it's not obvious how to make it better. Just wanted to record this as a friction, in case anyone has insight.