Change around components in the Data & BI Services Team product

VERIFIED FIXED

Status

()

VERIFIED FIXED
3 years ago
3 years ago

People

(Reporter: scabral, Assigned: dkl)

Tracking

Production

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
The Data & BI Services Team product has lots of categories, which are not useful to how we categorize things. We'd like to change them. We are open to changing names of existing components and/or retiring some components. I will try to outline here what we want, and what to do with the existing bugs.

All components should be in the Data & BI Services team, with a "QA Contact" of scabral@mozilla.com. The "Confidential Metrics bug" flag should be unchecked for all components, and there are no suggested reviewers for the review flag.

With that, we'd like the components as listed in https://docs.google.com/a/mozilla.com/spreadsheets/d/1Of8tw3BwPjoU-6Og1ax8CvFtPdEW-a4SytmSg-Bpv_M/edit?usp=sharing

Each line has a component name, description, and assignee, as well as any notes. I wasn't sure if I should make a separate bug for each, or put it all in one bug, so a spreadsheet seemed to be a good way to organize my thoughts until we can decide the best action plan.

Essentially: Retire 21 components, rename 8 components, create 5 new components.

I'm happy to have this done any way that's best, and I can lend some resources to these things (e.g. https://wiki.mozilla.org/BMO/RetiringComponents has some steps I might be able to do)
(In reply to Sheeri Cabral [:sheeri] from comment #0)
> Each line has a component name, description, and assignee, as well as any
> notes. I wasn't sure if I should make a separate bug for each, or put it all
> in one bug

a single bug is the best way to track this.

> so a spreadsheet seemed to be a good way to organize my thoughts
> until we can decide the best action plan.

it isn't clear if the plan you've documented is final, or if you still need time to figure out what you want.

once you've figured it out, it would be very helpful if you listed each of the current components with the changes you want made.

eg.

Consultative Svcs : Custom Dashboards and Reports
- rename to "BI: New Dashboards"

Consultative Svcs: Subject Matter/BI/Metrics
- move all bugs into "Other" component
- delete
Group: mozilla-employee-confidential
Flags: needinfo?(scabral)
(Reporter)

Comment 2

3 years ago
Ah, yes, sorry, the spreadsheet is final. I have rearranged it so each line is either an existing component to be retired or renamed, xor a new component to be created. I also realized there was one new component I needed.

Lines 2-30 are the existing components and what to do with them (retire and where to move open bugs to, or rename) and lines 31-36 are new components to be created.

Let me know if the spreadsheet makes sense or if I should organize it differently.
Flags: needinfo?(scabral)
(Assignee)

Comment 3

3 years ago
Note to admin: Rows where it says 'retire' without a component to be moved to (mostly Other), move to Graveyard product.
(Assignee)

Updated

3 years ago
Assignee: nobody → dkl
Status: NEW → ASSIGNED
(Assignee)

Comment 4

3 years ago
I have added the new components already.

The account mozsredba@pythian.com did not exist for the component DB: Hadoop Administration. Please advise on a different value or just use nobody.

Should we go ahead and continue with the rest (renaming and moving)?

dkl
Flags: needinfo?(scabral)
(Reporter)

Comment 5

3 years ago
I just emailed Pythian asking for an address for that - and asking them to make a BMO account for it.

Please do go ahead with the rest. Also, please note the timeframe on this is not dire. While it would be great to have everything in place sooner rather than later, mid-October is our cutoff (to have enough time to have the workflow in place before my leave starts in early December).
Flags: needinfo?(scabral)
(Assignee)

Comment 6

3 years ago
Components to be renamed have been done. Now to retire the rest.

Admin steps:

# perl scripts/syncflags.pl "Data & BI Services Team" "Data & BI Services Team Graveyard"
# perl scripts/syncmsandversions.pl "Data & BI Services Team" "Data & BI Services Team Graveyard"

Move to Data Warehouse:

# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Consultative Svcs: Data Warehousing"

Move to Other:

# perl scripts/movebugs.pl "Data & BI Services Team" "Consultative Svcs: Subject Matter/BI/Metrics" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Consultative Svcs: Training" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Customer Request (Master Bug)" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Data Ingestion: External" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Data Processing : ETL : MySQL target" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Data Processing: ETL: Vertica Target" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "General Discussions" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Internal Project (Master Bug)" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Operations: Data Quality / Data Event Research" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Operations: Platform Troubleshooting and Recovery" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Operations: Tool Troubleshooting and Recovery" "Data & BI Services Team" "Other"
# perl scripts/movebugs.pl "Data & BI Services Team" "Tool Development & Maintenance: Data Ingestion" "Data & BI Services Team" "Other"

Move to Graveyard:

# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Data Ingestion: Client"
# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Data Ingestion: One-Off"
# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Data Ingestion: Ping"
# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Data Processing: Aggregations and Views"
# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Data Processing: ETL: JSON target"
# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Data Processing: One-Off"
# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Operations: User Management"
# perl scripts/movecomponent.pl "Data & BI Services Team" "Data & BI Services Team Graveyard" "Tool Development & Maintenance: ETL"

Sheeri, does this look correct to you based on the spreadsheet?

dkl
Flags: needinfo?(scabral)
(Reporter)

Comment 7

3 years ago
dkl, I cross-referenced the document and yes, this looks good to me.

I will also ask if you can make one more change - I haven't put this on the spreadsheet because it's one of the new components - instead of "DB: bugzilla/reviewboard MySQL" can you change it to "DB: MySQL bugzilla/reviewboard" ? we've already had one incident where a bugzilla bug was made in the general MySQL component. (I thought putting bugzilla first would make people see it, but they basically ignored that part because they saw MySQL).

Thanx on both these fronts!
Flags: needinfo?(scabral)
(Assignee)

Comment 8

3 years ago
(In reply to Sheeri Cabral [:sheeri] from comment #7)
> I will also ask if you can make one more change - I haven't put this on the
> spreadsheet because it's one of the new components - instead of "DB:
> bugzilla/reviewboard MySQL" can you change it to "DB: MySQL
> bugzilla/reviewboard" ? we've already had one incident where a bugzilla bug
> was made in the general MySQL component. (I thought putting bugzilla first
> would make people see it, but they basically ignored that part because they
> saw MySQL).

All done.

dkl
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Reporter)

Comment 9

3 years ago
Everything looks fantastic, thank you.
Status: RESOLVED → VERIFIED
(Reporter)

Updated

3 years ago
Blocks: 1226287
You need to log in before you can comment on or make changes to this bug.