Thunderbird team, Firefox team, Drumbeat team, Localization team, Europe team, Engagement team etc. It would transform our team alliances from being org-driven into a more project related.
This sounds a lot like tagging, but are you referring to something a bit more weight to it? Are you talking about implementing ways for people to do social networking kind of stuff on this site or simply finding people that are a part of that team?
It's definitely more than tagging because I envision the "team page" as a separate entity, a virtual presence of a social group that cooperates together. Where I'm coming from is the world where the "team" at Mozilla is strictly overlapping with the role in the organization - say, you're hired by Mozilla to do QA so you're part of "QA team", but is hiring the only way to be a part of "QA team"? I imagine that mozillians.org could replace this organization-based grouping system with a more distributed, project-based one where being part of the group is a matter of being part of the project, not the organization. Such teams would be Many2Many with people and team leaders would add members of the team after them requesting to be added to the team. This could further help for things like what I proposed at bug 680224. The reason for us to group together (and by us I mean everyone who's involved) is to act in an organized way toward making an impact. For that to happen we organize ourselves into teams. That's why I thought that team units would fit into mozillians.org project (not the phone book through). I understand that it's a level of taxonomy that you're not currently working on, but I just wanted to add it for future reference :)
> Where I'm coming from is the world where the "team" at Mozilla is strictly > overlapping with the role in the organization - say, you're hired by Mozilla > to do QA so you're part of "QA team", but is hiring the only way to be a > part of "QA team"? In this case, wouldn't this be a matter of having QMO, the home of Mozilla's QA team, integrate with the phonebook in some way? That could also address bug 680224. Instead of having team pages in the phonebook itself, people could tag themselves as part of a team in the phonebook and the associated site for that team could pick that up. That's what MDN and ReMo are interested in doing -- having a site for their team and then checking the phonebook for information about who is in that team. So this would just be something that tagging enables other sites to make use of.
David's got a good point. This is a community directory app and won't go into the social network area by incorporating things like teams. We can offer links to the team sites themselves (if they're available), but not within the phonebook app.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
I'm not sure if this is a wontfix though. The phonebook will need to allow sites like QMO or MDN to integrate with it to create these networks or circles, right?
Component: mozillians.org → Phonebook
Product: Websites → Community Tools
QA Contact: mozillians-org → phonebook
Version: unspecified → other
You need to log in before you can comment on or make changes to this bug.