l10n decision bugs should be discoverable

NEW
Unassigned

Status

Localization Infrastructure and Tools
General
a year ago
a year ago

People

(Reporter: Pike, Unassigned)

Tracking

Details

(Reporter)

Description

a year ago
As we're trying out bugzilla to document decisions around l10n, Jeff and I figured it'd be good to have decision bugs to be discoverable proactively.

Jane, looping you in on this one. Is there already a concept for this?

I'd be up to create a "Decisions" component for the products we care about. That way, stakeholders could watch the component to be informed of decisions that are up to be made.

The downside of this is obviously that we'd create a bunch of components to be made.

Filing this in l10n infra general. If we're all on the same page, I'd file a bug on bmo to get the components created for this product and l20n, and then move this to l10n infra/decisions.
Flags: needinfo?(jfinette)

Comment 1

a year ago
(In reply to Axel Hecht [:Pike] from comment #0)
> As we're trying out bugzilla to document decisions around l10n, Jeff and I
> figured it'd be good to have decision bugs to be discoverable proactively.
> 
> Jane, looping you in on this one. Is there already a concept for this?
> 
> I'd be up to create a "Decisions" component for the products we care about.
> That way, stakeholders could watch the component to be informed of decisions
> that are up to be made.
> 
> The downside of this is obviously that we'd create a bunch of components to
> be made.
> 
> Filing this in l10n infra general. If we're all on the same page, I'd file a
> bug on bmo to get the components created for this product and l20n, and then
> move this to l10n infra/decisions.

thanks so much Pike. This quarter we wanted to 'pilot' adding the documentation of decisions to Bugzilla. An idea thus far would be fo the pilot purposes only to use: 

https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org and choose the Governance component.

If we deem this makes sense, then we’d look to create a new component “Decision Record”.

Would that work for you for now? Also super happy to take advice on a better way of recording. 

Thank you!
Flags: needinfo?(jfinette)
(Reporter)

Comment 2

a year ago
I guess right now I've got my bugs all over the place. I don't mind much moving them to governance for now, though.

It seesm that you're interested in a way to track *all* decisions. I'm expecting that there's a bigger audience that's interested in just some areas. Maybe that's an argument to have a product for decisions, and components for the primary target audience?

If we're just looking at the ability to do reports, we could also standardize on a component name, and individual products could opt in. I doubt we have component watching for this right now, but queries and reports would probably still work out fine. This taxonomy also had a plus in that people could follow "Firefox" or "L10n", and get all l10n bugs, including decision bugs.
Would a "Governance" component within Mozilla Localizations fit?
You need to log in before you can comment on or make changes to this bug.