Public Teams Redux - Githubissues

svperfecta commented 11 years ago

We've been thinking a lot about clans groups and teams while we were out here. Essentially we think we should create something called TEAMS, and allow them to be both private or public. We should roll out public teams first. Here's the suggested breakdown:

SIMPLE PUBLIC TEAMS

Anyone can join
Anyone can follow
Has a homepage, is visible to the public
Owner can edit team's info
Team affiliation is shown on profile
Users can join up to four? teams

Later on down the road, I would suggest we add: SIMPLE PRIVATE TEAMS

Membership is by invite only * Invites are sent using the new notification system to someone's email account * Membership has two states, invited, or active
When you join, you automatically follow the team (later we might allow unfollowing)
Has a homepage, is visible to the public
Owner can edit team's info
Team affiliation is shown on profile

COMPLEX PUBLIC/PRIVATE TEAMS

Owner can allow anyone else to be a manager, or an owner
Managers & owners can ban people people
Managers & owners can give anyone a team title "support, engineer, mid, top, bot, jungler"
Owners can can change info

FUTURE:

Teams automatically get a public or private area in our forums or a irc channel or something

erkattak commented 11 years ago

puts on devil's advocate hat

What is the pro of building in an exclusivity mechanism when our whole point is to get you matched up with people?

sethlouey commented 11 years ago

Professional clan teams will want it and we want them.

Sent from my iPhone

On Mar 28, 2013, at 8:46 AM, Erik Straub notifications@github.com wrote:

puts on devil's advocate hat

What is the pro of building in an exclusivity mechanism when our whole point is to get you matched up with people?

— Reply to this email directly or view it on GitHub.

svperfecta commented 11 years ago

We shouldnt do it first, totally agree. But we needed something :) On Mar 28, 2013 8:46 AM, "Erik Straub" notifications@github.com wrote:

puts on devil's advocate hat

What is the pro of building in an exclusivity mechanism when our whole point is to get you matched up with people?

— Reply to this email directly or view it on GitHubhttps://github.com/madgloryint/nowplayus/issues/244#issuecomment-15595868 .

svperfecta commented 11 years ago

Public first On Mar 28, 2013 9:00 AM, "Brian Corrigan" bcorrigan78@gmail.com wrote:

We shouldnt do it first, totally agree. But we needed something :) On Mar 28, 2013 8:46 AM, "Erik Straub" notifications@github.com wrote:

puts on devil's advocate hat

What is the pro of building in an exclusivity mechanism when our whole point is to get you matched up with people?

— Reply to this email directly or view it on GitHubhttps://github.com/madgloryint/nowplayus/issues/244#issuecomment-15595868 .

madglory / nowplayus

Public Teams Redux #244