BMO/new-security-group: Difference between revisions

From MozillaWiki
< BMO
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
== Adding a new security group ==
== Adding a new security group ==


These steps need to be implemented when adding a new "security" group to BMO:
These steps need to be implemented when adding a new "security" group to BMO after the group has been created on BMO:


* Add code to extensions/BMO/lib/Data.pm that accomplish the following:
* Add code to extensions/BMO/lib/Data.pm that accomplish the following:
** %group_to_cc_map: Add the email address to automatically CC when a bug is placed in the security group.
** If the group is to be used as the default security group for a product (ie. it will be used when the user checks "Many users could be harmed by this security problem: it should be kept hidden from the public until it is resolved"):
** %always_fileable_group: Add the group as one that can always be filed into, whoever you are.
*** Add the group to <tt>%product_sec_groups</tt> (this establishes the mapping)
** %product_sec_groups: Add the product to group mapping for the new security group.
*** Add the group to <tt>%always_fileable_group</tt> (this ensures all users can file bugs into this group)
** If the requester wanted an automatic CC when a bug is placed into the group, update <tt>%group_to_cc_map</tt>
 
* Security groups rare can be bless directly into even admins. Normally the groups membership is determined by inheritance from other groups.
* Security groups rare can be bless directly into even admins. Normally the groups membership is determined by inheritance from other groups.

Revision as of 07:31, 2 May 2012

Adding a new security group

These steps need to be implemented when adding a new "security" group to BMO after the group has been created on BMO:

  • Add code to extensions/BMO/lib/Data.pm that accomplish the following:
    • If the group is to be used as the default security group for a product (ie. it will be used when the user checks "Many users could be harmed by this security problem: it should be kept hidden from the public until it is resolved"):
      • Add the group to %product_sec_groups (this establishes the mapping)
      • Add the group to %always_fileable_group (this ensures all users can file bugs into this group)
    • If the requester wanted an automatic CC when a bug is placed into the group, update %group_to_cc_map
  • Security groups rare can be bless directly into even admins. Normally the groups membership is determined by inheritance from other groups.