| 2009-01-08 00:29:25 |
Diogo Matsubara |
description |
Currently if you create a team you have two choices for how mail should work with the team. With one, each team member is mailed, the second is that you can set a custom address for this mail. I think that there should be a third which is basically "/dev/null" or this team should not generate any mail.
This is useful for teams that are only used for permissions distribution and might want to have other, larger teams included in the list but don't want to create additional mail burden for those included teams.
Specifically I'm creating the team gnome-power-manager-team to have a shared place for all the GPM packaging branches. I would like to add ubuntu-core-dev to that team so that all core-dev's can access those branches also (not sure why they would, but they should be able to). We'd like to ensure that this doesn't cause the core-dev's any more mail burden.
Thanks, Ted. |
Currently if you create a team you have two choices for how mail should work with the team. With one, each team member is mailed, the second is that you can set a custom address for this mail. I think that there should be a third which is basically "/dev/null" or this team should not generate any mail.
This is useful for teams that are only used for permissions distribution and might want to have other, larger teams included in the list but don't want to create additional mail burden for those included teams.
Specifically I'm creating the team gnome-power-manager-team to have a shared place for all the GPM packaging branches. I would like to add ubuntu-core-dev to that team so that all core-dev's can access those branches also (not sure why they would, but they should be able to). We'd like to ensure that this doesn't cause the core-dev's any more mail burden.
Thanks, Ted. |
|
