Mirror all BMO groups as Phabricator projects and keep them in sync

RESOLVED FIXED

Status

RESOLVED FIXED
11 months ago
11 months ago

People

(Reporter: glob, Assigned: dkl)

Tracking

({conduit-story, conduit-triaged})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 months ago
see https://bugzilla.mozilla.org/show_bug.cgi?id=1452013#c3

> One revision was made private due to unknown Bugzilla groups.

that's a completely non-actionable comment for people on a bug; what does it mean?  what should they do?

if it's a warning that something isn't configured correctly in phabricator, then the warning should be sent to the conduit team (eg. via sentry), not plastered on a bug.

if it's a call for action from one of the bug participants, it would be better if we email the participant directly with the issue and what they can do to resolve it.

Comment 1

11 months ago
Sounds like the consensus is this:

* For now, prevent the creation new projects entirely.
* Have Phabricator prevent creation of bmo-* projects by anyone other than BMO.
* Sync all BMO groups over as projects.
* Monitor for new group creation and renaming, updating Phabricator appropriately.

Updated

11 months ago
Summary: "One revision was made private due to unknown Bugzilla groups." bug comments are useless → Mirror all BMO groups as Phabricator projects and keep them in sync

Updated

11 months ago
Keywords: conduit-story, conduit-triaged
(Assignee)

Comment 2

11 months ago
Posted file github pr #548
Assignee: nobody → dkl
Status: NEW → ASSIGNED
(Assignee)

Updated

11 months ago
Status: ASSIGNED → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.