• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Disclosure project - Checkpoint from 2011-11-02

Harden bug and teams

• Private/security bugs with open teams -> in progres

  • 20% of users have complied
  • Will be cleaned up forcebly on Nov 11.

• PPA with open teams -> email in progress

  • Grace period of 2 weeks also there.

• Private bugs with multiple bug tasks -> in progress

  • Script to split a bug -> working

  • Will need to be run by a LOSA (plus bug #....) because of status change restricted to bug supervisor.
  • Currently expect project owners to review the list of affected bugs and

    then run the split-bug script to do the split -> doesn't scale.

  • Need to be intervention less: get agreement from stakeholders on the script output and run it across the board.

Managing disclosure

• New schema landed.
• Need to prepare announcement on new policy way of working, give them migrated policy content and ask them to review.
• We need to let people edit the security policy.
  • Should we manage this through +manage-disclosure page.

Other deliverables

• Collateral deliverables
  • Deletion of bugtask
    • UI landed "under the cover"
    • Will add AJAXification this week.
  • A good source of "weird" private bugs is comments with private info
    • Change the policy to allow project maintainers, bug supervisors and

      users to hide their comments -> would reduce source.

Actions for next checkpoint

• [huwshimi] Produce new mockups around security/privacy policy conundrum (options for one or two pages)
• [danhg] User-test the mock-ups
• [purple] Fix the bug that prevents admins from setting privileged bug status.
• [purple] Review the split script and get agreement from stakeholders on its output so that we can run it unattended.
• [purple] Settle what are the requirements from stakeholders before we can turn-off the multi-tenancy feature for private bugs.
• [purple] Send the PPA clean-up email
• [purple] Change the policy around hiding own bug comment.
• [purple] Add AJAX ui to delete bug task
• [purple] Create report around branch privacy multi-tenancy.
• [purple] Remove multi-tenancy around bug privacy.