Closed Bug 556623 Opened 15 years ago Closed 5 years ago

[life] expose l10n forest for trees/appversions

Categories

(Webtools Graveyard :: Elmo, enhancement, P2)

Product:
Webtools Graveyard
Component:
Elmo
Type:
enhancement

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bmo.cec, Unassigned)

References

Details

(Whiteboard: [data2])

It would be nice to have the l10n Mercurial repository to use indicated aside the label in the "Tree" column, or to add a new column next to it, to ease l10n work. I was sometimes lost in translation ;-) , well in branches to use.
Rewording this in the lingo we use in the back end. When folks see trees and appversions, it'd be good to expose what we know about those, in particular, which l10n forest is associated with them. Another feature would be to expose which en-US repos are in use, which we have set up in the database, but we never actually fill that data in.
Summary: Adding the l10n Mercurial repository to use in l10n dashboard → [dashboard] expose l10n forest for trees/appversions
I'm wondering if we should rip out the current link between tree and repos, and replace it with a versioned (by time) set of links to repo and module (plus tld nit for mobile, and something for weave).
Summary: [dashboard] expose l10n forest for trees/appversions → [dashboard][life] expose l10n forest for trees/appversions
Priority: -- → P2
Moving to time-window-based mappings is going to happen as part of data2.
Component: Infrastructure → Elmo
Product: Mozilla Localizations → Webtools
QA Contact: infrastructure → elmo
Summary: [dashboard][life] expose l10n forest for trees/appversions → [life] expose l10n forest for trees/appversions
Whiteboard: [data2]
Version: unspecified → 1.0
Axel: does this depend on another bug?
And further, has data1.1 solved this already?
Nope, this doesn't depend on other bugs. The db setup is there, Tree has repositories = models.ManyToManyField(Repository) l10n = models.ForeignKey(Forest) where l10n is actually filled in, but repositories is not. Extra candy if it knows about the top-level directories that matter for an app. See also the previous comments in this bug about how we may want to use the relationship over time here.
I'm not sure what to do here. Maybe a page with details for an AVT, linked from the team page tree/appversion box?

Is this still relevant with the current process? Could this bug be closed?

The production instance of Elmo running on l10n.mozilla.org has been decommissioned as of September 2020, and there are no plans to develop this project further.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.