Closed
Bug 728068
Opened 12 years ago
Closed 12 years ago
Document day-to-day maintainance flow in narro
Categories
(Mozilla Localizations Graveyard :: Documentation, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: gueroJeff)
References
()
Details
The current narro docs are focused on new contributors, and stop at the point where you register a localization effort. We should have doc that explains how localizers can use narro to maintain their localization effort, export updates for commit, investigate that commit, and push it. Also, if someone has contributions in hg, how to pull them in to narro, say if a file is moved.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → jbeatty
Assignee | ||
Comment 1•12 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #0) > The current narro docs are focused on new contributors, and stop at the > point where you register a localization effort. > > We should have doc that explains how localizers can use narro to maintain > their localization effort, export updates for commit, investigate that > commit, and push it. > > Also, if someone has contributions in hg, how to pull them in to narro, say > if a file is moved. The tutorial moves through the process of maintaining a L10n effort. It outlines exporting language packs and references lang pack testing on another wiki page, as testing a lang pack (or even an exported zip file) lie outside of the scope of Narro, as well as pushing it (unless I'm mistaken). I have already created another bug to take note of additional topics to outline in an intermediate or advanced Narro tutorial (https://bugzilla.mozilla.org/show_bug.cgi?id=718956) and another about hg topics to include in the MDN wiki (https://bugzilla.mozilla.org/show_bug.cgi?id=708410). Can we call this a duplicate and move these items to those bugs?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•12 years ago
|
||
Reopening: - bug 718956 lacks concrete topics to document, while this one has. - the artifacts that come out of an export from narro are special to narro, and not applicable to localizing on mercurial in general, thus I don't see this as a dupe of bug 708410. - bug 718956 also talks about admin features, which I don't think should be covered on the same front as this
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Assignee | ||
Comment 3•12 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #2) > Reopening: > > - bug 718956 lacks concrete topics to document, while this one has. > - the artifacts that come out of an export from narro are special to narro, > and not applicable to localizing on mercurial in general, thus I don't see > this as a dupe of bug 708410. > - bug 718956 also talks about admin features, which I don't think should be > covered on the same front as this Sounds reasonable :-) I'll look into this this week as I work on creating additional Narro documentation. Perhaps this should be part of an Intermediate tutorial. I'd rather not add too many details to the basic tutorial but keep it targeted at brand new contributors. Opinions?
Status: REOPENED → ASSIGNED
Reporter | ||
Comment 4•12 years ago
|
||
Yeah, separate page sounds totally fine.
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Updated•12 years ago
|
Assignee | ||
Comment 5•12 years ago
|
||
Intermediate tutorial has been written and reviewed and taken out of draft. Closing bug.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Mozilla Localizations → Mozilla Localizations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•