Closed Bug 1608137 Opened 5 years ago Closed 5 years ago

Document and kickstart the agreed process to "suggest new or change existing metric types"

Categories

(Data Platform and Tools :: Glean: SDK, task, P1)

task

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Dexter, Assigned: Dexter)

References

Details

(Whiteboard: [telemetry:glean-rs:m11])

Attachments

(2 files, 1 obsolete file)

+++ This bug was initially created as a clone of Bug #1570386 +++

Once bug 1570386 is settled and the design is agreed upon, we need to document the outcome of our decision and implement the proposal strategy.

Whiteboard: [telemetry:glean-rs:m11] → [telemetry:glean-rs:m?]
Priority: P1 → P3
Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:backlog]
Assignee: nobody → alessio.placitelli
Priority: P3 → P1
Whiteboard: [telemetry:glean-rs:backlog] → [telemetry:glean-rs:m11]
Depends on: 1613859
Attached file change_request_metric_type.md (obsolete) —

This is a markdown questionnaire created from the proposal document (section "The custom bugzilla form").

This will be shown as the default form when filing a new bug in the Glean Metric Types component.

I tried to phrase the required points as question and to provide a simple example for each answer.

Attachment #9125394 - Flags: review?(chutten)
Attachment #9125394 - Flags: review?(brizental)

I think the form is very clear overall and the examples really help in understanding how to fill it.

One sentence that is not very clear to me is:

Depending on the request, only leave and fill one of the two sections below.

What is the intended meaning here? Do we have any non-required field?

And one small nit:

[...] This would make it harder to consume on available tools such as GLAM, requiring us to write custom SQL code._

(In reply to Beatriz Rizental from comment #2)

I think the form is very clear overall and the examples really help in understanding how to fill it.

One sentence that is not very clear to me is:

Depending on the request, only leave and fill one of the two sections below.

What is the intended meaning here? Do we have any non-required field?

Oh, you're right. That's a leftover from a previous version of that file.

And one small nit:

[...] This would make it harder to consume on available tools such as GLAM, requiring us to write custom SQL code._

Fixed!

Attachment #9125394 - Attachment is obsolete: true
Attachment #9125394 - Flags: review?(chutten)
Attachment #9125394 - Flags: review?(brizental)
Attachment #9125402 - Flags: review?(chutten)
Attachment #9125402 - Flags: review?(brizental)

And this is the template to be used to drive the discussion after a new request is triaged.

Feedback is appreciated. This captures what was decided on in the proposal document, section "The discussion document". The format is intentionally very simple to allow for easier conversion to other formats in order to attach it to the bug.

Flags: needinfo?(mdroettboom)
Flags: needinfo?(chutten)
Flags: needinfo?(brizental)
Flags: needinfo?(brizental)
Attachment #9125402 - Flags: review?(brizental) → review+

See comment 5.

Flags: needinfo?(brizental)

Left comments in the document.

Flags: needinfo?(brizental)
Attachment #9125402 - Flags: review?(chutten) → review+

Comments in the doc.

Flags: needinfo?(chutten)
Depends on: 1614401

The process doc is now publicly available on the Mozilla Wiki.

LGTM

Flags: needinfo?(mdroettboom)
Attached file Glean Book PR

Note to self: before closing this bug I need to move the existing bugs to the other component.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: