1361033 - [configuration] add metadata to configuration docs

Status: RESOLVED FIXED

(Localization Infrastructure and Tools :: General, enhancement)

Description

[Axel Hecht [:Pike]]

Attachment: configuration notes - taipei 2017-04-24

Talked to flod a lot about configuration metadata, let's patch this in

Comment 1

[Axel Hecht [:Pike]]

Attachment: First iteration at meta data docs and example

Comment 2

[Francesco Lodolo [:flod]]

Comment on attachment 8863355 [details]
First iteration at meta data docs and example

Looks like you extended it a bit further than our initial discussion, e.g. project.import, description, and both of them make definitely sense.

One nit: metadata vs meta data.

There's one bit missing: path in metadata (page 2).

If you recall, the need is to cover what happens already in mozilla.org, where a file can have a different set of locales, different priority compared to the whole project, etc.

So, metadata could be associated to a path (a file, a folder), and we need some sort of aggregation strategy like we do for filters.

It's also going to be needed for tiers. For example:
* everything that's in /browser is tier 1
* then I only need rules for what has to be tier 2 or 3

Comment 3

[Axel Hecht [:Pike]]

Seems this landed with nits fixed.