Closed Bug 287585 Opened 20 years ago Closed 19 years ago

l10n CVS account request for Kazakh language (kk-KZ) for Talgat Daniyarov <tdaniyar@hotmail.com>

Categories

(mozilla.org :: Repository Account Requests, task)

Product:
mozilla.org
Component:
Repository Account Requests
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: tdaniyar, Assigned: marcia)

References

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050221 Firefox/1.0 (Ubuntu) (Ubuntu package 1.0+dfsg.1-6ubuntu1) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050221 Firefox/1.0 (Ubuntu) (Ubuntu package 1.0+dfsg.1-6ubuntu1) Firefox CVS access for Kazakh language (kk-KZ) localization is requested according to the "Registration of new L10n Project How-to". Please see Bug 287583 for further details. Contact details: Talgat Daniyarov, tdaniyar@hotmail.com Reproducible: Always
1) Please attach or link your localization files in CVS structure for review. 2) Please attach your SSH public key 3) FAX the CVS contributor form and also mail it
Status: UNCONFIRMED → NEW
Component: Registration & Management → CVS Account Request
Ever confirmed: true
Product: Mozilla Localizations → mozilla.org
Summary: Request for Firefox CVS access for Kazakh language localization → l10n CVS account request for Kazakh language (kk-KZ) for Talgat Daniyarov <tdaniyar@hotmail.com>
Version: unspecified → other
Assignee: registration → marcia
Blocks: 287583
QA Contact: registration → justdave
Status: NEW → ASSIGNED
Could we get a status update for this? We're going to branch for 1.1 late next week and would like to get new locales reviewed and in the tree by then, if possible.
QA Contact: justdave → justdave
No activity on this bug in quite some time - can we get a status?
2 requests for a status update and not much activity. I am closing this one out - please reopen if you want to pursue getting CVS access.
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.